<div dir="ltr">+1 on Saverio's response. You will want to upgrade to Mitaka by NOT jumping releases; J - K - L - M not J - M </div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 15, 2016 at 4:13 AM, Saverio Proto <span dir="ltr"><<a href="mailto:zioproto@gmail.com" target="_blank">zioproto@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
first of all I suggest you read this article:<br>
<a href="http://superuser.openstack.org/articles/openstack-upgrading-tutorial-11-pitfalls-and-solutions" rel="noreferrer" target="_blank">http://superuser.openstack.org/articles/openstack-upgrading-tutorial-11-pitfalls-and-solutions</a><br>
<span class=""><br>
> What is the best way to performe an upgrade from Juno to Mitaka?<br>
<br>
</span>I would go for the in place upgrade, but I always upgraded without<br>
jumping version, that AFAIK is not supported.<br>
<br>
The main problem I see, is that database migrations are supported when<br>
you upgrade to the next release, but if you jump form Juno to Mitaka I<br>
have to idea how the database upgrade cloud be done.<br>
<br>
Saverio<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote></div><br></div>