Hi Sateesh, Did not realise unitl I started looking at the code that you contributed greatly to it, great to get reply from you. I have done some investigation around the VmwareManagerImpl.java which uses this configuration and see that change was made for 4.2 branch, sadly.
Do you have any feedback on version 4.1 Thanks Noel On 20 June 2013 18:27, Noel King <noelk...@gmail.com> wrote: > Hi Sateesh, > > Sorry replied too quick from phone when I away from my desk, Are those > global config changes in 4.1 as well as I dont see them but will have a > quick search in docs for them. > > "private.network.vswitch.name > "public.network.vswitch.name" > "guest.network.vswitch.name" > > Thanks > Noel > > > On 20 June 2013 18:19, Noel King <noelk...@gmail.com> wrote: > >> Apologies if I did not state that, but had restarted the management >> server and error message sent was after the restart. So looks like its not >> picking up the change. >> >> thanks >> >> Noel >> On Jun 20, 2013 6:16 p.m., "Sateesh Chodapuneedi" < >> sateesh.chodapune...@citrix.com> wrote: >> >>> > -----Original Message----- >>> > From: Noel King [mailto:noelk...@gmail.com] >>> > Sent: 20 June 2013 22:37 >>> > To: dev@cloudstack.apache.org >>> > Subject: Re: VMWare changing the default vSwitch Name >>> > >>> > Hi Sateesh >>> > >>> > Thanks for your reply, I have made those changes and restarted but >>> with no joy and am still seeing vSwitch0 being used in the log and my >>> > portgroup is returning "Message: Uable to find management port group >>> MyPortGroup" >>> > >>> > INFO [vmware.resource.VmwareResource] (ClusteredAgentManager Timer:) >>> VmwareResource network configuration info. private >>> > vSwitch: vSwitch0, public vSwitch: vSwitch0, guest network: vSwitch0 >>> > >>> > Any further insight would be greatly appreciated. >>> >>> Can you set following global configuration parameters based on the >>> traffic type? >>> "private.network.vswitch.name >>> "public.network.vswitch.name" >>> "guest.network.vswitch.name" >>> >>> Need to restart management server once these parameters are modified. >>> Hope that helps! >>> >>> Regards, >>> Sateesh >>> >>> > >>> > Kind regards >>> > >>> > Noel >>> > >>> > >>> > >>> > On 20 June 2013 17:42, Sateesh Chodapuneedi < >>> sateesh.chodapune...@citrix.com >>> > > wrote: >>> > >>> > > > -----Original Message----- >>> > > > From: Noel King [mailto:noelk...@gmail.com] >>> > > > Sent: 20 June 2013 20:16 >>> > > > To: dev@cloudstack.apache.org >>> > > > Subject: VMWare changing the default vSwitch Name >>> > > > >>> > > > Hi All, >>> > > > >>> > > > I am currently working on a Cloudstack VMWare integration project >>> > > > and we >>> > > have setup up a dedicated vSwitch and PortGroup for >>> > > > cloudstack. >>> > > > >>> > > > On reading the VMware vSphere Installation and Configuration ( >>> > > http://cloudstack.apache.org/docs/en- >>> > > > US/Apache_CloudStack/4.0.2/html/Installation_Guide/ >>> vmware-install.ht >>> > > > ml >>> > > > ) I see the following advise: >>> > > > >>> > > > 8.3.5.1. Configure Virtual Switch >>> > > > A default virtual switch vSwitch0 is created. CloudStack requires >>> > > > all >>> > > ESXi hosts in the cloud to use the same set of virtual switch names. >>> > > If >>> > > > you change the default virtual switch name, you will need to >>> > > > configure >>> > > one or more CloudStack configuration variables as well. >>> > > > >>> > > > Would you mind explaining *"you will need to configure one or more >>> > > CloudStack configuration variables as well*." What settings these are >>> > > > and where they can be changed. >>> > > >>> > > Edit the physical network traffic label to specify the vswitch name >>> to >>> > > be used for particular traffic. >>> > > Ex: If you would like to use "vSwitch2" for guest traffic then edit >>> > > the guest network traffic label as "vSwitch2". >>> > > >>> > > > >>> > > > Kind regards >>> > > > >>> > > > Noel >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > Kind regards, >>> > > > >>> > > > Noel >>> > > >>> >> >
