[Starlingx-discuss] Help needed to add patch to openstackclient

Bailey, Henry Albert (Al) Al.Bailey at windriver.com
Thu Jul 4 14:02:18 UTC 2019


My mistake, my response was based on the current codebase and release.

I don’t know what the procedure is for porting or supporting fixes in older STX releases.

Al

From: Song Gao song (高松) [mailto:gaosong.lc at inspur.com]
Sent: Thursday, July 04, 2019 9:27 AM
To: Bailey, Henry Albert (Al); starlingx-discuss at lists.starlingx.io
Subject: 答复: Help needed to add patch to openstackclient

Thanks for your timely response!
But, per starlingx 2018.10 how the openstackclient package built, is it built from the repo hosted in starlingx/upstream?
And if it’s right, I can make ti straight to commit to upstream.

发件人: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com]
发送时间: 2019年7月4日 21:13
收件人: Song Gao song (高松) <gaosong.lc at inspur.com>; starlingx-discuss at lists.starlingx.io
主题: RE: Help needed to add patch to openstackclient

Currently the manifest for starlingx  openstackclient  builds from stable/stein.
https://opendev.org/starlingx/manifest/src/branch/master/default.xml#L51

So if your fix is merged in vanilla openstackclient, and back-ported to the stable stein branch, it will get picked up automatically.

If you need to temporarily diverge from vanilla openstack, we typically request that the gerrit review be submitted to the openstack community,  and then we can temporarily merge it as a patch until the two environments are able to become in sync.

We do that with openstack-helm
https://opendev.org/starlingx/upstream/src/branch/master/openstack/openstack-helm

Al

From: Song Gao song (高松) [mailto:gaosong.lc at inspur.com]
Sent: Thursday, July 04, 2019 8:38 AM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] Help needed to add patch to openstackclient

Hi Folks:
   What is the steps to add patch to openstackclient for stx.1.0. Currently we have some problems with the openstack cli, and already find solutions, but stuck in the commit steps.
Any help will be appreciated!

Best Regards
Song.Gao

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190704/3c061d81/attachment.html>


More information about the Starlingx-discuss mailing list