Page History

...

1. Only clusters of the associated DC can be added to a zone.
   1. Retrieve name of DC which encompasses this cluster. Compare the retrieved DC name with name of DC (being) associated with this zone.
2. Only N1kv VSM of the associated DC can be added to a zone.
   1. N1kv's vCenter server connection's properties would need to be checked to retrieve the association of N1kv with a vCenter and a DC. Compare the retrieved vCenter IP and DC name with vCenter IP and DC name of current zone
3. DC is not associated with any other zone already.
   1. Check guid, of new DC being added, doesn't already exist in table 'cloud'.'data_center_zone_map'. The guid is a string that encapsulates MOR of DC and vCenter host name/ip. By tracking both vCenter host name/ip and MOR of DC, it's possible to distinguish DC's across multiple vCenters.
4. DC is not associated with any other cloudstack deployment.
   1. Check custom property over VMware's DC object if this DC is already associated with a zone of a cloudstack deployment. Custom property of type boolean can represent this, 'cloudstackzone'

• While adding resource adding to cloudstack zone, approaches to apply constraint checks are,

...

1. 'cloud'.'vmware_dc' table to track all DC specific information along with details of resources & vCenter.
   1. Implement Dao & VO for this table.
   2. Columns in this table are id, vCenter host/ip, DC name, DC Mor, guid
   3. id is primary key field of this table
2. 'cloud'.'zone_dc_map' table will be added to store persist the mapping of zone to DC.
   1. Columns in this table are id, vmware_dc_id, zone_id
   2. Foreign key id from vmware_dc table
   3. Foreign key id from data_center table
   4. Implement Dao & VO for this table.
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.
   1. Columns in this table are id, zone_id & vsm_id where id is Primary key of this table.
   2. Foreign key zone_id from data_center table.
   3. Foreign key vsm_id from virtual_supervisor_module table.
   4. Implement Dao & VO classes for this table.

Web Services APIs

1. AddCluster will be modified
   1. Make vCenter credentials and DC name optional based on vmwaredc keyzone id's presence in datazone_centerdc_detailsmap.

UI Flow

• Changes required in UI for live migrating a volume from one storage pool to another.
  1. Add Cluster form in zone wizard
  2. Add Cluster wizard
  3. Add NexusVSM instance to zone
  4. Add ASA instance to zone

...