incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-657) VMware vNetwork Distributed Virtual Switch support in CloudStack
Date Wed, 27 Feb 2013 13:09:13 GMT


ASF subversion and git services commented on CLOUDSTACK-657:

Commit 3c00e7b8c52014d8b531b0bb7bd48f5d25506372 in branch refs/heads/master from [~sateeshc]
[;h=3c00e7b ]

Re-basing with latest master.

CLOUDSTACK-657 VMware vNetwork Distributed Virtual Switch support in CloudStack

This is 5th patch for feature 'Support for VMware dvSwitch in CloudStack'.

This patch contains
1)Changes to addCluster done in vmware discoverer to support vswitch type provided as parameters.
Also performing validation of vswitch type parameter provided with addCluster api call. Checks
for physical network configuration for vmware cluster is added.
2)Changes to vmware resource to use specified vswitch type while preparing network for guest
and public traffic types.
3)Changes to vmware manager to introduce new global parameter vmware.ports.per.dvportgroup.
Some cleanup.
Virtual switch type could be chosen at zone level or at cluster level for specific traffic
autoExpand of dvPortGroup is available in code but disabled as its breaking because vCenter
4.1 does not support autoExpand feature. Would be enable once vSphere 5.1 SDK support is added
to CloudStack.

Signed-off-by: Sateesh Chodapuneedi <>

> VMware vNetwork Distributed Virtual Switch support in CloudStack
> ----------------------------------------------------------------
>                 Key: CLOUDSTACK-657
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>         Environment: VMware vSphere 4.1/5.0/5.1
>            Reporter: Sateesh Chodapuneedi
>            Assignee: Sateesh Chodapuneedi
>             Fix For: 4.2.0
> Need to integrate the functionality of VMware dvSwitch with CloudStack. This enables
orchestration of virtual networks in VMware environment over distributed virtual switch inside
> Background:-
> -----------------
> 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.
> Each Standard vSwitch represents an independent point of configuration that needs to
be managed and monitored. The management of virtual networks required by instances in the
cloud is tedious when virtual networks have to span across large number of hosts. Using distributed
vSwitch (vDS) simplifies the configuration and monitoring.
> Being standalone implementations, standard vSwitches do not provide any support for virtual
machine mobility. So there needed a component  to ensure that the network configurations on
the source and the destination virtual switch are consistent and will allow the VM to operate
without breaking connectivity or network policies. Particularly during migration of VM across
hosts, the sync up among peers need to be taken care.  However in case of distributed vSwitch
during VMotion, the vCenter server, would update the vSwitch modules on the hosts in cluster
> Following features are available with a Distributed Switch over and above Standard vSwitch
of vSphere.
> 1. Shaping of inbound (RX) traffic
> 2. Supports a central unified management interface through vCenter Server
> 3. Supports Private VLANs (PVLANs)
> 4. Provides potential customization of Data and Control Planes
> 5. Increased visibility of inter-virtual machine traffic through Netflow
> 6. Improved monitoring through port mirroring (dvMirror)
> 7. Support for LLDP (Link Layer Discovery Protocol), a vendor-neutral protocol.
> Release Planning:
> Dev list discussions:
> Functional Spec:
> Feature branch: reviewboard submission

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message