Page History

...

https://issues.apache.org/jira/browse/CLOUDSTACK-657

Branch

master, 4.12.0

Introduction

VMware Distributed Switch is an aggregation of per-host virtual switches presented and controlled as a single distributed switch through vCenter Server at the Datacenter level. vDS abstracts configuration of individual virtual switches and enables centralized provisioning, administration, and monitoring.
vDS is integral component of vCenter. Hence the native vDS support makes sense for wider and larger deployments of Cloudstack over vSphere.

...

1. Check box
   1. Label - Choose to override zone wide traffic label for guest traffic for this cluster.
   2. Function - This check box controls below list box and text box.
2. List Box
   1. Label - "Guest Virtual Switch Type"
   2. Default option - if "vmware.use.nexus.dvswitch" is true then use "Cisco Nexus 1000v Distributed Virtual Switch". Otherwise use "VMware vNetwork Distributed Virtual Switch"
   3. List Box options are,
      1. "VMware vNetwork Standard Virtual Switch"
         Action to perform if this option is selected:-
         Add a parameter to parameter list of AddClusterCmd API call.
         Parameter name: "guestvswitchtype"
         Parameter value: "vmwaresvs"
      2. "VMware vNetwork Distributed Virtual Switch"
         Action to perform if this option is selected:-
         Add a parameter to parameter list of AddClusterCmd API call.
         Parameter name: "guestvswitchtype"
         Parameter value: "vmwaredvs"
      3. "Cisco Nexus 1000v Distributed Virtual Switch"
         Action to perform if this option is selected:-
         Add a parameter to parameter list of AddClusterCmd API call.
         Parameter name: "guestvswitchtype"
         Parameter value: "nexusdvs"
3. Text Box
   1. Label - "Name of Virtual Switch for guest traffic"
   2. Action to perform if the text box is not empty:-
      Add a parameter to parameter list of AddClusterCmd API call.
      Parameter name: "guestvswitchname"
      Parameter value: textbox content
4. Check box
   1. Label - Choose to override zone wide traffic label for public traffic for this cluster.
   2. Function - This check box controls below list box and text box.
5. List Box
   1. Label - "Public Virtual Switch Type"
   2. Default option - if "vmware.use.nexus.dvswitch" is true then use "Cisco Nexus 1000v Distributed Virtual Switch". Otherwise use "VMware vNetwork Distributed Virtual Switch"
   3. List Box options are,
      1. "VMware vNetwork Standard Virtual Switch"
         Action to perform if this option is selected:-
         Add a parameter to parameter list of AddClusterCmd API call.
         Parameter name: "publicvswitchtype"
         Parameter value: "vmwaresvs"
      2. "VMware vNetwork Distributed Virtual Switch"
         Action to perform if this option is selected:-
         Add a parameter to parameter list of AddClusterCmd API call.
         Parameter name: "publicvswitchtype"
         Parameter value: "vmwaredvs"
      3. "Cisco Nexus 1000v Distributed Virtual Switch"
         Action to perform if this option is selected:-
         Add a parameter to parameter list of AddClusterCmd API call.
         Parameter name: "publicvswitchtype"
         Parameter value: "nexusdvs"
6. Text Box label
   1. Label - "Name of Virtual Switch for public traffic"
   2. Action to perform if the text box is not empty:-
      Add a parameter to parameter list of AddClusterCmd API call.
      Parameter name: "publicvswitchname"
      Parameter value: textbox content

Open Issues

1. What is level of support for migration Scenarios? Does an existing CloudStack deployment over standard vSwitch need to be migrated to dvSwitch?
2. Management network over virtual switches other than standard vSwitch. Does CloudStack has to support management/private network over dvSwitch or just support guest and public network traffic?

...