[OpenStack-Infra] Moving a project to OpenStack Gerrit

Sandro Mathys sandro at midokura.com
Mon Nov 30 07:46:33 UTC 2015


On Mon, Nov 30, 2015 at 4:28 PM, Andreas Jaeger <aj at suse.com> wrote:
> On 2015-11-30 07:58, Sandro Mathys wrote:
>>
>> Hi,
>>
>> We (MidoNet) would like to move to OpenStack infrastructure rather
>> sooner than later. As part of this, we'd obviously like to move to
>> OpenStack gerrit, from GitHub/GerritHub. However, we're looking for a
>> way to do so with as little disruption as possible. Most notably, we'd
>> like our upstream repo to keep working (in read-only, at least). Can
>> this be achieved somehow?
>>
>> Looking for an answer, I stumbled upon the "upstream" setting in
>> project-config/gerrit/projects.yaml but the information I could find
>> on that is very shallow. Can you explain what exactly this does,
>> please? i.e. is the upstream repo only used for the initial import or
>> will it be kept as upstream repo?
>
>
> Upstream is a one time import.
>
> You can keep your original repo, leaving it as read-only after merging a
> commit that points to the new location sounds like a good idea.

Except it would go stale after that, and that would cause us some
trouble in the migration period. Is it maybe possible to mirror the
gerrit repo to our GitHub repo in addition to the other two mirrors
(git.openstack.org and openstack/midonet on GitHub)?

Thanks,
Sandro

>> Also, I learned that GitHub enables redirects that would serve our
>> purpose, but only if the repo is moved (rather than forked or
>> recreated). Is it possible to move midonet/midonet to
>> openstack/midonet before turning openstack/midonet into a mirror of
>> OpenStack gerrit's openstack/midonet repo?
>
>
> AFAIK we cannot move,
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>    GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>        HRB 21284 (AG Nürnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
>



More information about the OpenStack-Infra mailing list