All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	qemu-devel@nongnu.org,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/2] tests: Update CentOS 8 container to CentOS Stream 8
Date: Tue, 1 Feb 2022 18:02:21 +0000	[thread overview]
Message-ID: <Yfl1rZN6yKCyQ1O0@redhat.com> (raw)
In-Reply-To: <CABJz62Osah308O2pHFMWs+D2X+Mq=aOf1NAKFcUaWF5bGzwJEw@mail.gmail.com>

On Tue, Feb 01, 2022 at 09:08:22AM -0800, Andrea Bolognani wrote:
> On Tue, Feb 01, 2022 at 11:19:11AM +0100, Thomas Huth wrote:
> > +++ b/tests/docker/dockerfiles/centos8.docker
> > @@ -1,10 +1,10 @@
> >  # THIS FILE WAS AUTO-GENERATED
> >  #
> > -#  $ lcitool dockerfile centos-8 qemu
> > +#  $ lcitool dockerfile centos-stream-8 qemu
> >  #
> >  # https://gitlab.com/libvirt/libvirt-ci
> >
> > -FROM docker.io/library/centos:8
> > +FROM quay.io/centos/centos:stream8
> [...]
> > +++ b/tests/lcitool/refresh
> > @@ -77,7 +77,7 @@ ubuntu2004_tsanhack = [
> >  ]
> >
> >  try:
> > -   generate_dockerfile("centos8", "centos-8")
> > +   generate_dockerfile("centos8", "centos-stream-8")
> 
> I'm not convinced this is a good idea.
> 
> CentOS 8 and CentOS Stream 8 are two pretty distinct operating
> systems in terms of update cadence and stability expectations, so I
> think that using the label "centos8" for containers and CI jobs that
> are actually consuming CentOS Stream 8 is going to be a source of
> confusion.

Given the EOL of what I call the "traditional" CentOS model at the
end of 2021, both "CentOS" and "CentOS Stream" terms effectively
mean the same thing now.

If we were trying to support CI for both traditional CentOS and
CentOS Stream at the same time, then using the distinct naming
is sensible.  libvirt-ci.git is in this situation

Since QEMU should only care about CentOS Stream from this point
forwards, then I don't think we neccesarily[1] need to make the
naming more verbose by adding the word 'stream' everywhere.

The caveat is that aside from this dockerfile, we also have a
VM config in test/vm/ that historically used traditional CentOS.
That may also need updating to point to Stream unless it has
seemlessly transitioned to using Stream content without us
needing to change anything. I've not looked closely at that yet.

Regards,
Daniel

[1] what would make me change my mind is if we renamed all the
    QEMU dockerfiles so use the same distro naming convention
    as libvirt-ci.git rather than having QEMU's own naming. I've
    thought about suggesting it but it wasn't a high priority
    since lcitool usage is in its infancy in QEMU still
-- 
|: 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:[~2022-02-01 20:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 10:19 [PATCH 2/2] tests: Update CentOS 8 container to CentOS Stream 8 Thomas Huth
2022-02-01 10:53 ` Thomas Huth
2022-02-01 11:01 ` Philippe Mathieu-Daudé via
2022-02-01 11:15 ` Alex Bennée
2022-02-01 17:08 ` Andrea Bolognani
2022-02-01 17:35   ` Alex Bennée
2022-02-01 17:47     ` Philippe Mathieu-Daudé via
2022-02-01 18:34       ` Andrea Bolognani
2022-02-02  5:36         ` Thomas Huth
2022-02-01 18:02   ` Daniel P. Berrangé [this message]
2022-02-01 18:29     ` Andrea Bolognani
2022-02-03 17:39 ` Alex Bennée

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=Yfl1rZN6yKCyQ1O0@redhat.com \
    --to=berrange@redhat.com \
    --cc=abologna@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.