On Thu, Dec 20, 2012 at 1:19 AM, Deepti Dohare <deepti.doh...@citrix.com> wrote: > Hi, > > Currently in CloudStack architecture, domains can have dedicated zones but > not pods, clusters or hosts. > > We are proposing this functionality in "Dedicated Resources" where a domain > or a sub-domain can have dedicated pods, clusters or hosts. > > Why we need this feature: > Dedicating a zone might be very expensive offering for an end users, whereas > dedicating a pod, cluster or a host > may be more economical. This feature will allow Root-Admin to dedicate > resources to a specific domain that needs > private infrastructure for additional security or performance guarantees. > > In this feature > - Root Admin should be able to dedicate a pod/cluster/host to a particular > domain or sub-domain. > - Any users in that domain can access pod/cluster/host dedicated to their > domain. > - No users outside that domain, can access the dedicated pod, cluster or > hosts (eg. deploy instance on that pod/cluster/host). > - If there is no available resources in the dedicated pod/cluster/host, then > CloudStack should fail the operation > for a user in that domain. > > I have filed a jira request: > https://issues.apache.org/jira/browse/CLOUDSTACK-681, to track this feature. > Please let me know any comments and suggestions. >
So I personally think hosts are too low of a level to do something like this. clusters makes sense, but not individual hosts. Also - I think 90% of the benefit of this feature could be realized by changing the way we handle allocation on tagged resources. (e.g. require the tag to be present in the service offering to be deployed on a tagged resource) --David
