[Openstack-operators] [openstack-dev] [OpenStack-Ansible] Mitaka Upgrade

Kevin Carter kevin.carter at RACKSPACE.COM
Tue May 3 03:35:19 UTC 2016

Hi Wade, sorry for the late reply most of us have been traveling / afk for a bit for the summit. Regarding Liberty > Mitaka upgrades there are a few issues that we need to work out before we have a supported upgrade process.

Most notably we need to address:

* https://bugs.launchpad.net/openstack-ansible/+bug/1577245

* https://bugs.launchpad.net/openstack-ansible/+bug/1568029

* https://bugs.launchpad.net/openstack-ansible/+bug/1574019

* https://bugs.launchpad.net/openstack-ansible/+bug/1574303

It's likely if you hand fix these items you should be all taken care of. That said, work will be in full swing in the next week or so to get upgrades 100% squared away and there may be some other things that need be addressed before we'd say they're fully supported.

As for the RTFM part, it's not RTFM at all. We generally give our releases a bit of time to stabilize before announcing to the world how "wonderful our upgrade process is". Sadly, the issues you've found are a product of us not having worked everything out yet. We do have some documentation regarding the minor upgrade process as outlined here: [0] as well as other operational documentation that can be found here: [1]. Also if you're interested in working on the upgrades we'd love to have a chat regarding all of the things you've run into so that we can automate them away. I'd recommend joining in on the #openstack-ansible IRC channel and potentially raising issues on launchpad [2] for things we've not yet thought of to work on.

As for what you've done thus far, it seems like a sensible approach. The playbook execution should drop new code into place and start/restart all of the services. However the straggler process may have been related to this issue [ https://bugs.launchpad.net/openstack-ansible/+bug/1577245 ] if you can look through that and the other issues mentioned earlier we'd appreciate the feedback.

Sorry for the TL;DR I hope you're well. Ping us if you have questions.

[0] - http://docs.openstack.org/developer/openstack-ansible/install-guide/app-minorupgrade.html
[1] - http://docs.openstack.org/developer/openstack-ansible/install-guide/#operations
[2] - https://bugs.launchpad.net/openstack-ansible/


Kevin Carter
IRC: cloudnull

From: Wade Holler <wade.holler at gmail.com>
Sent: Thursday, April 28, 2016 11:33 AM
To: OpenStack Operators; OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Openstack-operators] [OpenStack-Ansible] Mitaka Upgrade

Hi All,

If this is RTFM please point me there and I apologize.

If not:

We are testing the Liberty to Mitaka transition with OSAD.  Could someone please advise if these were the correct general steps.

osad multinode (VMs/instances inside a osad cloud) built with latest 12.X liberty osad
1. save off config files: openstack_user_config.yml, user_variables,yml, ...hostname..., inventory,  etc.
2. rm -rf /etc/openstack_deploy; rm -rf /opt/openstack-ansible
3. git clone -b stable/mitaka ....
4. copy config files back in place
5. ./scripts/bootstrap-ansible.sh
6. openstack-ansible setup-everything.yml

That is the process we ran and it appears to have went well after adding the "-e rabbit_upgrade=true" flag.

Only straggler process that I found so far was a neutron-ns-metadata-proxy that was still running 12.X liberty code.  restarted the container and it didn't start again, but the 13.X mitaka version is running ( and was before shutdown ).

Is this the correct upgrade process or are there other steps / approaches that should be taken ?

Best Regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160503/261cabd7/attachment.html>

More information about the OpenStack-operators mailing list