Page History

...

Architecture and Design description

1. Vmware datacenter will be put under management of CloudStack zone.
2. In this explicit model, CloudStack will understand the relationship between a Vmware datacenter and resources underneath it, so when resources like a Vmware cluster or dvSwitch that is added to CloudStack, the underlying Vmware resource relationship between these objects will become constraint information for CloudStack to use. For example, a Vmware cluster can't be added to a CloudStack zone if it's Vmware DC is not under the CloudStack zone, also an ASA instance cannot be added to a Vmware cluster that its Vmware DC is not in the zone. The model itself will not limit how many Vmware clusters that a N1kv VSM instance or ASA or vDS will manage, as long as N1kv or ASA or vDS and its managed cluster are within the same Vmware DC.
3. CloudStack should be able to add/manage following DC level resources in scope of zone.
   1. Clusters
   2. Datastores for zone wide storage
   3. Distributed virtual switches for zone wide virtual networks.
      1. Nexus 1000v DVS
      2. VMware DVS - this is already realized by zone wide traffic labels.
4. Constraint checks
   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'
5. While adding resource to cloudstack zone, approaches to apply constraint checks are,
   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.
6. During discovery process, VmwareServerDiscoverer might have to retrieve vCenter host/ip & credentials from database given zone_id, because they are made optional parameters because this data is already available in database when the zone is associated with first cluster. Construct connection url from this data.
7. While re-loading resource make sure connection url is defined correctly, could be retrieved from vmware_dc table (guid).
8. AddCluster changes
   1. If a row matches zone_dc_map.zone id and if DC name is not specified, DC name can be retrieved from vmware_dc table and used. If DC name is specified, validation of DC name should happen.
   2. In VmwareServerDiscoverer, implement constraint checks while adding a cluster as mentioned in design section.
   3. Update vmware DC properties in cloud.vmware_dc table (Say DC name changes in vCenter)
   4. While adding VMware cluster to zone, check if zone_dc_map is empty or not. If empty, while adding this cluster we need to associate corresponding DC to zone. Hence do following,
      1. Update tables cloud.zone_dc_map and cloud.vmware_dc to associate DC with zone
      2. If N1kv instance is specified, update table cloud.virtual_supervisor_module and cloud.zone_vsm_map to assocaite N1kv VSM instance with zone
      3. Set custom property over VMware DC object. If not already present, add boolean property 'cloudstackzone' with value 'true'. If the property is already present, just set it to 'true'. Now this DC cannot be associated with any other cloudstack zone.
   5. Allow multiple N1kv VSM instances to be added to zone.
   6. Avoid cascaded removal of VSM instance upon cluster deletion as the association is now at zone level.
   7. Change cleanup code of N1kv VSM instances as cleanup should happen automatically with zone removal instead of cluster removal earlier.
9. DeleteCluster changes
   1. While deleting check if this is last cluster in the zone. If so, dis-association of DC to zone should be done. Hence do following,
      1. Cleanup tables cloud.zone_dc_map and cloud.vmware_dc for specific zone by removing entries by zone_id (if zone_id in row matches data_center.id then remove the row)
      2. Set the zone's corresponding DC object's property to 'false'. Now this DC can be associated with any other cloudstack zone.

Database modifications

1. 'cloud'.'vmware_dc' table to track all DC specific information along with details of resources & vCenter.
   1. Columns in this table are id, vCenter host/ip, DC name, DC Mor, guid
   2. id is primary key field of this table
   3. Implement Dao & VO for this table.
2. 'cloud'.'zone_dc_map' table will be added to 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.

...