> -----Original Message-----
> From: Mice Xia [mailto:[email protected]]
> Sent: 20 December 2012 16:52
> To: [email protected]
> Subject: RE: [DISCUSS] Dedicated Resources: Dedicate Pods, Clusters,
> Hosts to a domain
>
> but if further sub-domain is assigned a different pod then it cannot
> access
> its parent domain's pod. 2. Sub-domain and its child domains will have
> the
> sole access to that new pod.
By default we could work on a restrictive mode wherein if a domain(or a
subdomain) has resources dedicated to him/her then he/she will be forced to use
those resources only. Once the compute on dedicated resource are exhausted then
further deployVM calls will fail. We can introduce an option in compute
offering to relax this restriction wherein the said domain can fallback to
shared resources once he exhausts his resources. I am open to more ideas!
>
> when child domain already has some VMs on parent domain's dedicated
> pod, is
> it allowed to assign a pod to the child domain? or the existing VMs
> will be
> migrated to the new pod?
>
To start we could look at any future deployVM calls to use the dedicated
resources while the existing VMs continue on the shared resources. This I think
we give a nice transition path for existing customers of CloudStack.
Please let us know your thoughts.
> mice
