Then its a DB upgrade bug. If the GRE isolation is supported on the network in 4.1.1, DB upgrade should have inserted the provider to physical network.
On 3/21/14, 3:51 PM, "Jessica Wang" <jessica.w...@citrix.com> wrote: >> [Alena] Not exactly like that. >> [Alena] None of the providers are added to the physical network by >>default if execute createPhysicalNetwork call via API. >> [Alena] Our CS UI does this job - adding the providers to the network - >>for you by calling addNetworkServiceProvider call. > >Actually, OVS provider is an exception. >UI doesn't do the job because server-side already does the job. >When you create an Advanced zone in 4.3 code, server-side will >automatically add OVS provider to its physical network. >However, since your zone was created in 4.1 code and upgraded to 4.3, >server-side won't automatically add OVS provider to its physical network. > >Murali, please confirm. > > > >-----Original Message----- >From: Alena Prokharchyk >Sent: Friday, March 21, 2014 2:44 PM >To: Florin Dumitrascu; Jessica Wang; Murali Reddy; Florin Dumitrascu >Cc: Nguyen Anh Tu (t...@apache.org); dev@cloudstack.apache.org >Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is >your zone an Advanced zone or Basic zone? (2) > > > >On 3/21/14, 2:34 PM, "Florin Dumitrascu" ><florin.dumitra...@intunenetworks.com> wrote: > >>Hi, >> >>Alena, my assumption is that the Ovs provider is created when you create >>the physical network with GRE isolation (if someone can confirm ...). >>When I configured CS RC8 from scratch, I could see the provider and >>enable it in the GUI. > >Not exactly like that. None of the providers are added to the physical >network by default if execute createPhysicalNetwork call via API. Our CS >UI does this job - adding the providers to the network - for you by >calling addNetworkServiceProvider call. > > > >>But when I have upgraded from CS 4.1.1 to 4.3.0 RC9, I have preserved the >>existing configuration with the existing physical network. >>So my assumption is that the physical network was not updated with the >>OVS provider (such a provider was not needed in CS 4.1.1). > >So while you were on 4.1.1, GRE isolation was disabled? Did you enable it >on 4.3? If there is a way to enable new isolation on the physical network, >on my opinion - the UI should perform the background call and add all the >providers associated with this option, to the physical network. So it >would be a UI issue. > >Or the case was the following - the GRE isolation was enabled on your >network while on 4.1.1, but new provider - OVS - was added in 4.3. And >this provider wasn’t added to existing physical networks during the >upgrade. Then its a database upgrade bug. > > >Please confirm which one from the above is correct. > >> >>Jessica, I am building CentOS RPM packages from the RC source, using >>"package.sh" script in the source packaging folder. Not aware about the >>difference between "oss" and "noredist". >>Also, my setup is for an advanced zone. >> >>Kind Regards, >>Florin >> >> >> >>-----Original Message----- >>From: Jessica Wang [mailto:jessica.w...@citrix.com] >>Sent: Friday, March 21, 2014 8:28 PM >>To: Florin Dumitrascu; Murali Reddy >>Cc: Nguyen Anh Tu (t...@apache.org); dev@cloudstack.apache.org; Alena >>Prokharchyk >>Subject: RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is >>your zone an Advanced zone or Basic zone? (2) >> >>Florin, >>UI doesn't show OVS service provider because database doesn't have OVS >>service provider. >>The reasons might be: >>(1) You are using oss build (should be using noredist build). >>(2) Your zone is a Basic zone (OVS service provider is only supported in >>Advanced zone) >> >> >>Murali, >>Is there other possibility? >> >> >>Jessica >> >>-----Original Message----- >>From: Jessica Wang >>Sent: Friday, March 21, 2014 1:15 PM >>To: Alena Prokharchyk; Florin Dumitrascu >>Cc: Nguyen Anh Tu (t...@apache.org); Murali Reddy; >>dev@cloudstack.apache.org >>Subject: RE: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) - Is >>your zone an Advanced zone or Basic zone? >> >>Florin, >> >>Is your zone an Advanced zone or Basic zone? >> >>Jessica >> >>-----Original Message----- >>From: Alena Prokharchyk >>Sent: Friday, March 21, 2014 11:53 AM >>To: dev@cloudstack.apache.org; Florin Dumitrascu; Jessica Wang >>Cc: Nguyen Anh Tu (t...@apache.org); Murali Reddy >>Subject: Re: GRE isolation - no in service upgrade (4.1.1 to 4.3.0) >> >>Florin, you have to add the provider to the physical network first, and >>then enable it. To add a provider to physical network, use >>addNetworkServiceProvider. To enable it after, use >>updateNetworkServiceProvider >>. Not sure why our UI doesn¹t have this functionality enabled. Jessica, >>can you check out if the UI supports adding physical network providers, >>and under what conditions? >> >>Thanks, >>Alena. >> >> >>On 3/21/14, 11:47 AM, "Florin Dumitrascu" >><florin.dumitra...@intunenetworks.com> wrote: >> >>>Hi, >>> >>>I have successfully tested GRE isolation with CS 4.3.0 RC8 installed >>>from >>>scratch on a minimal setup. >>> >>>I have moved then on to upgrading a more complex lab setup from CS 4.1.1 >>>to CS 4.3.0 RC9. >>>I have followed the guidelines here for doing the upgrade: >>>http://apache-cloudstack-release-notes.readthedocs.org/en/latest/rnotes. >>>h >>>t >>>ml#upgrade-from-4-1-x-to-4-3 >>> >>>Once CS was back up and running, I have created an OVS network offering >>>using the GUI fix up from >>>https://issues.apache.org/jira/browse/CLOUDSTACK-6162 >>> >>>I tried then to enable the OVS service provider on the physical network, >>>but discovered that no such provider is created. >>>None in the GUI: >>>http://imgur.com/ar8c7sX >>> >>>And none in the database: >>>http://imgur.com/MsIdYrw >>> >>>So this means I pretty much need to re-configure the whole zone from >>>scratch, since I do not know of another way to change the physical >>>networks. >>> >>>If GRE is to be used in the production, this is a major drawback. >>> >>>Any thoughts ? >>> >>>Best Regards, >>>Florin >>> >>> >>>IMPORTANT NOTE: The information in this e-mail (and any attachments) is >>>confidential. The contents may not be disclosed or used by anyone other >>>than the addressee. If you are not the intended recipient, please notify >>>the sender immediately or telephone: +353 (0)1 6204700. We cannot accept >>>any responsibility for the accuracy or completeness of this message as >>>it >>>has been transmitted over a public network. If you suspect that the >>>message may have been intercepted or amended, please call the sender. >> >> >>IMPORTANT NOTE: The information in this e-mail (and any attachments) is >>confidential. The contents may not be disclosed or used by anyone other >>than the addressee. If you are not the intended recipient, please notify >>the sender immediately or telephone: +353 (0)1 6204700. We cannot accept >>any responsibility for the accuracy or completeness of this message as it >>has been transmitted over a public network. If you suspect that the >>message may have been intercepted or amended, please call the sender. >
