On 11/12/2016 08:10 AM, William Josefsson wrote:
Thanks Jay and Matt for sharing advice on the upgrade. I have found
the following documentation for each of the projects, I believe I
should also read the upgrade section in each projects release notes.
Can you please advice if the service DB upgrade order as below makes
sense, not sure what to do with the rabbitmq service?
You don't need to upgrade RabbitMQ if you don't want to. There's some
performance and reliability fixes (for at-scale deployments) in later
rabbitmq and erlang packages but for the size of your deployment I'm not
sure it would be particularly useful to upgrade rabbitmq.
I was looking for something more guided step by step upgrade, and
found these two links. Please share if you've seen any useful upgrade
posts covering Liberty->Mitaka; Mitaka->Newton. thx will
The process for upgrading from Liberty to Mitaka is the same as the
process for upgrading from Mitaka to Newton.
The best guide to follow is the Nova upgrade documentation, which you
link to below:
http://docs.openstack.org/developer/nova/upgrade.html#
Follow that and you should be 90% of the way there. Upgrading the
controller services like Keystone, Glance, Cinder (on the controller,
not the cinder-volume services on the compute nodes), Heat, etc should
be simple: shut down the services, upgrade the packages, run db syncs,
restart the services. Upgrading the compute nodes is the trickier part,
but the doc above gives a great rundown of what you should do.
Of course, make a backup of your database(s) before you do anything.
All the best,
-jay
http://people.redhat.com/~lkellogg/rhos7-upgrade-docs/upgrade-1.html
http://www.hellovinoth.com/upgrading-openstack-lets-give-it-a-try/
1. Keystone, http://docs.openstack.org/developer/keystone/upgrading.html
2. Glance, Missing upgrade documentation?
http://docs.openstack.org/developer/glance/
3. Nova, http://docs.openstack.org/developer/nova/upgrade.html#
4. Neutron, http://docs.openstack.org/developer/neutron/devref/upgrade.html#
5. Cinder,
http://docs.openstack.org/developer/cinder/devref/rolling.upgrades.html#
On Sat, Nov 12, 2016 at 9:13 AM, Matt Riedemann
<mrie...@linux.vnet.ibm.com> wrote:
On 11/11/2016 9:45 AM, Jay Pipes wrote:
On 11/11/2016 08:38 AM, William Josefsson wrote:
Hi everyone, I have been quite concerned about how to migrate 50
projects and total 100 instances on Liberty/CentOS72, to Newton.
My storage backend is CEPH. Can anyone advice if I can as a safe
migration path, do a fresh install of Newton on additional hardware.
The new Newton cluster connecting to same old DB and Storage(CEPH
cluster). And then live-migrate to the new hardware?
Please advice if this approach works. Thx will
The only safe and supported way to upgrade OpenStack is to do an N-1 to
N upgrade.
Upgrade your controller installation to Mitaka, run your migrations (DB
and online data migrations) then upgrade all of your nova-compute nodes
one by one from Liberty to Mitaka. You will not need to live-migrate any
workloads unless you simultaneously want to upgrade either the operating
system or the libvirt/QEMU versions on the nova-computes.
Rinse and repeat to get to Newton.
There's many guides online for how to do upgrades of OpenStack. Please
follow one of them to perform a best practice N-1 to N upgrade.
Best,
-jay
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
The nova docs on rolling upgrades were also recently updated:
http://docs.openstack.org/developer/nova/upgrade.html#minimal-downtime-upgrade-process
--
Thanks,
Matt Riedemann
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
