3:18 a.m.
On Mon, Dec 12, 2022 at 10:28 PM Alexey Kashavkin <akashavkin(a)gmail.com>
wrote:
If you don't mind, could you give me a link to a resource where I
can read
more about this decision? It could be a commit or a ticket on some public
tracking system. I've tried to find more information about this on my own,
but no luck.
Is it related to the end of support for CentOS 8 and the move to a stream
version?
No, it's absolutely unrelated to CentOS Stream, it's mostly related to
limitations and simplification in CI infrastructure and considerations
about the value provided by current-tripleo-rdo. As Ronelle mentioned,
current-tripleo tag should provide usable containers to deploy RDO using
TripleO with a pretty similar level of validation.
For context, in terms of TripleO coverage, current-tripleo-rdo was
current-tripleo + a specific tripleo job with libvirt mode (tripleo
quickstart creating undercloud and overcloud as VMs in a baremetal server
using libvirt). This mode was mostly used in tripleo development and never
intended for something close to production. Using proper baremetal servers
to run this jobs (which require a pretty big server) has become more
difficult over time as most of the CI environments are cloud based and with
the last changes in CentOS CI infra (where we ran this particular job) we
decided to just remove the job until there is an optimal alternative and
rely on current-tripleo tag which include all the tripleo scenarios and
configurations required to validate TripleO and RDO.
I hope this clarifies the situation.
Best regards,
Alfredo
_______________________________________________
users mailing list -- users(a)lists.rdoproject.org
To unsubscribe send an email to users-leave(a)lists.rdoproject.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s