<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div dir="ltr" >I'll offer a counter point.</div>
<div dir="ltr" > </div>
<div dir="ltr" >We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping over Liberty.</div>
<div dir="ltr" > </div>
<div dir="ltr" >The database migrations to get from Kilo to Mitaka have ran smoothly for us.</div>
<div dir="ltr" > </div>
<div dir="ltr" ><a href="https://github.com/blueboxgroup/ursula/blob/master/upgrade.yml" >https://github.com/blueboxgroup/ursula/blob/master/upgrade.yml</a></div>
<div dir="ltr" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div dir="ltr" style="margin-top: 20px;" ><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" >-jlk</font></div></div></div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<blockquote data-history-content-modified="1" dir="ltr" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: Melvin Hillsman <mrhillsman@gmail.com><br>To: Saverio Proto <zioproto@gmail.com><br>Cc: OpenStack Operators <openstack-operators@lists.openstack.org><br>Subject: Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka<br>Date: Wed, Jun 15, 2016 8:11 AM<br> 
<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> 
<div>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:

<blockquote 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><br><span>> What is the best way to performe an upgrade from Juno to Mitaka?</span><br><br>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" target="_blank" >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></blockquote></div></div>
<div><font face="Default Monospace,Courier New,Courier,monospace" size="2" >_______________________________________________<br>OpenStack-operators mailing list<br>OpenStack-operators@lists.openstack.org<br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank" >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></font></div></blockquote>
<div dir="ltr" > </div></div><BR>