Thanks for the suggestion. We can have an option that will allow admin to provide this kind of offering to a child domain, when resources are exhausted for him.
> -----Original Message----- > From: Saurav Lahiri [mailto:[email protected]] > Sent: Thursday, December 20, 2012 6:14 PM > To: [email protected] > Subject: Re: [DISCUSS] Dedicated Resources: Dedicate Pods, Clusters, Hosts > to a domain > > Lets say that the resources on the pod dedicated to the child-domain are > exhausted and resources on parent pod are available. In this case will > provisioning of vms for the child-domain happen on parent's pod. > > So essentially provisioning has a affinity for local pods if available. And if > resources are not available on the local pod but available on the parent pod > then use that. Would it be good to configure this affinity. > > Regards > Saurav > > On Thu, Dec 20, 2012 at 6:01 PM, Deepti Dohare > <[email protected]>wrote: > > > Hi Mice, > > > > Once a new pod is dedicated to the child-domain, deployment of the > > new VMs will happen only in the new pod. > > The existing VMs will keep running on parent-domain's pod. > > > > Do you have any other suggestion on this. > > > > - Deepti > > > -----Original Message----- > > > From: Mice Xia [mailto:[email protected]] > > > Sent: Thursday, December 20, 2012 4:52 PM > > > 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. > > > > > > 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? > > > > > > mice > > > >
