[
https://issues.apache.org/jira/browse/CLOUDSTACK-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577719#comment-13577719
]
ilya musayev commented on CLOUDSTACK-657:
-----------------------------------------
Sateesh
Thank you for the work on dvS support.
As you may know i'm actively testing dvSwitch portion you wrote - as we have an
immediate need of dVs support to make use of good number of vmware clusters
that all use dvs.
Please answer the following when possible:
1) I see the dvs support was pushed into 4.2 - is there a reason why it cant be
part of 4.1 - granted we do all of QA in the next week?
2) you have posted a link to your own github, does it mean the patches posted
on review board maybe outdated? If i was to use your github, can i merge it
with current master? I'm git beginner, so any pointers are very much
appreciated.
I'll be testing the code out today.
Thanks
ilya
PS: I tried backporting your code into 4.0 branch, but that did not go to well
- due to network refactoring on 4.1.. so i'm now back on 4.1 :)
> VMware vNetwork Distributed Virtual Switch support in CloudStack
> ----------------------------------------------------------------
>
> Key: CLOUDSTACK-657
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-657
> 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 vCenter.
> 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 accordingly.
> 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:
> http://markmail.org/message/eehzokoniwssrx5d
> http://markmail.org/message/ow7za62d3qmnjd2h
> Functional Spec:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Integration+of+CloudStack+with+VMware+DVS
> 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: http://www.atlassian.com/software/jira
