+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 <ziopr...@gmail.com> wrote: > Hello, > > first of all I suggest you read this article: > > http://superuser.openstack.org/articles/openstack-upgrading-tutorial-11-pitfalls-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@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
