Open Stack

Hi, Mike,

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:

   1. show warning to the user about deleting all resources managed by
   Murano (all VMs, networks, etc.. created as part of applications
   deployment);
   2. remove them;
   3. delete database;
   4. install Murano as usual.

 I worry that first step may be quite hard to implement, here we need
expertise from Fuel team.



On Wed, Jul 23, 2014 at 5:53 PM, Mike Scherbakov <mscherbakov at mirantis.com>
wrote:

> Hi Serg,
> 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.
>
> If this is trivial operation, such as adding a new package and updating
> configuration file, then we could consider it to be included.
>
> Thanks,
>
>
> On Wed, Jul 23, 2014 at 5:36 PM, Serg Melikyan <smelikyan at mirantis.com>
> wrote:
>
>> During this cycle we introduced migrations based on Alembic
>> <https://bitbucket.org/zzzeek/alembic> framework that are incompatible
>> with previous set of migrations based on sqlalchemy-migrate
>> <https://github.com/stackforge/sqlalchemy-migrate>. This changes are
>> going to be included to MOS with release targeting Juno release of
>> Openstack.
>>
>> 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.
>>
>> 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.
>> --
>> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>> http://mirantis.com | smelikyan at mirantis.com
>>
>> +7 (495) 640-4904, 0261
>> +7 (903) 156-0836
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Mike Scherbakov
> #mihgen
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelikyan at mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140723/52c37293/attachment.html>