Hi Ilya, Rebasing the patches against master instead of 4.1 branch. As the feature is targeted for 4.1 it makes sense to merge the patches into master rather than 4.1 branch. Currently testing the rebased bits, would re-submit as soon as verification is done.
Regards, Sateesh > -----Original Message----- > From: Sateesh Chodapuneedi [mailto:sateesh.chodapune...@citrix.com] > Sent: 21 February 2013 06:37 > To: cloudstack-dev@incubator.apache.org > Subject: RE: [jira] [Commented] (CLOUDSTACK-657) VMware vNetwork > Distributed Virtual Switch support in CloudStack > > Sure Ilya, I will re-submit the patches after rebasing with latest 4.1 > > Regards, > Sateesh > > > > -----Original Message----- > > From: ilya musayev (JIRA) [mailto:j...@apache.org] > > Sent: 21 February 2013 06:34 > > To: cloudstack-dev@incubator.apache.org > > Subject: [jira] [Commented] (CLOUDSTACK-657) VMware vNetwork Distributed > > Virtual Switch support in CloudStack > > > > > > [ https://issues.apache.org/jira/browse/CLOUDSTACK- > > 657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment- > > tabpanel&focusedCommentId=13582754#comment-13582754 ] > > > > ilya musayev commented on CLOUDSTACK-657: > > ----------------------------------------- > > > > Sateesh, > > > > Please re-create your patches against current 4.1 base or master branch. > > > > I could not apply the patches manually - specifically patch2 and patch5. > > > > Please post the new patches (that hopefully apply cleanly) i will retry once > more. > > I've just spend a decent amount of time backporting the patches - but as it > > seems, the branch you used to create this batch changed by alot from what is > > recent on git repo. I personally find a snapshot of 4.1 somewhat stable - > > so i > > attempted to backport your patches to 4.1 branch. The build process failed, > with > > errors, in any regard, i dont think its worth troubleshooting my hack. > > > > It would be much cleaner and better if you can do this - since you know the > code > > way better than i do. Btw, even if the patches passes review - we will > > still have > > trouble applying these patches, so you may as well get it working on newer > code > > base. > > > > Thank you > > ilya > > > > > > > > > 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
