[Starlingx-discuss] More OpenDev updates

Dean Troyer dtroyer at gmail.com
Sat Apr 20 19:52:34 UTC 2019


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:merged)

* 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
[2] https://review.opendev.org/653960

-- 
Dean Troyer
dtroyer at gmail.com



More information about the Starlingx-discuss mailing list