Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Root Admin should be able to dedicate a pod, cluster or host to any domain or sub-domain.
  2. Once a Zone is dedicated to a domain,  its pods and clusters will be dedicated to that domain eg: pod: p1 is dedicated to domain D1, clusters:c1, c11, c111 will be automatically dedicated to D1 by default.
  3. Resources under dedicated resource (to a domain) can be further dedicated, if dedication is done for sub-domain or accounts under domain or subdomain.
  4. A resource for eg. a zone, cannot be dedicated if resources under this zone is dedicated to domain/sub-domain/account not belonging to the domain requesting dedication.
  5. Eg. Suppose some hosts in a cluster are dedicated to Account A1. If admin wants to dedicate that cluster to same account A1, then dedicated hosts will be automatically released before the dedication of that cluster.   
  6. Users in Sub-Domains SD1, SD2, SD3 should be able to deploy vm in parent domain's clusters c1, c11, c111 or pod p1. 
  7. After dedicating pod p1 to domain D1, if further cluster c11 (in pod p1) is dedicated to SD3, then D1 or SD1 or SD2 should not be able to access c11. (Can SD3 use SD2, SD1 or D1's resources, verify)
  8. If another pod p2 is dedicated to SD1, then SD11, SD12 or D2 should not be able to access pod p2.
  9. Before dedicating a pod to a domain , check whether its zone is dedicated or not.
  10. Child Domain can access pod/cluster/host dedicated to parent domain, vice-versa is not.

...