incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sateesh Chodapuneedi <sateesh.chodapune...@citrix.com>
Subject RE: [ACS41][DISCUSS] Adding support for VMware dvSwitch (Was: [ASF41][DISCUSS] Adding support for VMware dvSwitch)
Date Wed, 19 Dec 2012 03:56:11 GMT


> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: 18 December 2012 01:15
> To: cloudstack-dev@incubator.apache.org
> Subject: [ACS41][DISCUSS] Adding support for VMware dvSwitch (Was:
> [ASF41][DISCUSS] Adding support for VMware dvSwitch)
> 
> (note subject line change)
> 
> On Mon, Dec 17, 2012 at 2:40 PM, Sateesh Chodapuneedi
> <sateesh.chodapuneedi@citrix.com> wrote:
> > Hi,
> >
> >
> >
> > I am planning to work on enabling support for VMware native dvSwitch
> in CloudStack. Filed a jira ticket for it, see [1].
> >
> >
> >
> > Integration of VMware dvSwitch with CloudStack 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.
> >
> >
> >
> > I'll share an FS for this in the next few days.
> >
> > Please do let me know your thoughts/concerns.
> >
> 
> +1 on adding this support.  Do you intend to keep the implementation
> similar to how the Nexus1000v support works (or will after it's fixed)?
> I'd prefer that they are at feature parity, given that the 1kv is really
> just a replacement for the VMware DVS that gives operators a nice CLI to
> work against.
> 
Yes, I am trying to keep the implementation similar to Nexus100v support.
The dvSwitch would be an alternative for orchestration of virtual networks (of VMware servers)
in CloudStack.

> >
> > [1] CLOUDSTACK-657 - "VMware vNetwork Distributed Virtual Switch
> support in CloudStack"
> >
> >
> >
> > Regards,
> >
> > Sateesh
> >
> >
> >
> >
> >

Mime
View raw message