Hi Bruce and all,

We also discussed this task in 9/25’s Non-OpenStack distro meeting, and we decide to choose Option 2.

Thanks.

 

https://storyboard.openstack.org/#!/story/2006544: update keystone on the host from the SRPM   

Decision was made:  wait for CentOS to support OpenStack Train, and from there we get SRPM for this keystone instance on host. Background: we happened to take OpenStack Keystone as the authentication and authorization solution for StarlingX, and it is okay we keep it (keystone on host) loosely coupled with OpenStack upstream.

 

Best Regards

Shuicheng

 

From: Lin, Shuicheng
Sent: Wednesday, September 25, 2019 4:33 PM
To: Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io; Hu, Yong <yong.hu@intel.com>
Subject: RE: About task "update keystone on the host from the SRPM" of Openstack Train

 

Hi Bruce,

Please check my inline comments.

 

Best Regards

Shuicheng

 

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

 

Shuicheng, thank you.  I tend to agree with you that Option 2 is the way to go, but I have some questions that maybe you or someone else in the community can answer.

 

[shuicheng] Per history of Stein and Rocky, it is about 1 month after OpenStack’s release date.

[shuicheng] I assume Host keystone (Stein) should have no communication with OpenStack(Train). Please correct me if it is wrong.

[shuicheng] Based on git history, we always use SRPM/RPM from CentOS for keystone.

[shuicheng] We could do it. Option 1 is to use upstream keystone code directly.

                      The risk is other dependent packages may need be upgraded together.

                                    For Option 2, CentOS help handle the dependency.

      brucej

 

From: Lin, Shuicheng
Sent: Monday, September 23, 2019 6:44 PM
To: starlingx-discuss@lists.starlingx.io; Jones, Bruce E <bruce.e.jones@intel.com>; Hu, Yong <yong.hu@intel.com>
Subject: 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