Updating Openstack from Pike non-containerised to something current

Tony Pearce tony.pearce at cinglevue.com
Tue Jan 21 09:16:54 UTC 2020


I am planning to upgrade my Openstack Pike. Please could I ask some
questions about this so I understand better how to proceed?

*Background*:
- I have Openstack Pike running on 3 nodes (2 x compute and 1 x
controller). Storage is provided by a Cinder driver and separate vendor
storage array (iSCSI).

- I have a bug which is impacting Cinder in Pike which is not present in
Queens/Stein.

- Since I installed Openstack some years ago, I was not able to
update/patch it for a number of reasons.

- The Openstack which I installed was from the tripleo.org website and I
followed the instructions there.

- I have configured LBaaS that was available in Pike by making config
changes to .conf files.

-  I recall reading a few months ago when I started looking into this that
I need to update to the latest within the current version (Pike) first,
before updating beyond Pike so I am planning for that.


*Questions*:
1. do I first need to deconfigure / remove the LBaaS before attempting an
upgrade beyond Pike?
2. The tripleo website is a little confusing. I am running Pike and it is
not containerised. The upgrade info on tripleo.org mentions upgrades to
Pike in a containerised environment. So should I follow the detail for the
"Ocata and earlier" release in this case? ref:
http://tripleo.org/upgrade/minor_update.html#updating-your-overcloud-ocata-and-earlier
3. Do I need to upgrade to each release? ie from Pike > Queens then Queens
> Stein etc ? Or can I do this:
a) update Pike to the latest in the current Pike release
b) Update Pike to Train


*What I've gathered so far:*
- If I can execute the 'openstack overcloud update' and limit it to the
controller node then I can apply this to a cloned environment consisting of
1 x undercloud "director" and 1 x controller but I am unable to stage this
for the compute nodes because they are physical bare-metal

- the tripleo website guide lists the latest as 'Rocky' but I could see
Stein in the yum search. I think I can follow the tripleo guide with a
pinch of salt and replace *rocky* with *stein*



Thank you


*Tony Pearce*   |
*Senior Network Engineer / Infrastructure Lead**Cinglevue International
<https://www.cinglevue.com>*

Email: tony.pearce at cinglevue.com
Web: http://www.cinglevue.com

*Australia*
1 Walsh Loop, Joondalup, WA 6027 Australia.

Direct: +61 8 6202 0036 | Main: +61 8 6202 0024

Note: This email and all attachments are the sole property of Cinglevue
International Pty Ltd. (or any of its subsidiary entities), and the
information contained herein must be considered confidential, unless
specified otherwise.   If you are not the intended recipient, you must not
use or forward the information contained in these documents.   If you have
received this message in error, please delete the email and notify the
sender.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200121/6379c9a3/attachment-0001.html>


More information about the openstack-discuss mailing list