9:27 a.m.
I noticed that in quay.io in tripleotraincentos8, containers with the current-tripleo-rdo
tag have not appeared for a long time. I took some time to look into how CI is set up, and
found that the names of jobs with test scenarios in CI configuration, after which
containers should be marked with this tag, do not match the available jobs in Zuul.
I was comparing the two files and realized that the job names here do not match:
1.
https://github.com/rdo-infra/ci-config/blob/master/ci-scripts/dlrnapi_pro...
2. https://github.com/rdo-infra/rdo-jobs/blob/master/zuul.d/jobs.yaml#L998
If you pay attention to the current-tripleo tag in the file
https://github.com/rdo-infra/ci-config/blob/master/ci-scripts/dlrnapi_pro...,
the scenarios for this tag match the jobs in the rdo-jobs repository for Zuul.
I assume this is the reason for the long absence of this tag. But I do not exclude that
the reason lies in something else. I would like to find out why containers with
current-tripleo-rdo tag do not appear in qaya.io.
10:42 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
On Mon, Dec 12, 2022 at 10:27 AM <akashavkin(a)gmail.com> wrote:
I noticed that in quay.io in tripleotraincentos8, containers with
the
current-tripleo-rdo tag have not appeared for a long time. I took some time
to look into how CI is set up, and found that the names of jobs with test
scenarios in CI configuration, after which containers should be marked with
this tag, do not match the available jobs in Zuul.
That is correct - we no longer move containers to the current-tripleo-rdo
tag - current-tripleo is the last tag we promote to now.
I was comparing the two files and realized that the job names here do not
match:
1.
https://github.com/rdo-infra/ci-config/blob/master/ci-scripts/dlrnapi_pro...
2. https://github.com/rdo-infra/rdo-jobs/blob/master/zuul.d/jobs.yaml#L998
If you pay attention to the current-tripleo tag in the file
https://github.com/rdo-infra/ci-config/blob/master/ci-scripts/dlrnapi_pro...,
the scenarios for this tag match the jobs in the rdo-jobs repository for
Zuul.
I assume this is the reason for the long absence of this tag. But I do not
exclude that the reason lies in something else. I would like to find out
why containers with current-tripleo-rdo tag do not appear in qaya.io.
_______________________________________________
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
10:57 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
Does this only apply to Train? Or will new releases also only have the current-tripleo
tag?
10:59 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
On Mon, Dec 12, 2022 at 11:57 AM Alexey Kashavkin <akashavkin(a)gmail.com>
wrote:
Does this only apply to Train? Or will new releases also only have
the
current-tripleo tag?
All releases going forward.
_______________________________________________
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
3:27 p.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
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?
3:18 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
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
6:32 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
In addition to tripleo-quickstart, the current-tripleo-rdo tag in some releases or
versions of CentOS, if you look in the ci-config repository, included smoke tests of
tempest using the packstack environment and puppet integration tests. This gave the tag a
greater level of stability. I found confirmation of this in the TripleO documentation (1)
at docs.openstack.org and in the Delorean documentation (2). Although the Delorean
documentation talks about the current-passed-ci tag, I understood from exploring the
trunk.rdoproject.com repository that it is the same as current-tripleo-rdo, but I may be
wrong. For this reason, I was concerned about the long absence of new containers with this
tag in quay.io. It's very unfortunate that you were forced to make this decision.
Thanks a lot for the clarification, Alfredo.
1.
https://docs.openstack.org/tripleo-docs/latest/ci/dlrn-promoter-overview....
2.
https://dlrn.readthedocs.io/en/latest/repositories.html#dlrn-repository-c....
6:36 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
On Tue, Dec 13, 2022 at 7:32 AM Alexey Kashavkin <akashavkin(a)gmail.com>
wrote:
In addition to tripleo-quickstart, the current-tripleo-rdo tag in
some
releases or versions of CentOS, if you look in the ci-config repository,
included smoke tests of tempest using the packstack environment and puppet
integration tests. This gave the tag a greater level of stability. I found
confirmation of this in the TripleO documentation (1) at
docs.openstack.org and in the Delorean documentation (2). Although the
Delorean documentation talks about the current-passed-ci tag, I understood
from exploring the trunk.rdoproject.com repository that it is the same as
current-tripleo-rdo, but I may be wrong. For this reason, I was concerned
about the long absence of new containers with this tag in quay.io. It's
very unfortunate that you were forced to make this decision.
Thanks a lot for the clarification, Alfredo.
1.
https://docs.openstack.org/tripleo-docs/latest/ci/dlrn-promoter-overview....
2.
https://dlrn.readthedocs.io/en/latest/repositories.html#dlrn-repository-c...
.
Alfredo, thank you for responding with the reasoning behind the change.
Noted that our documentation requires some updates.
We will relook at that once we know what our upcoming releases will
require.
_______________________________________________
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
10:16 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
On Tue, Dec 13, 2022 at 1:37 PM Ronelle Landy <rlandy(a)redhat.com> wrote:
On Tue, Dec 13, 2022 at 7:32 AM Alexey Kashavkin <akashavkin(a)gmail.com>
wrote:
> In addition to tripleo-quickstart, the current-tripleo-rdo tag in some
> releases or versions of CentOS, if you look in the ci-config repository,
> included smoke tests of tempest using the packstack environment and puppet
> integration tests. This gave the tag a greater level of stability. I found
> confirmation of this in the TripleO documentation (1) at
> docs.openstack.org and in the Delorean documentation (2). Although the
> Delorean documentation talks about the current-passed-ci tag, I understood
> from exploring the trunk.rdoproject.com repository that it is the same
> as current-tripleo-rdo, but I may be wrong. For this reason, I was
> concerned about the long absence of new containers with this tag in
> quay.io. It's very unfortunate that you were forced to make this
> decision.
>
>
You are correct. WRT validation using packstack and puppet, we still run it
in a different pipeline in parallel and use it to promote puppet-passed-ci
link in RDO Trunk repos, you can see the jobs status for the more recent
releases in [1]. I understand that these two validation sets run in
parallel and they don't converge in a single tag but note that any issue we
catch in puppet promotions will be fixed and patches will end up in
tripleo containers.
[1]
http://dashboard-ci.tripleo.org/d/wplmDxdVz/puppet-promotion-pipelines?or...
Thanks a lot for the clarification, Alfredo.
>
> 1.
>
https://docs.openstack.org/tripleo-docs/latest/ci/dlrn-promoter-overview....
> 2.
>
https://dlrn.readthedocs.io/en/latest/repositories.html#dlrn-repository-c...
> .
>
Alfredo, thank you for responding with the reasoning behind the change.
Noted that our documentation requires some updates.
We will relook at that once we know what our upcoming releases will
require.
> _______________________________________________
> 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
>
_______________________________________________
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
noon
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
Based on this, can we say that the current-tripleo tag provides the same stability as the
current-tripleo-rdo tag did before?
Also, could you please write if there is any updated information about the tags, which one
follows which one? For example, somewhere in some blog or article, if there are any, of
course. Because there is no information about the puppet-passed-ci tag in the TripleO CI
[1] or DLRN [2] documentation. All I found about this tag is just your 2016 presentation
[3].
Thank you so much, Alfredo.
[1] https://docs.openstack.org/tripleo-docs/latest/ci/index.html
[2] https://dlrn.readthedocs.io/en/latest/index.html
[3] https://amoralej.fedorapeople.org/slides/RDO-CI-summit-bcn-final.pdf
5:19 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
On Tue, Dec 13, 2022 at 7:00 PM Alexey Kashavkin <akashavkin(a)gmail.com wrote:
Best regards,
Alfredo
> [1]
https://docs.openstack.org/tripleo-docs/latest/ci/index.html
> [2] https://dlrn.readthedocs.io/en/latest/index.html
> [3] https://amoralej.fedorapeople.org/slides/RDO-CI-summit-bcn-final.pdf
> _______________________________________________
> 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
Based on this, can we say that the current-tripleo tag provides the
same
stability as the current-tripleo-rdo tag did before?
Yes, I'd say it should provide similar stability, specially if you are
using TripleO to deploy.
Also, could you please write if there is any updated information
about the
tags, which one follows which one? For example, somewhere in some blog or
article, if there are any, of course. Because there is no information about
the puppet-passed-ci tag in the TripleO CI [1] or DLRN [2] documentation.
All I found about this tag is just your 2016 presentation [3].
As puppet pipelines and tripleo ones are parallel effort we probably don't
have any doc with the whole content but the tags would be:
current -> consistent -> puppet-passed-ci
current -> consistent -> current-tripleo
There are intermediate tags as -testing ones or for component pipelines but
i'd say those are not intended to be used for users, it's more an internal
CI element.
Thank you so much, Alfredo.
7:35 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
Okay, thank you, Alfredo. I think that's enough for me.
4:51 a.m.
New subject: Containers with the current-tripleo-rdo tag have not appeared in quay.io for a long time
Alfredo, sorry to bother you, but could you please respond to my previous message.
497
days inactive
501
days old
12 comments
4 participants
participants (4)
-
akashavkin＠gmail.com -
Alexey Kashavkin
-
Alfredo Moralejo Alonso -
Ronelle Landy