Created attachment 562130 [details] Template mismatch Steps to Reproduce: 1. Create a hardware profile with below configuration memory(MB) 1024 cpu count 2 storage(GB) 200 architecture label x86_64 Expected Results: The close match from aws template definition for the above configuration is m1.large. Actual Results: Aeolus displays c1.xlarge as the close match(PFA: Template mismatch.png) Additional info: cost of m1.large:$0.20 per hour(for Linux usage) cost of c1.xlarge:$0.40 per hour(for Linux usage) Conclusion: It seems that aeolus is choosing the close match based on RAM value. It will be really appreciated, if aeolus would consider all the possible parameters (which includes the cost also) to choose the best possible match, this will benefit the end customer to a greater extent.
Contact me.. Thanks
The problem is that cost isn't available via deltacloud. All we have is RAM and CPU. Taking both RAM and CPU into account would potentially better than simply taking RAM into account, but that would require us to define the relative "size" of a given amount of extra RAM vs. a given amount of extra CPU, and so far we hadn't come up with a satisfactory way of doing this.
*** Bug 801505 has been marked as a duplicate of this bug. ***