Re: [openstack-dev] Upgrade skip release

[Matt Riedemann]

On 12/19/2016 4:26 PM, Chris Friesen wrote:

On 12/19/2016 03:17 PM, Ajay Kalambur (akalambu) wrote:

Hi Chris
Thanks for the response. What were the specific problem areas you saw
when upgrading from Kilo to Mitaka which were introduced by skipping
Liberty?


There were issues with RPC incompatibility, object versioning, DB
upgrades, etc.

Liberty had compatibility code for this stuff, but then it got ripped
out early in Mitaka since it was assumed to be no longer needed.

Chris

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Right, it's not only about database schema migrations anymore, which in 
the before times you could generally just roll those forward and skip a 
release.


Nova has been doing online data migrations since Kilo, and assumptions 
are made that you're doing lock-step N to N+1 upgrades and running the 
schema and online data migrations, and rolling services forward in that 
fashion so that we can drop compatibility code after a full release of 
that compat code being in place.


We only test N to N+1 in the CI system (the grenade jobs) so while 
things might work in practice by skipping a release, it's not tested 
that way upstream at all so any chance of it working is accidental and 
shouldn't be relied upon or really expected to be supported that way 
upstream.


--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Upgrade skip release

[Chris Friesen]

On 12/19/2016 03:17 PM, Ajay Kalambur (akalambu) wrote:

Hi Chris
Thanks for the response. What were the specific problem areas you saw when 
upgrading from Kilo to Mitaka which were introduced by skipping Liberty?


There were issues with RPC incompatibility, object versioning, DB upgrades, etc.

Liberty had compatibility code for this stuff, but then it got ripped out early 
in Mitaka since it was assumed to be no longer needed.


Chris

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Upgrade skip release

[Ajay Kalambur (akalambu)]

Hi Chris
Thanks for the response. What were the specific problem areas you saw when 
upgrading from Kilo to Mitaka which were introduced by skipping Liberty?
Ajay




On 12/19/16, 12:36 PM, "Chris Friesen"  wrote:

>On 12/19/2016 01:56 PM, Ajay Kalambur (akalambu) wrote:
>> Hi
>> Does openstack support skipping releases if one is performing a maintanance
>> upgrade. Would alembic migrations work for instance from Liberty to Newton
>
>OpenStack as a whole only supports N to N+1 upgrades, though it's possible 
>some 
>services may support more than that.
>
>We did Kilo->Mitaka for various reasons and had to resolve a bunch of problems.
>
>Chris
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Upgrade skip release

[Chris Friesen]

On 12/19/2016 01:56 PM, Ajay Kalambur (akalambu) wrote:

Hi
Does openstack support skipping releases if one is performing a maintanance
upgrade. Would alembic migrations work for instance from Liberty to Newton


OpenStack as a whole only supports N to N+1 upgrades, though it's possible some 
services may support more than that.


We did Kilo->Mitaka for various reasons and had to resolve a bunch of problems.

Chris

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev