Open Stack

Hello Saverio,
 
thank you for the link, I will have a look at this article.
 
In place upgrade would be the best way, becaus we do not have to setup
everything from scratch again, also at the moment it would be no problem to make
a new installation because there is not much data by now in our installation
only a few projects. But in the future we will have mor data, and the next
upgrade will come sometimes so then we have the same problems and it would be
nice not to have setup everything again.
 
So I think we will try to save the data and go for an in place upgrade first and
see how it works out.
 
Is this one the actual guid for upgrades, and is it valid for every upgrade or
ony for specific versions?:
http://docs.openstack.org/ops-guide/ops_upgrades.html
 
 
Kind regards,
Michael
 

> Saverio Proto <zioproto at gmail.com> hat am 15. Juni 2016 um 11:13 geschrieben:
>
>
> Hello,
>
> first of all I suggest you read this article:
> http://superuser.openstack.org/articles/openstack-upgrading-tutorial-11-pitfalls-and-solutions
>
> > What is the best way to performe an upgrade from Juno to Mitaka?
>
> I would go for the in place upgrade, but I always upgraded without
> jumping version, that AFAIK is not supported.
>
> The main problem I see, is that database migrations are supported when
> you upgrade to the next release, but if you jump form Juno to Mitaka I
> have to idea how the database upgrade cloud be done.
>
> Saverio
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160616/151b8389/attachment.html>