Given the move away from defining these access rights in code (see [1]), I hope that these checks are going to be defined in the new ACL check layer.
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+API+refac toring On 12/19/12 10:39 PM, "Manikanta Kattamuri" <manikanta.kattam...@sungard.com> wrote: >This seems to be sort of a private cloud feature in a shared DC. > >> In this feature >> - Root Admin should be able to dedicate a pod/cluster/host to a >> particular domain or sub-domain. >Will the domain/sub-domain will also have access to shared resources? > >Then what happens to the domain specific resources like iso's, templates >etc... where will they be placed. > > >--Mani > >-----Original Message----- >From: Anthony Xu [mailto:xuefei...@citrix.com] >Sent: Thursday, December 20, 2012 11:59 AM >To: cloudstack-...@incubator.apache.org; >cloudstack-users@incubator.apache.org >Subject: RE: [DISCUSS] Dedicated Resources: Dedicate Pods, Clusters, Hosts >to a domain > >> In this feature >> - Root Admin should be able to dedicate a pod/cluster/host to a >> particular domain or sub-domain. > >How about primary storage? Can PS be dedicated to a domain? > >Can an account have dedicated resource? > >> - If there is no available resources in the dedicated >> pod/cluster/host, then CloudStack should fail the operation >> for a user in that domain. > >If this happens, how does admin handle this? >Can admin extend resource for this domain? > > >Anthony > > > > >> -----Original Message----- >> From: Deepti Dohare [mailto:deepti.doh...@citrix.com] >> Sent: Wednesday, December 19, 2012 10:20 PM >> To: cloudstack-...@incubator.apache.org; cloudstack- >> us...@incubator.apache.org >> Subject: [DISCUSS] Dedicated Resources: Dedicate Pods, Clusters, Hosts >> to a domain >> >> 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. >> >> Thanks >> Deepti
