Open Stack

We¹re almost complete with this process, we¹re moving from icehouse to
kilo.

Certainly for nova, I was able to jump directly from I->K however, I did
have to deal with lots of weird issues that ended up with me having to
update the computes at the same time as the controllers.

With regards to upgrade levels, I found the docs to be a little
incomplete, I also found that certain components (e.g nova-cert) didn¹t
take a release name as per the docs and required an RPC version number.

Watch out, you¹ll need to refactor your configs quite a bit, things have
been moved into different stanza¹s, new options added.

From:  Melvin Hillsman <mrhillsman at gmail.com>
Date:  Wednesday, June 15, 2016 at 8:07 AM
To:  Saverio Proto <zioproto at gmail.com>
Cc:  OpenStack Operators <openstack-operators at lists.openstack.org>
Subject:  Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka


+1 on Saverio's response. You will want to upgrade to Mitaka by NOT
jumping releases; J - K - L - M not J - M

On Wed, Jun 15, 2016 at 4:13 AM, Saverio Proto
<zioproto at gmail.com> wrote:

Hello,

first of all I suggest you read this article:
http://superuser.openstack.org/articles/openstack-upgrading-tutorial-11-pit
falls-and-solutions

> What is the best way to performe an upgrade from Juno to Mitaka?

I would go for the in place upgrade, but I always upgraded without
jumping version, that AFAIK is not supported.

The main problem I see, is that database migrations are supported when
you upgrade to the next release, but if you jump form Juno to Mitaka I
have to idea how the database upgrade cloud be done.

Saverio

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