I believe the idea is that CPU cores are treated like compute units, and speed is simply a value the admin set based on availability and cost model. However the fact that you can create many different compute units, lets you leverage a more granular pricing model. CloudStack already factors into its thresholds the total value in GHZ, so speed is currently a consideration for capacity planning (the only consideration [units x GHZ]).
Could you maybe flesh out what you're thinking into a bit more detail? Thanks. -kd >-----Original Message----- >From: Koushik Das [mailto:koushik....@citrix.com] >Sent: Wednesday, January 16, 2013 10:34 AM >To: cloudstack-dev@incubator.apache.org >Subject: RE: [DISCUSS] Limit Resources to domain/account > >What is the upgrade story? For e.g. say based on the existing VM's for an >account, the total CPU and RAM exceeds the global maximums. What >happens in this case? >Also for CPU number of cores are considered, should speed also be >considered? > >-Koushik > >> -----Original Message----- >> From: Chris Sears [mailto:chris.x.se...@sungard.com] >> Sent: Wednesday, January 16, 2013 10:39 PM >> To: cloudstack-dev@incubator.apache.org >> Subject: Re: [DISCUSS] Limit Resources to domain/account >> >> On Wed, Jan 16, 2013 at 6:00 AM, Sanjay Tripathi >> <sanjay.tripa...@citrix.com >> > wrote: >> >> > Can anyone suggest that what should be the default max resource >> > values that an account/project can have for the following global >> > config >> parameters: >> >> >> It seems like the least surprising default max would be to leave them >> all unlimited. Otherwise, it's likely some admins will just overlook >> this and then just stumble upon the arbitrary limit. If you default to >> unlimited, only admins who need to restrict it will need to be concerned >with the settings. >> >> As an aside, I wasn't clear from the FS how to specify "unlimited" in the UI. >> Does leaving the value blank imply unlimited? >> >> - Chris
