Re: [Openstack-operators] Kilo ->-> Mitaka anyone have notes :)

[Jesse Keating]

That's strange, this very command has worked for every environment we've tried, Kilo -> Mitaka. No errors, successful appearing migration, continued Nova operation after the fact.
 
Maybe I'm missing something. I realize it's untested, but the sync command does not fail.
-jlk
 
 
- Original message -From: Andrew Laski <and...@lascii.com>To: openstack-operators@lists.openstack.orgCc:Subject: Re: [Openstack-operators] Kilo ->-> Mitaka anyone have notes :)Date: Mon, Jun 27, 2016 5:35 AM 
On Sun, Jun 26, 2016, at 07:58 PM, Sam Morrison wrote:> I’ve done kilo -> mitaka with Keystone and all worked fine. Nothing> special I needed to do.>> If you’re wanting to do live upgrades with nova you can’t skip a version> from my understanding.Correct. Not without doing the work yourself to make it possible, andrealizing that it's untested/unsupported and likely will bring outgremlins.In order to make db migrations less painful, i.e. faster, Nova moved toa system where only schema changes occur in the sqlalchemy-migratemigrations and all data is migrated by another nova-manage command whichcan be run while the system is in use. But the side effect of this isthat the data migration needs to take place for each release, and thereare checks in place to ensure this happens. Unless you have an emptydatabase "nova-manage db sync" won't even complete successfully forkilo->mitaka since there's a check in place to ensure the liberty datamigration took place.>> Sam>>> > On 25 Jun 2016, at 4:16 AM, Jonathan Proulx <j...@csail.mit.edu> wrote:> >> > Hi All,> >> > I about to start testing for our Kilo->Mitaka migration.> >> > I seem to recall many (well a few at least) people who were looking to> > do a direct Kilo to Mitaka upgrade (skipping Liberty).> >> > Blue Box apparently just did and I read Stefano's blog[1] about it,> > and while it gives me hope my plan is possible it's not realy a> > technical piece.> >> > I'm on my 7th version of OpenStack for this cloud now so not my first> > redeo as they say, but other than read Liberty and Mitaka release> > notes carefully and test like crazy wonder if anyone has seen specific> > issues or has specific advice for skiping a step here?> >> > Thanks,> > -Jon> >> > --> > [1] https://www.dreamhost.com/blog/2016/06/21/dreamcompute-goes-m-for-mitaka-without-unleashing-the-dragons/> >> > ___> > OpenStack-operators mailing list> > OpenStack-operators@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>>> ___> OpenStack-operators mailing list> OpenStack-operators@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators___OpenStack-operators mailing listOpenStack-operators@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
 


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Kilo ->-> Mitaka anyone have notes :)

[Andrew Laski]

On Sun, Jun 26, 2016, at 07:58 PM, Sam Morrison wrote:
> I’ve done kilo -> mitaka with Keystone and all worked fine. Nothing
> special I needed to do.
> 
> If you’re wanting to do live upgrades with nova you can’t skip a version
> from my understanding.

Correct. Not without doing the work yourself to make it possible, and
realizing that it's untested/unsupported and likely will bring out
gremlins.

In order to make db migrations less painful, i.e. faster, Nova moved to
a system where only schema changes occur in the sqlalchemy-migrate
migrations and all data is migrated by another nova-manage command which
can be run while the system is in use. But the side effect of this is
that the data migration needs to take place for each release, and there
are checks in place to ensure this happens. Unless you have an empty
database "nova-manage db sync" won't even complete successfully for
kilo->mitaka since there's a check in place to ensure the liberty data
migration took place.

> 
> Sam
> 
> 
> > On 25 Jun 2016, at 4:16 AM, Jonathan Proulx  wrote:
> > 
> > Hi All,
> > 
> > I about to start testing for our Kilo->Mitaka migration.
> > 
> > I seem to recall many (well a few at least) people who were looking to
> > do a direct Kilo to Mitaka upgrade (skipping Liberty).
> > 
> > Blue Box apparently just did and I read Stefano's blog[1] about it,
> > and while it gives me hope my plan is possible it's not realy a
> > technical piece.
> > 
> > I'm on my 7th version of OpenStack for this cloud now so not my first
> > redeo as they say, but other than read Liberty and Mitaka release
> > notes carefully and test like crazy wonder if anyone has seen specific
> > issues or has specific advice for skiping a step here?
> > 
> > Thanks,
> > -Jon
> > 
> > -- 
> > [1] 
> > https://www.dreamhost.com/blog/2016/06/21/dreamcompute-goes-m-for-mitaka-without-unleashing-the-dragons/
> > 
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> 
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Kilo ->-> Mitaka anyone have notes :)

[Sam Morrison]

I’ve done kilo -> mitaka with Keystone and all worked fine. Nothing special I 
needed to do.

If you’re wanting to do live upgrades with nova you can’t skip a version from 
my understanding.

Sam


> On 25 Jun 2016, at 4:16 AM, Jonathan Proulx  wrote:
> 
> Hi All,
> 
> I about to start testing for our Kilo->Mitaka migration.
> 
> I seem to recall many (well a few at least) people who were looking to
> do a direct Kilo to Mitaka upgrade (skipping Liberty).
> 
> Blue Box apparently just did and I read Stefano's blog[1] about it,
> and while it gives me hope my plan is possible it's not realy a
> technical piece.
> 
> I'm on my 7th version of OpenStack for this cloud now so not my first
> redeo as they say, but other than read Liberty and Mitaka release
> notes carefully and test like crazy wonder if anyone has seen specific
> issues or has specific advice for skiping a step here?
> 
> Thanks,
> -Jon
> 
> -- 
> [1] 
> https://www.dreamhost.com/blog/2016/06/21/dreamcompute-goes-m-for-mitaka-without-unleashing-the-dragons/
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Kilo ->-> Mitaka anyone have notes :)

[Xav Paice]

FWIW, I did that with Cinder and it was great except for one DB change we
had to make regarding the server name for volumes -
http://dischord.org/2015/12/22/cinder-multi-backend-with-multiple-ceph-pools/
is a pretty good description of what I saw.  I suspect that was just a poor
configuration from our Kilo setup rather than a change specifically related
to the upgrade, but the upgrade brought it to light.

Haven't yet taken the same step with others, we're doing the upgrades one
thing at a time and for some (Nova) we'll be jumping through Liberty
because of the risk of jumping two steps at a time.

On 25 June 2016 at 06:16, Jonathan Proulx  wrote:

> Hi All,
>
> I about to start testing for our Kilo->Mitaka migration.
>
> I seem to recall many (well a few at least) people who were looking to
> do a direct Kilo to Mitaka upgrade (skipping Liberty).
>
> Blue Box apparently just did and I read Stefano's blog[1] about it,
> and while it gives me hope my plan is possible it's not realy a
> technical piece.
>
> I'm on my 7th version of OpenStack for this cloud now so not my first
> redeo as they say, but other than read Liberty and Mitaka release
> notes carefully and test like crazy wonder if anyone has seen specific
> issues or has specific advice for skiping a step here?
>
> Thanks,
> -Jon
>
> --
> [1]
> https://www.dreamhost.com/blog/2016/06/21/dreamcompute-goes-m-for-mitaka-without-unleashing-the-dragons/
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators