qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [RFC] Using gitlab for upstream qemu repo?
Date: Fri, 23 Oct 2020 09:44:51 +0100	[thread overview]
Message-ID: <20201023084451.GB445638@redhat.com> (raw)
In-Reply-To: <672b8aa0-2128-23e1-b778-01a4d96b209d@redhat.com>

On Thu, Oct 22, 2020 at 06:47:55PM +0200, Paolo Bonzini wrote:
> Hi all,
> 
> now that Gitlab is the primary CI infrastructure for QEMU, and that all
> QEMU git repositories (including mirrors) are available on Gitlab, I
> would like to propose that committers use Gitlab when merging commits to
> QEMU repositories.
> 
> There are four reasons for this:
> 
> - this would be a step towards ensuring that all commits go through the
> CI process, and it would also provide a way to run the deployment of the
> web site via .gitlab-ci.yml.
> 
> - right now Gitlab pulls from upstream repos and qemu.org pulls from
> gitlab, but this is not true for the qemu, qemu-web and openbios
> repositories where Gitlab pulls from qemu.org and qemu.org is the main
> repository.  With this switch, all the main repositories would be on
> Gitlab and then mirrored to both qemu.org and GitHub.  Having a
> homogeneous configuration makes it easier to document what's going on.

I think it makes sense to make GitLab be the canonical location for
all the GIT repos that QEMU project hosts, and everything else be a
read-only mirror.

With the current mixed setup both qemu.org and gitlab.com are failure
points which impact us. This is bad because while gitlab.com has
scalable redundant hardware with dedicated sysadmins, qemu.org is a
single VM, with part time sysadmins, and no failover facility if the
VM fails.

By making gitlab.com primary, any problems with qemu.org no longer
have a blocking impact on us.

> - it would limit the number of people with access to qemu.org, since
> committers would no longer need an account on the machine.
> 
> - by treating gitlab as authoritative, we could include it in the
> .gitmodules file and remove load on the qemu.org server

Yes makes sense,

> Nothing would change for developers, who would still have access to all
> three sets of repositories (git.qemu.org, gitlab.com and github.com).
> Committers however would need to have an account on the
> https://gitlab.com/qemu-project organization with access to the
> repositories they care about.  They would also lose write access to
> /srv/git on qemu.org.
> 
> Of course this is just starting a discussion, so I'm not even proposing
> a date for the switch.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2020-10-23  8:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 16:47 [RFC] Using gitlab for upstream qemu repo? Paolo Bonzini
2020-10-22 17:24 ` Eric Blake
2020-10-23  7:37   ` Gerd Hoffmann
2020-10-23  8:51   ` Daniel P. Berrangé
2020-10-23 13:41     ` Stefan Hajnoczi
2020-10-23  9:37   ` Paolo Bonzini
2020-10-23  8:44 ` Daniel P. Berrangé [this message]
2020-10-23 13:41 ` Stefan Hajnoczi
2020-10-26 11:04 ` Peter Maydell
2020-10-27 13:14   ` Michael Roth
2020-10-27 18:48     ` Paolo Bonzini
2020-10-27 14:08   ` Stefan Hajnoczi
2020-10-27 14:20     ` Daniel P. Berrangé
2020-10-27 14:32     ` Peter Maydell
2021-01-05 14:12 ` Peter Maydell
2021-01-11  9:57   ` Stefan Hajnoczi
2021-01-11 11:02     ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201023084451.GB445638@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=edgar.iglesias@gmail.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).