<div dir="ltr">Serg,<div>as of 5.1, we do not have an ability to upgrade OpenStack.</div><div><br></div><div>Your case falls into upgrades capabilities. We plan to start working on OpenStack upgrades in 6.0. As of 5.1, we will have an ability to patch environments in terms of maintenance releases, i.e. to lay some patches on your Icehouse code from stable/icehouse. Please do not propose such a large change regarding DB migrations to stable branch, as Fuel will be unable to even patch old envs.</div>
<div><br></div><div>Considering the fact that we can't upgrade Murano Icehouse to Juno, let's focus on preparing Juno code in a way that it supports further upgrades from Juno to K* and following releases.</div></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 23, 2014 at 6:08 PM, Serg Melikyan <span dir="ltr"><<a href="mailto:smelikyan@mirantis.com" target="_blank">smelikyan@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi, Mike,<div><br></div><div>I can't be specific about implementation details due to lack of expertise in Fuel, but to properly handle update of Murano from previous version to MOS 5.1 we need to:</div>
<div>
<ol><li>show warning to the user about deleting all resources managed by Murano (all VMs, networks, etc.. created as part of applications deployment);<br></li><li>remove them;<br></li><li>delete database;<br></li><li>install Murano as usual.<br>
</li></ol></div><div> I worry that first step may be quite hard to implement, here we need expertise from Fuel team. </div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Jul 23, 2014 at 5:53 PM, Mike Scherbakov <span dir="ltr"><<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Serg,<div>what needs to be done in order to include Alembic-related stuff into 5.1? The thing is that we are just a day before Soft Code Freeze.</div>
<div><br></div><div>If this is trivial operation, such as adding a new package and updating configuration file, then we could consider it to be included.</div>
<div><br></div><div>Thanks,</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Wed, Jul 23, 2014 at 5:36 PM, Serg Melikyan <span dir="ltr"><<a href="mailto:smelikyan@mirantis.com" target="_blank">smelikyan@mirantis.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">During this cycle we introduced migrations based on <a href="https://bitbucket.org/zzzeek/alembic" target="_blank">Alembic</a> framework that are incompatible with previous set of migrations based on <a href="https://github.com/stackforge/sqlalchemy-migrate" target="_blank">sqlalchemy-migrate</a>. This changes are going to be included to MOS with release targeting Juno release of Openstack. <div>
<br></div><div>New migration framework makes imposible to seamlessly migrate from previous version of Murano to the next one - all data stored in the database is going to be lost. Murano (as part of MOS) can't be upgraded from any previous version of MOS to MOS 6.0.</div>
<div><br></div><div>I suggest to include this feature (migrations based on Alembic) to MOS as soon as possible, to be precise to MOS 5.1. This will allow to have upgrades for Murano from MOS 5.1 to all the next versions of MOS, including 6.0. Upgrade from 5.0.1 to 5.1 for Murano without loosing all data will be impossible. <span><font color="#888888"><div>
-- <br><div dir="ltr"><div>Serg Melikyan, Senior Software Engineer at Mirantis, Inc.<br></div><div><a href="http://mirantis.com/" target="_blank">http://mirantis.com</a> | <a href="mailto:smelikyan@mirantis.com" target="_blank">smelikyan@mirantis.com</a><br>
<div><br>+7 (495) 640-4904, 0261</div><div>+7 (903) 156-0836</div></div></div>
</div></font></span></div></div>
<br></div></div>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Mike Scherbakov<br>#mihgen<br><br></div>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Serg Melikyan, Senior Software Engineer at Mirantis, Inc.<br></div><div><a href="http://mirantis.com/" target="_blank">http://mirantis.com</a> | <a href="mailto:smelikyan@mirantis.com" target="_blank">smelikyan@mirantis.com</a><br>
<div><br>+7 (495) 640-4904, 0261</div><div>+7 (903) 156-0836</div></div></div>
</div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Mike Scherbakov<br>#mihgen<br><br></div>
</div>