Page History

...

1. Track relationship between resources (DC <-> Cluster <> DataStore <> DVS <> N1kv <-> ASA etc.) in cloudstack database - suffices within single CloudStack deployment. Cannot detect if multiple CloudStack deployments are managing same resource (DC, DataStore etc.)
2. Use custom property on VMware object as flag. This works across cloustack deployments but proper cleanup is required upon removal.

• 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.

Database modifications

1. 'cloud'.'vmware_dc' table to track all DC specific information along with details of resources & vCenter.
2. 'cloud'.'zone_dc_map' table will be added to store mapping of zone to DC.
3. 'cloud'.'cluster_vsm_map' would be removed.
4. 'cloud'.'zone_vsm_map' would be added. Also a zone can be associated with more than 1 VSM instances.

...