[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-6320: -- Assignee: (was: Kishan Kavala) > Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network > -- > > Key: CLOUDSTACK-6320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver > 6.1.0 > Advanced zone with GRE isolation is configured before upgrade. >Reporter: Florin Dumitrascu > Fix For: 4.4.0, 4.5.0 > > > 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. > Full message thread: > -Original Message- > From: Alena Prokharchyk > Sent: Friday, March 21, 2014 4:18 PM > To: Jessica Wang; Florin Dumitrascu; Murali Reddy > Cc: Nguyen Anh Tu (t...@apache.org); d...@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) > 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" 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); d...@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" > > 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); d...@cloudst
[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-6320: Fix Version/s: (was: 4.4.0) 4.4.3 > Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network > -- > > Key: CLOUDSTACK-6320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver > 6.1.0 > Advanced zone with GRE isolation is configured before upgrade. >Reporter: Florin Dumitrascu > Fix For: 4.5.0, 4.4.3 > > > 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. > Full message thread: > -Original Message- > From: Alena Prokharchyk > Sent: Friday, March 21, 2014 4:18 PM > To: Jessica Wang; Florin Dumitrascu; Murali Reddy > Cc: Nguyen Anh Tu (t...@apache.org); d...@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) > 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" 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); d...@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" > > 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...
[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-6320: Fix Version/s: (was: 4.5.0) 4.5.1 > Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network > -- > > Key: CLOUDSTACK-6320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver > 6.1.0 > Advanced zone with GRE isolation is configured before upgrade. >Reporter: Florin Dumitrascu > Fix For: 4.4.3, 4.5.1 > > > 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. > Full message thread: > -Original Message- > From: Alena Prokharchyk > Sent: Friday, March 21, 2014 4:18 PM > To: Jessica Wang; Florin Dumitrascu; Murali Reddy > Cc: Nguyen Anh Tu (t...@apache.org); d...@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) > 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" 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); d...@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" > > 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...
[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6320: -- Fix Version/s: (was: 4.3.1) 4.4.0 > Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network > -- > > Key: CLOUDSTACK-6320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver > 6.1.0 > Advanced zone with GRE isolation is configured before upgrade. >Reporter: Florin Dumitrascu > Fix For: 4.4.0 > > > 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. > Full message thread: > -Original Message- > From: Alena Prokharchyk > Sent: Friday, March 21, 2014 4:18 PM > To: Jessica Wang; Florin Dumitrascu; Murali Reddy > Cc: Nguyen Anh Tu (t...@apache.org); d...@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) > 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" 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); d...@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" > > 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.or
[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-6320: --- Assignee: Kishan Kavala > Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network > -- > > Key: CLOUDSTACK-6320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver > 6.1.0 > Advanced zone with GRE isolation is configured before upgrade. >Reporter: Florin Dumitrascu >Assignee: Kishan Kavala > Fix For: 4.4.0, 4.5.0 > > > 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. > Full message thread: > -Original Message- > From: Alena Prokharchyk > Sent: Friday, March 21, 2014 4:18 PM > To: Jessica Wang; Florin Dumitrascu; Murali Reddy > Cc: Nguyen Anh Tu (t...@apache.org); d...@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) > 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" 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); d...@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" > > 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...@apach
[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-6320: --- Fix Version/s: 4.5.0 > Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network > -- > > Key: CLOUDSTACK-6320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver > 6.1.0 > Advanced zone with GRE isolation is configured before upgrade. >Reporter: Florin Dumitrascu >Assignee: Kishan Kavala > Fix For: 4.4.0, 4.5.0 > > > 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. > Full message thread: > -Original Message- > From: Alena Prokharchyk > Sent: Friday, March 21, 2014 4:18 PM > To: Jessica Wang; Florin Dumitrascu; Murali Reddy > Cc: Nguyen Anh Tu (t...@apache.org); d...@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) > 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" 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); d...@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" > > 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.o
[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6320: -- Fix Version/s: (was: 4.5.1) 4.5.2 > Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network > -- > > Key: CLOUDSTACK-6320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver > 6.1.0 > Advanced zone with GRE isolation is configured before upgrade. >Reporter: Florin Dumitrascu > Fix For: 4.4.3, 4.5.2 > > > 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. > Full message thread: > -Original Message- > From: Alena Prokharchyk > Sent: Friday, March 21, 2014 4:18 PM > To: Jessica Wang; Florin Dumitrascu; Murali Reddy > Cc: Nguyen Anh Tu (t...@apache.org); d...@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) > 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" 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); d...@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" > > 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...@apa
[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6320: -- Fix Version/s: (was: 4.4.3) 4.4.4 > Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network > -- > > Key: CLOUDSTACK-6320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver > 6.1.0 > Advanced zone with GRE isolation is configured before upgrade. >Reporter: Florin Dumitrascu > Fix For: 4.4.4, 4.5.2 > > > 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. > Full message thread: > -Original Message- > From: Alena Prokharchyk > Sent: Friday, March 21, 2014 4:18 PM > To: Jessica Wang; Florin Dumitrascu; Murali Reddy > Cc: Nguyen Anh Tu (t...@apache.org); d...@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) > 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" 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); d...@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" > > 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...@apa
[jira] [Updated] (CLOUDSTACK-6320) Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6320: -- Fix Version/s: (was: 4.5.2) (was: 4.4.4) > Upgrade 4.1.1 -> 4.3.0 OVS provider should be inserted to the physical network > -- > > Key: CLOUDSTACK-6320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6320 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Upgrading from CS 4.1.1 to CS 4.3.0, using Xenserver > 6.1.0 > Advanced zone with GRE isolation is configured before upgrade. >Reporter: Florin Dumitrascu > > 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. > Full message thread: > -Original Message- > From: Alena Prokharchyk > Sent: Friday, March 21, 2014 4:18 PM > To: Jessica Wang; Florin Dumitrascu; Murali Reddy > Cc: Nguyen Anh Tu (t...@apache.org); d...@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) > 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" 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); d...@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" > > 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); d...@cloudstack.a
