@ma78 Can you let me know in August ap-southeast-2, what product, operation and usagetype are when Ice shows changes and you think it's not possible? This will help me understand what the issue is.

from ice.

Apologies.. i had an error in my ice.properties which I needed to regenerate and once i cleared everything i found the usage.

Just to confirm.. if i am using:
ice.reservationCapacityPoller=false

Then under the "reservations by region" page under the "usage" listing of "Reserved Instances" is the hourly number of RI slots that are being applied to the account?

Also.. how to handle the situation where an account has a variety of light/medium/heavy RIs?

from ice.

@ma78 If you set ice.reservationCapacityPoller=false, Ice will not poll the API to find out how many RIs your accounts have. So under the "reservations by region" page under the "usage" listing of "Reserved Instances" is the hourly number of used RI hours (which could be less the total RI #).

I am implementing the feature to handle multiple RI utilizations. It should be ready in the next a couple weeks or so.

Thanks
-Fang

from ice.

Thanks Fang so to clarify...

If not using poller

• the usage figure can be used to identify how many RIs you are using per hour.. but you would need to know how many RIs you actually have to know whether you are getting full utilisation
  • the cost figures in the "reserved instances" show ondemand and reserved instances only. will these be accurate?

If you are using the poller

• if you have created an "owneraccount" line in ice.properties for each and every account with RIs under your consolidated billing structure, then under the 'reservations" tab the number of Reserved + Lent + Unused instances should always equal the number of RIs on your account ?
• if you have missed any of your accounts with RIs then the usage figure will not be accurate
• as above, can you trust the cost figures if you have not accurately captured all accounts with RIs?
• wouldn't you expect the number of "borrowed" instances to equal the number of "lent" instances at all times? for me it is always different and i can't see how that can be.

from ice.

If not using poller:
You understanding it right. Ice will now show amortized upfront cost. For heavy RIs, Ice will not show unused hourly cost either.

If you are using the poller:
You should configure owneraccount properties correctly.
If you missed some accounts, the instance usage/cost for the missed accounts should be the same with not using poller.
The the number of "borrowed" instances should be equal the number of "lent" instances at all times. I'm curious how can you see different numbers... Did you select all accounts? Note the "borrowed" and "lent" instances are from different accounts.

from ice.

@ma78 the borrowed and lent numbers should always match. I'm not sure why are you seeing different numbers...

For the mixed ec2 reservation utilizations, I just checked in a feature for that a few days ago. To use this feature, please get the latest code and clean&reprocess you data.

If you have 3 out of 9 accounts having RIs, assuming they are all under the same payer account, they should be able to share RIs from each other. In your ice.properties file, make sure you have:

1. ice.reservationCapacityPoller=true
2. ice.owneraccount.act1=act2,act3,act4,act5,act6,act7,act8,act9
   ice.owneraccount.act2=act1,act3,act4,act5,act6,act7,act8,act9
   ice.owneraccount.act3=act1,act2,act4,act5,act6,act7,act8,act9

Replace act1, act2, act3 with the 3 account names with RIs and act4-9 with your other account names.

Thanks
Fang

from ice.

@ma78 the borrowed and lent numbers should always match. I'm not sure why are you seeing different numbers...

For the mixed ec2 reservation utilizations, I just checked in a feature for that a few days ago. To use this feature, please get the latest code and clean&reprocess you data.

If you have 3 out of 9 accounts having RIs, assuming they are all under the same payer account, they should be able to share RIs from each other. In your ice.properties file, make sure you have:

1. ice.reservationCapacityPoller=true
2. ice.owneraccount.act1=act2,act3,act4,act5,act6,act7,act8,act9
   ice.owneraccount.act2=act1,act3,act4,act5,act6,act7,act8,act9
   ice.owneraccount.act3=act1,act2,act4,act5,act6,act7,act8,act9

Replace act1, act2, act3 with the 3 account names with RIs and act4-9 with your other account names.

Thanks
Fang

Sent from my iPhone

On Nov 24, 2013, at 6:07 PM, ma78 [email protected] wrote:

Yes I have all account selected. Three of the nine accounts have RI purchases. Those three are configured into ice.properties to share with all other accounts. At one point in time I see:

Reserved: 255
Borrowed: 2
Lent: 14
Unused: 18

Could this have to do with the fact that the RIs are mixed? (A combination of fixed, heavy, medium and light).

Also, I'm unclear as to why you have provided the ability to decide on who shares which RIs. They should be shareable by all accounts. And there should only be one payer account being parsed by Ice.. what am I missing? (Unless you have used multiple ice.billing_payerAccountId= lines??)

—
Reply to this email directly or view it on GitHub.

from ice.

Fang

That is exactly how I have configured ICE. I'll have to look deeper at why there is a mismatch.

I still don't understand the need for the ice.owneraccount.act1 parameter. Is it possible to have multiple payer accounts in the one ice.properties file? If so then this makes sense... if not, the RIs can all be shared between all accounts so why need to specify it?

Also, your "mixed ec2 reservations" feature doesn't have any documentation.. how do we actually configure ICE to look at all types of RIs? Should we now ignore the ice.reservationPeriod and ice.reservationUtilization parameters?

Thank you Fang :)

