Open anpbabaki opened 9 years ago
anyone else seeing this?
Yes seeing the same on a fresh install. Used the ansible scripts from http://answersforaws.com/code/netflixoss/ice/ to set it up.
We are having this exact problem as well. Has anyone figured it out?
After a few days of digging I think I have it tracked to a undocumented config setting. In the code it defaults the property ice.resourceGroupCost to "modeled", which the code then goes and creates the ReservedInstanceHeavy even if you are not using it.
I set the property to ice.resourceGroupCost=fishy and the ReservedInstance was removed from the list.
I don't know if this will exactly fix your problem, but I have a feeling it might.
This post pretty much explains the reasoning for the behavior we are seeing..if you read the whole thread you will see what I mean
https://groups.google.com/forum/#!topic/iceusers/zh6pBh0c7oA
All OnDemandInstances are being shown as ReservedInstanceHeavy on the pages using Resource Groups. Running the latest commit, Grails 2.4.4
Here you can see us-east-1 EC2 costs are 15,502.69 and the On Demand and Reserved are properly broken down
Here you see on the Details with Rsource Groups, they are lumped into one Operation.