Open Stack

I agree with all said below.
The Ops guide is also talking about this case : should you want to 
upgrade, there are a certain steps to follow (ie. which components to 
upgrade *before* others).

Anyway, this is not a out-of-the-box upgrade. I strongly recommend to 
deploy an Openstack testing environment (with virtualized instances it 
does work, provided your hypervisor being QEMU) quite identical as your 
production environment, and do the upgrade against the test env.

This is the best way for preventing quite an emergency.

-Sylvain

Le 29/03/2013 15:52, Razique Mahroua a écrit :
> +1
> We don't have any out-of-the-box migration plan, thing is depending on 
> your setup, there are many cases that cannot be anticipated.
> Before trying anything, if you use a database for the data, make sure 
> to dump it before
> Regards,
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahroua at gmail.com <mailto:razique.mahroua at gmail.com>
> Tel : +33 9 72 37 94 15
>
>
> Le 29 mars 2013 à 15:31, Jacob Godin <jacobgodin at gmail.com 
> <mailto:jacobgodin at gmail.com>> a écrit :
>
>> Are you running ubuntu cloud ppa? If so, you're best off waiting for 
>> the official release. Ubuntu tests the upgrade process with their ppa 
>> before releasing.
>>
>> On 2013-03-29 11:29 AM, "Baktha" <baktha.sg at gmail.com 
>> <mailto:baktha.sg at gmail.com>> wrote:
>>
>>     Hi guys,
>>
>>      We have a fully working Folsom testing environment, with 10
>>     running instances. I would like to upgrade my Folsom to grizzly
>>     without disturbing the setup... Is it possible?
>>     I tried updating the test grizzly package and it doesn't seems to
>>     be working please guide me
>>     Sent from my iPhone
>>     _______________________________________________
>>     OpenStack-operators mailing list
>>     OpenStack-operators at lists.openstack.org
>>     <mailto:OpenStack-operators at lists.openstack.org>
>>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org 
>> <mailto:OpenStack-operators at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130329/e95ff17f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 10122 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130329/e95ff17f/attachment.jpe>