from ice.

@ma78

You can have configure multiple payer accounts in Ice. You will need to specify multiple values (delimited by ,) for following properties: (See item 1.6 in Readme page)
# s3 bucket name where the billing files are. multiple bucket names are delimited by ",". Ice must have read access to billing s3 bucket.
ice.billing_s3bucketname=billing_s3bucketname1,billing_s3bucketname2
# prefix of the billing files. multiple prefixes are delimited by ","
ice.billing_s3bucketprefix=,
# specify your payer account id here if across-accounts IAM role access is used. multiple account ids are delimited by ",". "ice.billing_payerAccountId=,222222222222" means assumed role access is only used for the second bucket.
ice.billing_payerAccountId=,123456789012
# specify the assumed role name here if you use IAM role access to read from billing s3 bucket. multiple role names are delimited by ",". "ice.billing_accessRoleName=,ice" means assumed role access is only used for the second bucket.
ice.billing_accessRoleName=,ice
# specify external id here if it is used. multiple external ids are delimited by ",". if you don't use external id, you can leave this property unset.
ice.billing_accessExternalId=

If you enable ReservationCapacityPoller, ice.owneraccount properties are needed to by ReservationCapacityPoller to make describeReservedInstances calls in different RIs owner accounts.

With the new mixed ec2 reservation utilizations feature, properties ice.reservationPeriod and ice.reservationUtilization parameters will be used to convert on-demand ec2 instance costs by ResourceGroups into reserved costs.

from ice.

Fang that is not immediately obvious from the readme... When I get a chance
I'll update it with wording that spells out you can use multiple payer
accounts. (at the least there should be a comment near the payeraccountid
line explaining this). Now it makes sense!

I'm unclear on your last sentence.. If we have a mix of RI types should we
configure multiple ice.reservationPeriod and ice.reservationUtilization
lines or leave them commented out?
On 27/11/2013 8:11 AM, "fangji" [email protected] wrote:

@ma78 https://github.com/ma78

You can have configure multiple payer accounts in Ice. You will need to
specify multiple values (delimited by ,) for following properties: (See
item 1.6 in Readme page)

s3 bucket name where the billing files are. multiple bucket names are

delimited by ",". Ice must have read access to billing s3 bucket.
ice.billing_s3bucketname=billing_s3bucketname1,billing_s3bucketname2

prefix of the billing files. multiple prefixes are delimited by ","

ice.billing_s3bucketprefix=,

specify your payer account id here if across-accounts IAM role access is

used. multiple account ids are delimited by ",".
"ice.billing_payerAccountId=,222222222222" means assumed role access is
only used for the second bucket.
ice.billing_payerAccountId=,123456789012

specify the assumed role name here if you use IAM role access to read

from billing s3 bucket. multiple role names are delimited by ",".
"ice.billing_accessRoleName=,ice" means assumed role access is only used
for the second bucket.
ice.billing_accessRoleName=,ice

specify external id here if it is used. multiple external ids are

delimited by ",". if you don't use external id, you can leave this property
unset.
ice.billing_accessExternalId=

If you enable ReservationCapacityPoller, ice.owneraccount properties are
needed to by ReservationCapacityPoller to make describeReservedInstances
calls in different RIs owner accounts.

With the new mixed ec2 reservation utilizations feature, properties
ice.reservationPeriod and ice.reservationUtilization parameters will be
used to convert on-demand ec2 instance costs by ResourceGroups into
reserved costs.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/75#issuecomment-29334237
.

from ice.