Ask Your Question
0

How to upgrade between releases

asked 2018-09-24 06:26:15 -0500

dendvk gravatar image

updated 2018-09-24 06:28:04 -0500

Hello.

Recent upgrade from Pike to Queens of my stack wasn't smooth, but after dance with yum ( -e centos-release-openstack-pike, -i centos-release-openstack-queens, "missing requires" and so so on) it finally happen and even works.

But upgrade from Queens to Rocky was terrible. Just having new repo installed (# yum install -y centos-release-openstack-rocky) and upgrading packages (# yum update -y) lead me to the situation with 1) database inconsistency; 2) absence of listener of keystone port 35357 for admin/internal endpoints.

After some digging I've fixed DB structure, and after reading keystone RNs - remapped all endpoints to 5000 port (by direct UPDATE in MySQL!! - the only way I could imagine).

But something deep inside me telling that I was just lucky several times and likely that I've done upgrade completely incorrectly.

My stack consists of one Controller node and several Compute nodes, and all of them were installed using official instructions and via yum (i.e. no automated-deployment tools). Digging into documentation, googling, asking Lord does not shed light to the main question - How to upgrade OpenStack nodes between releases in correct way? May be I missed something just near me? Please help.

edit retag flag offensive close merge delete
add a comment

1 answer

Sort by ยป oldest newest most voted
0

answered 2018-09-24 18:23:42 -0500

Bernd Bausch gravatar image

I am not sure if this can be counted as an answer. Generally, you should not jump over a release, that is, Pike->Rocky is dangerous or simply not possible without going through Queens. Tripleo seems to champion what they call fast-forward upgrades (see this Superuser article and this spec, for example), but it's definitely not mainstream yet.

Individual projects have their upgrade pages, e.g. Nova, Neutron, Cinder, Heat. To me, this is not quite satisfactory, as there seems to be no information about upgrading a cloud as a whole, and those pages are scattered and have to be found in the first place. Having said that, googling for them was not too hard.

In addition to these upgrade pages, release notes contain a section with upgrade instructions specific to the release in question. Again, this is per project, e.g. Nova; it would be great to have the information centralized.

You can also get inspiration from commercial OpenStack distros, e.g. SUSE. At a high level, the process mentioned there should be generally applicable.

Finally, there are quite a few summit videos where operators talk about their upgrade experience and tips and tricks.

Disclaimer: I consider my main competence to be finding information, not upgrading.

edit flag offensive delete link more

Comments

Bernd, thank you for your answer.

Yes, indeed, upgrade over one or several releases is the best way to potentially re-deploy your cloud from scratch. And also, I found release notes per project, and they were really helpful, f.e., to figure out the Keystone port changes. To be continuing...

dendvk gravatar imagedendvk ( 2018-09-25 01:14:08 -0500 )edit

Btw, if there aren't cumulative RNs for OpenStack in the whole, let consider this as Feature Request. But for me, this is a bug. Every RPM have pre- and post- sections, which are great for upgrade scripts, imho, like this "# su -s /bin/sh -c "nova-manage api_db sync" nova"...

dendvk gravatar imagedendvk ( 2018-09-25 01:17:05 -0500 )edit

Hi bernad, My stack runs on openstack KILO, consisting of 1 controller(vm) and 4 compute physical nodes.

They want is to upgrade it to rocky version, how do i do it? i cannot find any docs that explains this procedure.

John Bernad gravatar imageJohn Bernad ( 2018-11-27 05:16:38 -0500 )edit

There is no supported method to go from Kilo to Rocky in one step, and probably no unsupported method either. You need to go release by release. If you can afford downtime, I would save instances, images, volumes etc and just reinstall the cloud.

Disclaimer: As above.

Bernd Bausch gravatar imageBernd Bausch ( 2018-11-27 05:23:06 -0500 )edit

So you mean to say, leave the existing stack as it is and build another stack with rocky and migrate the instances images volumes etc?

John Bernad gravatar imageJohn Bernad ( 2018-11-27 05:28:29 -0500 )edit
see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2018-09-24 06:26:15 -0500

Seen: 441 times

Last updated: Sep 24 '18

Related questions

devstack Queens: Tacker, cannot delete VNF

Rocky: nova-status upgrade check fails - no compute resource providers in Placement Service

devstack queens : multiple uwsgi processes consuming CPU

Provider network not working !!?

Time duration Tripleo upgrade between Queens to Rocky

Query Openstack Time

gnocchi-upgrade -v crashes with ImportError: cannot import name EncryptedType

Packstack upgrades

Rocky Neutron does not work per installation guide [closed]

openstack FWaaS