Page History

...

Architecture and Design description

CloudStack

...

reads physical traffic labels to understand the designated virtual switches to use for virtual network orchestration. Also virtual switch type is added to existing list of custom properties of cluster to enable a cluster level override option for virtual switch type. A cluster level option would precede over virtual switch type specified in zone level physical traffic label.

1. CloudStack does following,
   1. Create dvPortGroup over designated dvSwitch
   2. Modify dvPortGroup over designated dvSwitch
   3. Delete dvPortGroup over designated dvSwitch
2. CloudStack doesn't do following,
   1. Create dvSwitch
   2. Add host to dvSwitch
   3. Dynamic migration of virtual adapters of existing VMs across differnt types of virtual switches in scenarios in which co-existance of multiple types of virtual switches (Cisco's Nexus 1000v or VMware standard vSwitch and dvSwitch) is possible. Instead this is left to administrator to decide.
   4. Configuration of PVLAN
   5. Configuration dvPort mirror
   6. Configuration of user defined network resource pools for Network I/O Control (NIOC)

1. Highlight architectural patterns being used (queues, async/sync, state machines, etc) - N/A
2. Talk about main algorithms used

   ...

   1. 1. Isolated network configuration using VLAN over dvSwitch. CloudStack manages dvPortGroup configured with a designated VLAN ID.

   ...

   1. 1. The scenarios to be covered are,

      ...

      1. 1. 1. Adding host/compute resource to podcluster. Create necessary cloudstack managed virtual networks on designated dvSwitch.

      ...

      1. 1. 1. Livemigration

      ...

      1. 1. 1. All VM life cycle operations which might need instantiation of guest network etc.

      ...

      1. 1. 1. Network operations like network creation, network destroy etc.

      ...

      1. Port binding would be static binding.

      ...

      1. Performance implications: what are the improvements or risks introduced to capacity, response time, resources usage and other relevant KPIs•In vSphere 5.0, we will use "AutoExpand" support to configure dvPorts per dvPortGroup. This ensures that we don't pre-allocate unnecessary dvPorts so that they

      ...

      2. Packages that encapsulates the code changes,
         ##core

      ...

      1. package (VmwareManager, VmwareResource)
         

      ...

      1. ##server package
         

      ...

      1. ##vmware-base package mo and util packages

      Web Services APIs

      Changes to existing web services APIs - AddClusterCmd
      Adding an optional parameter named 'virtulSwitchType' which can have values 'vmwaresvs' or 'vmwaredvs' or 'nexusdvs'.
      New APIs introduced - N/A

      UI flow

      Add cluster wizard

      If hypervisor is VMware and global configuration parameter "vmware.use.dvswitch" is set to true, then display a list box. List box details are below,

      ...