Shuicheng,

I thought we do have one patch on keystone on host? If we follow either Option#1 or #2, this means we have zero patches from StarlingX on keystone, correct?

Thx. - cindy

From: Lin, Shuicheng <shuicheng.lin@intel.com>
Sent: Tuesday, September 24, 2019 9:44 AM
To: starlingx-discuss@lists.starlingx.io; Jones, Bruce E <bruce.e.jones@intel.com>; Hu, Yong <yong.hu@intel.com>
Subject: [Starlingx-discuss] About task "update keystone on the host from the SRPM" of Openstack Train

Hi all,

There is a task 36619 [0] “update keystone on the host from the SRPM” of story 2006544 “Integrate with OpenStack Train (master)”.

Due to Train is not released yet, and it will take sometime for CentOS to support Train and provide the SRPM.

We have two option as below. And I prefer Option 2, since host keystone is to serve flock service, not OpenStack service.

Please help provide your suggestion.

Thanks in advance.

Option 1:

To catch stx 3.0 release, we need switch SRPM to use upstream git directly.

Advantage:

Host keystone will align with containerized keystone.

Disadvantage:

A few keystone related packages need switch from SRPM to git repository.

Other rpms may need be upgraded also if they have dependency on keystone.

Option 2:

We defer the upgrade task to stx 4.0, wait until SRPM is available in CentOS mirror.

Advantage:

Follow current design, and related packages could be upgraded easily together.

Disadvantage:

Host keystone will differ from containerized keystone.

Not sure when CentOS will provide SRPM for Train.

[0]: https://storyboard.openstack.org/#!/story/2006544

Best Regards

Shuicheng