Page History

...

1. Manage Clusters
2. Manage Datastores for zone wide storage
3. Manage distributed virtual switches for zone wide virtual networks.
   1. Nexus 1000v DVS
   2. VMware DVS

• Discover resources in DC being associated with zone. Resources could be,

1. dvSwitches,
2. Datastores,
3. Clusters,

• Upon adding to cloudstack, approaches to apply constraint checks are

1. Track relation information in cloudstack database - works per single cloudstack deployment
2. Use custom property on vmware object - works across cloustack deployments

Using dvswitches or datastores is fine if configuration is mutually exclusive, means guest VLANs doesn't overlap etc.
datastore also vm names like s-1-vm or instance name path should not clash in case of primary storage.

• Mapping dc to zone in database
• Resource management in dc/zone

1. Discover resources in dc
2. Add resource to zone
3. Check if resource is part of other cloudstack deployment
4. Check if resource satisfies constraints
   1. resource should be part of DC associated with zone - if discover resources done and choosing from that list then this check can be skipped.
5. Delete resource from zone

• Single DC will NOT be allowed to be managed by multiple cloudstack deployments. Add custom property to DC to flag if DC is being managed by cloudstack. Flag needs to be cleared upon 'unmanaging'/'removing' the last cluster in that zone.

...

1. Choosing to NOT allowing single DC to be managed by multiple cloudstack deployments. Name space collision issues within DC will be resolved by this.
2. Sharing of resources with other entity (cloudstack or non-cloudstack entity)
3. DC release criteria from association with zone - deletion of last host or last cluster?

Impact on other areas/features

...