[kolla] Upgrading from Centos7 Train to Centos8 Ussuri

Mark Goddard mark at stackhpc.com
Wed Mar 17 08:54:31 UTC 2021


On Wed, 17 Mar 2021 at 08:51, Mark Goddard <mark at stackhpc.com> wrote:
>
> On Tue, 16 Mar 2021 at 18:54, Braden, Albert
> <C-Albert.Braden at charter.com> wrote:
> >
> > I’m testing the Train7->Ussuri8 upgrade on a heat stack, following this document:
>
> Hi Albert,
>
> The procedure takes you from Train on CentOS 7 to Train on CentOS 8. A
> Ussuri upgrade would be a separate step. I'll try to make that clearer
> in the docs.
>
> Mark

It does include the following near the beginning:

The Train release is the last release to support CentOS 7, and the first to
support CentOS 8. CentOS 7 users wishing to upgrade beyond Train must therefore
migrate to CentOS 8. The upgrade path looks like this:

* Stein & earlier (CentOS 7)
* Train (CentOS 7)
* Train (CentOS 8)
* Ussuri & later (CentOS 8)

>
> >
> >
> >
> > OpenStack Docs: CentOS 8
> >
> >
> >
> > I used the instructions here to successfully remove a controller from the cluster:
> >
> >
> >
> > https://docs.openstack.org/kolla-ansible/train/user/adding-and-removing-hosts.html#removing-existing-controllers
> >
> >
> >
> > Now I’m ready to add one, using the instructions here:
> >
> >
> >
> > https://docs.openstack.org/kolla-ansible/train/user/adding-and-removing-hosts.html#adding-new-controllers
> >
> >
> >
> > They say to run bootstrap-servers:
> >
> >
> >
> > kolla-ansible -i <inventory> bootstrap-servers [ --limit <limit> ]
> >
> >
> >
> > The question is, how to run it? My build server is running Centos 7 and has Python 2.7.5. Should I just download Ussuri to my existing build server, or do I need to build a new Centos 8 build server with Python 3?
> >
> >
> >
> > I read the “potential issues” text but it’s not obvious whether it is safe to run Ussuri bootstrap-servers on Train hosts. If I don’t run bootstrap-servers on the Train controllers, then how does the new Ussuri controller get integrated (RMQ, MariaDB, etc.)?
> >
> >
> >
> >
> >
> >
> >
> > I apologize for the nonsense below. I have not been able to stop it from being attached to my external emails.
> >
> >
> >
> > The contents of this e-mail message and
> > any attachments are intended solely for the
> > addressee(s) and may contain confidential
> > and/or legally privileged information. If you
> > are not the intended recipient of this message
> > or if this message has been addressed to you
> > in error, please immediately alert the sender
> > by reply e-mail and then delete this message
> > and any attachments. If you are not the
> > intended recipient, you are notified that
> > any use, dissemination, distribution, copying,
> > or storage of this message or any attachment
> > is strictly prohibited.



More information about the openstack-discuss mailing list