[Starlingx-discuss] More OpenDev updates
For those of you not following along in IRC here are my notes about things specific to StarlingX and the OpenDev transition: * All git remotes will need to eventually be updated. The gerrit remote WILL need to be updated to work as it uses ssh rather than https and can not be redirected. I have a script[-1] in progress to do this, it works for me but please run it with -n to see what it will do before you trust it. It is only changing git remotes so the risk is low but still... . .gitreview has been updated for us during the transition. You will not see this in the Gerrit queue as it was done direclty in the back-end repos while Gerrit was offline. You will see it in the git log and will need to do a git pull to refresh your working copies. * The repo name changes required some work in devstack itself plus our devstack jobs to address places where the repo name is used in the filesystem.[0] This means everywhere we assume we know the repo name in tox.ini and .zuul.yaml and other places we need to update it. The primary non-DevStack place I have seen this so far is pylint tox jobs that require other repos present to work. * At this point I have reviews up for the devstack jobs in update, integ, fault and config. The remaining ones yet to come...they will look a lot like the four already done. Also, fault and config depend on each other, wheee!!! I think I'll have to break up the plugins to get around that... * This Gerrit query will show the opendev stuff I have been doing under topic opendev-update: https://review.opendev.org/#/q/topic:opendev-update+(status:open+OR+status:m...) * Depends-On: footers must now use review.opendev.org in the URL. This is a Gerrit limitation that redirects can not be used. We had only two open reviews with Depends-On[1], I updated the commit message on both. Please verify that they are working as expected. (The original depends-on footer was not in the last block of text in the commit message, it may not have been previously working.) * I made a review in manifest[2] to use the new remotes but not change the destination paths. I'll leave it up to the build maintainers to decide if the destination directory names should also be changed. I've left a -1 on the review so it doesn't get blindly merged, if someone wants to pick it up and made further changes, feel free to do so. I am taking some weekend time, will check back in after a bit. If you have problems or questions please find me here, in #starlingx or anyone in #openstack-infra. Happy weekend everyone! dt [-1] https://github.com/starlingx-staging/tools-contrib/pull/8 for the PR or https://raw.githubusercontent.com/starlingx-staging/tools-contrib/8bea0e6d06... for the raw file [0] Free Internet points to the first one to make Apache redirects work there too... :) [1] https://review.opendev.org/653910 https://review.opendev.org/653911 [2] https://review.opendev.org/653960 -- Dean Troyer dtroyer@gmail.com
On Sat, Apr 20, 2019 at 2:52 PM Dean Troyer <dtroyer@gmail.com> wrote:
[-1] https://github.com/starlingx-staging/tools-contrib/pull/8 for the PR or https://raw.githubusercontent.com/starlingx-staging/tools-contrib/8bea0e6d06... for the raw file
I updated the script, now with more sed(1). Here is the new direct link: https://raw.githubusercontent.com/starlingx-staging/tools-contrib/3e311b467e... dt -- Dean Troyer dtroyer@gmail.com
Hi Troyer, I can see 'review.opendev.org' on opendev.org [1], but 'review.openstack.org' on github[2]. Will github.com/openstack/stx-xxx still be used and synced with opendev.org/starlingx/xxx? Or we won't use github.com/openstack/stx-xx anymore? [1] https://opendev.org/starlingx/config/src/branch/master/.gitreview [2] https://github.com/openstack/stx-config/blob/master/.gitreview Thanks, Cheng -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Sunday, April 21, 2019 3:53 AM To: starlingx <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] More OpenDev updates For those of you not following along in IRC here are my notes about things specific to StarlingX and the OpenDev transition: * All git remotes will need to eventually be updated. The gerrit remote WILL need to be updated to work as it uses ssh rather than https and can not be redirected. I have a script[-1] in progress to do this, it works for me but please run it with -n to see what it will do before you trust it. It is only changing git remotes so the risk is low but still... . .gitreview has been updated for us during the transition. You will not see this in the Gerrit queue as it was done direclty in the back-end repos while Gerrit was offline. You will see it in the git log and will need to do a git pull to refresh your working copies. * The repo name changes required some work in devstack itself plus our devstack jobs to address places where the repo name is used in the filesystem.[0] This means everywhere we assume we know the repo name in tox.ini and .zuul.yaml and other places we need to update it. The primary non-DevStack place I have seen this so far is pylint tox jobs that require other repos present to work. * At this point I have reviews up for the devstack jobs in update, integ, fault and config. The remaining ones yet to come...they will look a lot like the four already done. Also, fault and config depend on each other, wheee!!! I think I'll have to break up the plugins to get around that... * This Gerrit query will show the opendev stuff I have been doing under topic opendev-update: https://review.opendev.org/#/q/topic:opendev-update+(status:open+OR+status:m...) * Depends-On: footers must now use review.opendev.org in the URL. This is a Gerrit limitation that redirects can not be used. We had only two open reviews with Depends-On[1], I updated the commit message on both. Please verify that they are working as expected. (The original depends-on footer was not in the last block of text in the commit message, it may not have been previously working.) * I made a review in manifest[2] to use the new remotes but not change the destination paths. I'll leave it up to the build maintainers to decide if the destination directory names should also be changed. I've left a -1 on the review so it doesn't get blindly merged, if someone wants to pick it up and made further changes, feel free to do so. I am taking some weekend time, will check back in after a bit. If you have problems or questions please find me here, in #starlingx or anyone in #openstack-infra. Happy weekend everyone! dt [-1] https://github.com/starlingx-staging/tools-contrib/pull/8 for the PR or https://raw.githubusercontent.com/starlingx-staging/tools-contrib/8bea0e6d06... for the raw file [0] Free Internet points to the first one to make Apache redirects work there too... :) [1] https://review.opendev.org/653910 https://review.opendev.org/653911 [2] https://review.opendev.org/653960 -- Dean Troyer dtroyer@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Sun, Apr 21, 2019 at 9:35 PM Li, Cheng1 <cheng1.li@intel.com> wrote:
I can see 'review.opendev.org' on opendev.org [1], but 'review.openstack.org' on github[2]. Will github.com/openstack/stx-xxx still be used and synced with opendev.org/starlingx/xxx? Or we won't use github.com/openstack/stx-xx anymore?
None of the repos that changed to different namespaces are mirrored to github now, including starlingx/*. We are not planning to continue to mirror StarlingX to github. dt -- Dean Troyer dtroyer@gmail.com
Hi Dean, I ran your script but it didn't seem to do anything to my repo. [emacdona@yow-cgts4-lx:/localdisk/designer/emacdona/starlingx-0/cgcs-root/stx ] $ ./stx-remote-fix.sh -n stx.io-: https://opendev.org/stx-root.git git remote set-url starlingx https://opendev.org/stx-root.git [emacdona@yow-cgts4-lx:/localdisk/designer/emacdona/starlingx-0/cgcs-root/stx ] $ ./stx-remote-fix.sh stx.io-: https://opendev.org/stx-root.git [emacdona@yow-cgts4-lx:/localdisk/designer/emacdona/starlingx-0/cgcs-root/stx ] $ ls downloads git stx-clients stx-config stx-fault stx-gui stx-ha stx-integ stx-metal stx-nfv stx-remote-fix.sh stx-update stx-upstream It would be helpful if you circulated an email that specifically listed the operations that users need to execute that will allow us to bridge the namespace change in our local repos or to specifically recommend that we create new local repos with the namespace change. There are a lot of people affected by this update so a clear summary of what to do and maybe some checkpoints along the way would help the development community bridge this change. Thanks, Eric.
-----Original Message-----
From: Dean Troyer [mailto:dtroyer@gmail.com]
Sent: Saturday, April 20, 2019 3:53 PM
To: starlingx
Subject: [Starlingx-discuss] More OpenDev updates
For those of you not following along in IRC here are my notes about
things specific to StarlingX and the OpenDev transition:
* All git remotes will need to eventually be updated. The gerrit
remote WILL need to be updated to work as it uses ssh rather than
https and can not be redirected. I have a script[-1] in progress to
do this, it works for me but please run it with -n to see what it will
do before you trust it. It is only changing git remotes so the risk
is low but still...
. .gitreview has been updated for us during the transition. You will
not see this in the Gerrit queue as it was done direclty in the
back-end repos while Gerrit was offline. You will see it in the git
log and will need to do a git pull to refresh your working copies.
* The repo name changes required some work in devstack itself plus our
devstack jobs to address places where the repo name is used in the
filesystem.[0] This means everywhere we assume we know the repo name
in tox.ini and .zuul.yaml and other places we need to update it. The
primary non-DevStack place I have seen this so far is pylint tox jobs
that require other repos present to work.
* At this point I have reviews up for the devstack jobs in update,
integ, fault and config. The remaining ones yet to come...they will
look a lot like the four already done. Also, fault and config depend
on each other, wheee!!! I think I'll have to break up the plugins to
get around that...
* This Gerrit query will show the opendev stuff I have been doing
under topic opendev-update:
https://review.opendev.org/#/q/topic:opendev-update+(status:open+OR+status:m...)
* Depends-On: footers must now use review.opendev.org in the URL.
This is a Gerrit limitation that redirects can not be used. We had
only two open reviews with Depends-On[1], I updated the commit message
on both. Please verify that they are working as expected. (The
original depends-on footer was not in the last block of text in the
commit message, it may not have been previously working.)
* I made a review in manifest[2] to use the new remotes but not change
the destination paths. I'll leave it up to the build maintainers to
decide if the destination directory names should also be changed.
I've left a -1 on the review so it doesn't get blindly merged, if
someone wants to pick it up and made further changes, feel free to do
so.
I am taking some weekend time, will check back in after a bit. If you
have problems or questions please find me here, in #starlingx or
anyone in #openstack-infra.
Happy weekend everyone!
dt
[-1] https://github.com/starlingx-staging/tools-contrib/pull/8 for the
PR or https://raw.githubusercontent.com/starlingx-staging/tools-
contrib/8bea0e6d0650ec0e12648e3c5b749093e60203d7/misc/stx-remote-fix.sh
for the raw file
[0] Free Internet points to the first one to make Apache redirects
work there too... :)
[1] https://review.opendev.org/653910 https://review.opendev.org/653911
--
Dean Troyer
dtroyer@gmail.com
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On 2019-04-22 14:08:58 +0000 (+0000), MacDonald, Eric wrote: [...]
I ran your script but it didn't seem to do anything to my repo.
[emacdona@yow-cgts4-lx:/localdisk/designer/emacdona/starlingx-0/cgcs-root/stx ] $ ./stx-remote-fix.sh -n
stx.io-: https://opendev.org/stx-root.git
git remote set-url starlingx https://opendev.org/stx-root.git [...]
It looks like it must have missed dropping the "stx-" predfix and adding the "starlingx/" namespace in its place. -- Jeremy Stanley
On Mon, Apr 22, 2019 at 9:08 AM MacDonald, Eric <Eric.MacDonald@windriver.com> wrote:
I ran your script but it didn't seem to do anything to my repo.
I am not sure what you started with in your remote, it got the name change but not the path, the only form that I thought did not require a namespace was git.starlingx.io/stx-XXX, did you have something else to start with? It is not going to work well at that level in the build tree. IIRC that only updates the stx-root remotes. The script is meant to be run in _each_ repo, it makes no assumptions about anything around it, only changing the remotes in the 'current' git repo, ie what you will see by typing 'git remote -v'.
It would be helpful if you circulated an email that specifically listed the operations that users need to execute that will allow us to bridge the namespace change in our local repos or to specifically recommend that we create new local repos with the namespace change.
I am not making any specific recommendations on how to deal with the build environment workspace as I am not intimately familiar with it nor the assumptions built in to those scripts. That is why it does not (nor did the manifest change) attempt to rename any directories. dt -- Dean Troyer dtroyer@gmail.com
participants (4)
-
Dean Troyer
-
Jeremy Stanley
-
Li, Cheng1
-
MacDonald, Eric