Does this mean that zones with both standard vSwitch clusters and dvSwitch clusters will not be supported? Can you not discover the type of vSwitch when the cluster is added?
On 1/2/13 11:57 PM, "Sateesh Chodapuneedi" <sateesh.chodapune...@citrix.com> wrote: >> -----Original Message----- >> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] >> Sent: 03 January 2013 13:12 >> To: CloudStack DeveloperList >> Subject: Re: [ACS41][DISCUSS] Adding support for VMware dvSwitch >> >> Why the need for the "vmware.use.dvswitch" if the AddCluster api already >> requires this? > >The purpose of the global parameter "vmware.use.dvswitch" is to use it as >a switch to enable / disable the feature. > >Disable the feature in the sense, >* All the new UI elements related to the feature would not be displayed >if switch is off (parameter is set to 'false') >* All the new API parameters (all have to be optional parameters, if any >of the new parameters introduced are necessary then the feature can't be >hidden/disabled) would be ignored. > >> >> >> On 1/1/13 9:03 PM, "Sateesh Chodapuneedi" >> <sateesh.chodapune...@citrix.com> wrote: >> >> >I have created an initial draft of the FS here, >> >https://cwiki.apache.org/confluence/display/CLOUDSTACK/Integration+of+C >> >lou >> >dStack+with+VMware+DVS >> >I'll keep updating it based on discussion and comments. >> > >> >Regards, >> >Sateesh >> > >> >> -----Original Message----- >> >> From: Sateesh Chodapuneedi [mailto:sateesh.chodapune...@citrix.com] >> >> Sent: 19 December 2012 09:27 >> >> To: cloudstack-dev@incubator.apache.org >> >> Subject: RE: [ACS41][DISCUSS] Adding support for VMware dvSwitch >> >> >> >> Changed category from [ASF41] to [ACS41] in subject line >> >> >> >> > -----Original Message----- >> >> > From: Musayev, Ilya [mailto:imusa...@webmd.net] >> >> > Sent: 18 December 2012 01:33 >> >> > To: cloudstack-dev@incubator.apache.org >> >> > Subject: RE: [ASF41][DISCUSS] Adding support for VMware dvSwitch >> >> > >> >> > Sateesh >> >> > >> >> > As mentioned before I have a good number of vSphere environments >> >> > using dvSwitches that I can't roll into CS just yet. >> >> > >> >> > Whenever you are ready to test something or have a proof of concept >> >> > code to try - I can assist. >> >> > >> >> That would be great! Sure, I will get in touch as soon as the branch >> >> is ready. >> >> Thanks. >> >> >> >> > I've been meaning to ask - are you planning to build any controls >> >> > that are available via VCenter for dvSwitches - or is it strictly >> >> > support and enablement? >> >> >> >> CloudStack will provide the option to choose dvSwitch in VMware >> >> environment and uses vSphere API (talk to vCenter) when a virtual >> >> network needs orchestration (create, modify, destroy cycle). >> >> >> >> > >> >> > Thank you >> >> > -ilya >> >> > >> >> > -----Original Message----- >> >> > From: Sateesh Chodapuneedi [mailto:sateesh.chodapune...@citrix.com] >> >> > Sent: Monday, December 17, 2012 2:41 PM >> >> > To: cloudstack-dev@incubator.apache.org >> >> > Subject: [ASF41][DISCUSS] Adding support for VMware dvSwitch >> >> > >> >> > 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] CLOUDSTACK-657 - "VMware vNetwork Distributed Virtual Switch >> >> > support in CloudStack" >> >> > >> >> > >> >> > >> >> > Regards, >> >> > >> >> > Sateesh >> >> > >> >> > >> >> > >> >> > >> >> > >> > >
