[all][tc] Repository renames during OpenDev migration
On Wed, 2019-04-10 at 20:44 +0000, Jeremy Stanley wrote:
> On 2019-04-10 16:34:09 -0400 (-0400), Jim Rollenhagen wrote:
> > Before you ask, yes, there will be redirects.
> The redirects for git.openstack.org to opendev.org have in fact
> already been available for testing for a few weeks (and this week we
> added rules which should properly cover git.airshipit.org,
> git.starlingx.io and git.zuul-ci.org too). If you're interested in
> helping us prove them further, you can add a line like this to your
> /etc/hosts file:
> 2001:4800:7817:103:be76:4eff:fe04:e3e3 git.airshipit.org git.openstack.org git.starlingx.io git.zuul-ci.org
> ...or, if you don't have IPv6 access, like:
> 18.104.22.168 git.airshipit.org git.openstack.org git.starlingx.io git.zuul-ci.org
so after doing this if i clone directly i get
sean at pop-os:~/testing$ git clone https://git.openstack.org/openstack/nova
Cloning into 'nova'...
warning: redirecting to https://opendev.org/openstack/nova/
remote: Enumerating objects: 535171, done.
remote: Counting objects: 100% (535171/535171), done.
remote: Compressing objects: 100% (98416/98416), done.
remote: Total 535171 (delta 427543), reused 530320 (delta 423684)
Receiving objects: 100% (535171/535171), 150.93 MiB | 4.37 MiB/s, done.
Resolving deltas: 100% (427543/427543), done.
and if i clone via a local squid proxy i get
sean at pop-os:~/testing$ http_proxy=192.168.1.155:32345 git clone http://git.openstack.org/openstack/nova
Cloning into 'nova'...
remote: Counting objects: 535171, done.
remote: Compressing objects: 100% (259964/259964), done.
remote: Total 535171 (delta 425706), reused 365748 (delta 262136)
Receiving objects: 100% (535171/535171), 150.74 MiB | 4.80 MiB/s, done.
Resolving deltas: 100% (425706/425706), done.
so via the proxy i dont even see the redirct warning
but it seams to work fine for me over ipv4.
https also works.
> The expectation is that any hyperlinks to old cgit URLs remain
> working, as should any git operations relying on http:// or https://
> URLs (we unfortunately need to drop git:// support for a couple of
for what its worth while you can use netcat or socat to tunnel thorough a sock5 proxy with
a little trickery, for peopel behind coperate proxies the http/https repos on
github were always simpler to get working.
i dont have that problem anymore but i am glad that we changed the devstack
default to https as it make getting up and running for new people simpler.
that saidsetting GIT_BASE was not exactly hard either.
> As for any namespace changes and renames which happen during the
> course of the transition, the Gitea service at opendev.org handles
> redirecting those transparently and we've already tested (and in one
> instance fixed a corner case for) that functionality.