As far as implementation goes you can have a look at how to create customizable disk offering for reference and it should be on the same lines. Thinking loud you will have to change deployvm and createservice offering api, allocator logic a bit for pushing customized cpu and ram, capacity checker logic to pick up customizable size and last not the least UI as well. Why don't you give it a shot by creating a Functional spec for this and I can review it for you which should give us an idea of how much work will be required (my hunch says not quite a lot)
But, before we tread this path it would be good to understand your use case here. Generally speaking, I do not see a lot of customized configuration required for cpu and ram compared to disk size and I guess that is why we never had customized cpu and ram in the first place. Thanks, -Nitin -----Original Message----- From: sx chen [mailto:cloudchen0...@gmail.com] Sent: Thursday, October 04, 2012 9:50 AM To: cloudstack-us...@incubator.apache.org Cc: cloudstack-dev@incubator.apache.org Subject: Re: How can I specify the vCPU and ram manually? Date: 2012/10/4 Subject: Re: How can I specify the vCPU and ram manually? To: cloudstack-dev@incubator.apache.org Cc: "cloudstack-us...@incubator.apache.org" < cloudstack-us...@incubator.apache.org> let the custom set the service offering,disk offering and network offering is a little confused. I don't think every custom is so familiar with all these offerings. So if the admin create the offerings,and let the custom select CPU,ram,and disk and network is another choice. So If the CloudStack service offering will set a range for vCPU and ram just like disk offering, and let the custom set the vCPU and ram when custom deploy a vm will meet my request. If I change the source code for this, will it be a large project?
