Yong:

Going with option 1 (move keystone, barbican, horizon) to Train makes sense as Stein is no longer going to be maintained later this year.  Then when the move to CentOS 8.x happens in a future release these 3 packages should be upversioned to align with the rest of the openstack services.

Frank 

From: Hu, Yong <yong.hu@intel.com>
Sent: Monday, March 16, 2020 4:10 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] about upgrading 3 OpenStack services on platform

Hi community members,

Here is a topic I like to get your feedback.

Currently we are using 3 OpenStack services on StarlingX platform natively, besides those containerized OpenStack services.

They are keystone, barbican and horizon for stx-gui, which are still with version “Stein” as of today.

Previously when we were making plan for stx.4.0 release, we aimed at upgrading these 3 services from “Stein” to “U”,

to align with containerized services (in progress of upgrading to “U”).  

However, now we have to give up this upgrade for stx.4.0, because:

1).  CentOS 7.x doesn’t have plan to provide packages for OpenStack “U”, so we cannot make the upgrade based on CentOS 7.x.

2).  CentOS 8.x has the plan to provide packages for OpenStack “U”,  but we won’t go there for stx.4.0 accordingly the decision from the meet-up in AZ two weeks ago.

Alternatively, we have some options:

1). For stx.4.0, we upgrade these 3 services from “Stein” to “Train”, which CentOS 7.x has already supported. It’s not perfect, but we are 1 step ahead. And then in stx.5.0, we move on from “Train” to “U”. Question:  *Is this valuable??**

2). We simply defer this upgrade to stx.5.0, by when we expect we can get full support base packages on CentOS 8.x for OpenStack “U”.

Please share your feedback if you care this matter.

Regards,

Yong