Re-use the multi-rhel deployment (fs 66) and add the update variables
to the new job.
Use the run_test_role_vars to pass the variable to the role.
Change-Id: Ica24513c6542376695d6c2f5d71e57166b0aca3f
In order to add the periodic version of external compute jobs,
we need to create a seperate job which contains the reusable
job definitions. It can be reused in RDO, Downstream and
Upstream job definitions.
edpm jobs are parented from multinode cs9 distro jobs. When we
use multi parenting with the existing jobs then tags and playbook
vars are not getting overriden in multi parenting.
In order to fix that, we have added a new edpm base job which
will be shared in RDO/downstream also.
Here is the new parent structure
tripleo-ci-base-multinode-standard
tripleo-ci-base-multinode-edpm-standard
tripleo-ci-base-required-projects-edpm-upstream
tripleo-ci-base-edpm-centos-9
then actual job: tripleo-ci-centos-9-standalone-external-compute-target-host
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I7cc3b191e9af124878f037bcf0f837d353a44f8f
Zuul will be removing support for ansible 2.8 and 2.9 in the near
future. This changes removes the pins of jobs to those versions which
will cause the jobs to run against the current zuul tenant default
ansible (version 5). Eventually this will update to Ansible version 6
and so on.
Change-Id: I410ff0205a317a7655657a8acb6a95c3b61144d8
Due to Zuul Job reparenting work, base-upstream.yaml file is created
to keep the new zuul job base there.
Since Zuul job reparenting work is done, it's time to drop old
base.yaml and rename base-upstream.yaml to base.yaml.
base.yaml is dropped in this review:
https://review.opendev.org/c/openstack/tripleo-ci/+/849856/
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I08afc3e69059c7bc066eeec0a40ce4cd50d3cc7f
Since we have completed Upstream TripleO CI Zuul Job Reparenting.
We need to start prepration for renaming base-upstream.yaml
to base.yaml.
In order to have clean rename, remaining jobs from base.yaml
should be moved to base-upstream.yaml.
This patch does the same.
Due to Zuul Job reparenting work, base-upstream.yaml file is created
to keep the new zuul job base there.
Since Zuul job reparenting work is done, it's time to drop old
base.yaml and rename base-upstream.yaml to base.yaml.
It deletes the base.yaml and will rename the base-upstream.yaml
to base.yaml in
https://review.opendev.org/c/openstack/tripleo-ci/+/849806.
It helps to keep the changes seperate.
It updates the old job name with new parent in deprecated jobs also
to fix zuul issue.
RDO Check job review: https://review.rdoproject.org/r/c/config/+/44455
It also adds a dummy tripleo-ci-standalone-base job to avoid zuul
error.
Depends-On: https://review.rdoproject.org/r/c/config/+/44455
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I08a5e67d31eb8c81c05b9e23d907944c566db07a
Codes under the test directory are not used by actual functionality but
only by unit tests. Thus we don't need to run functional jobs in case
only these test codes are updated.
Change-Id: I425c111238768163ed237d57e16c68f391b0f41c
Complements I4f4b19a8a056efef6a7d63cace88cd8a650e80dc
but there is no strict dependency to merge these.
Change-Id: I5e3ccf21b6b4896ff0c832d3b00755ff800bb810
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
Ansible OpenStack collection is not used by TripleO Quickstart.
It is used within TripleO Ansible et al but Ansible OpenStack
collection is used via RPMs from RDO for that.
Change-Id: I551d46e612038a739c34dc6738de85344b7f1be7
Earlier we were using singlenode parent from base.yaml.
Since we have undercloud distro base jobs is already available,
we can re-use the same and remove the singlenode parent.
It also cleans up old singlenode cs8 base jobs and moves
c8s undercloud upgrade job to upgrade template.
These jobs are used as a parent in stable branches job.
https://review.rdoproject.org/r/q/topic:cs-parenting-undercloud-upgrade
cleans up the reference from rdo side.
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: If54577079cf61d82e88aa84a414d6e3c288138b1
As a part of reparenting strategy[1], It adds the following jobs
* tripleo-ci-undercloud-required-projects-upstream
By using above as a parent, we created following
distro jobs.
* tripleo-ci-base-undercloud-centos-7
* tripleo-ci-base-undercloud-centos-8
* tripleo-ci-base-undercloud-centos-9
The above parent is now used in Undercloud and centos-7
content provider jobs.
It removes tripleo-ci-undercloud-content-consumer-centos-8
unused jobs.
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: Ic14a34c9c8dc196b42603a539bd67685d5384a0b
Based on CS job parenting re-structure[1], for container build
jobs, It follows the following inheritance
* tripleo-ci-base-common-required-projects
* tripleo-ci-base
* tripleo-ci-base-singlenode-standard
* tripleo-ci-base-containers-standard
* tripleo-ci-build-containers-required-projects-upstream
For Distro specific
* CentOS 7
tripleo-ci-build-containers-required-projects-upstream
* tripleo-build-containers-base
* CentOS 8
tripleo-ci-build-containers-required-projects-upstream
* tripleo-build-containers-base-centos-8
* CentOS 9
tripleo-ci-build-containers-required-projects-upstream
* tripleo-build-containers-base-centos-9
Note: It adds tripleo-build-containers-base-centos-8
as a CS8 distro base job to create
tripleo-build-containers-centos-8 in order to keep
the consistency.
[1]. https://review.opendev.org/q/hashtag:cs-parenting
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: Ifd941e8ce0b42b434b95688c461db8db0a2ded9c
Based on CS job parenting re-structure[1], for multinode jobs,
It follows the following inheritance
* tripleo-ci-base-common-required-projects
* tripleo-ci-base
* tripleo-ci-base-multinode-standard
* tripleo-ci-base-required-projects-multinode-upstream
For Distro specific
* CentOS 7
tripleo-ci-base-required-projects-multinode-upstream
- tripleo-ci-base-multinode
* CentOS 8
tripleo-ci-base-required-projects-multinode-upstream
- tripleo-ci-base-multinode-centos-8
* CentOS 9
tripleo-ci-base-required-projects-multinode-upstream
- tripleo-ci-base-multinode-centos-9
With the above pattern,
* tripleo-ci-base-multinode-standard will be used as a parent in
downstream or rdo.
* Any Upstream specific multinode var can be placed in the distro
base job.
post-artifact-mult.yml playbook is used in EL8 and EL9 so
it is moved to a new role [2] tripleo-ci-post, to reuse it
at all places.
[1.] https://review.opendev.org/q/topic:cs-parenting
[2]. https://review.opendev.org/c/openstack/tripleo-ci/+/832254
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I2f3420d0be112a53c240f9e5539860e5e8673e4b
playbooks/tripleo-ci/post-artifact-mult.yml and
playbooks/tripleo-ci/post-artifact-sa.yml are used in post-run
to collect zuul artifacts.
Both are defined in multinode and standalone CentOS 8 base jobs.
While doing Zuul job reparenting, We found that It cannot be used
in different jobs defined in downstream or RDO. As zuul looks for
playbook in the project where zuul jobs are defined.
In order to reuse it in downstream and RDO, we are converting it
into role and call it in starting as a part of post.yaml playbook.
It also removes it from post-run.
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: Ibae7eaa6e6e91c88ac233c8fd52550e89bf2defc
This patch moves setup-compose-repos.yml playbook[1] to tripleo-ci repo
to be used on its base jobs.
This playbook is responsible for configuring and enabling CentOS compose
repos based on a provided compose URL.
It has no effect if 'dependency' var is not set to 'compose-repos'.
'centos_compose_url', if omitted, will be set by default to the latest
CentOS compose (for Stream 8 or 9).
With this change, the playbook can be deleted from previous repo.
The playbook is renamed to centos-compose-repos.yml
[1] https://github.com/rdo-infra/rdo-jobs/blob/master/playbooks/dependency/setup-compose-repos.yml
Change-Id: I09cf2d74638f9c056e62fdaaa2ff41047fce925d
Signed-off-by: Douglas Viroel <dviroel@redhat.com>
Adds tq and tqe to the required-projects: and roles: in zuul.d/base
for use with [1] where we are switching to use the repo-setup
role for containers and image builds. We need to split out the
changes to base so we can merge those and before we can test [1]
with the downstream jobs
[1] https://review.opendev.org/c/openstack/tripleo-ci/+/818222/48#message-a616446c90e0aff70e7c7a1276efd6330392e4c4
Change-Id: I4c1c972e1ea3111c623701a53a20c588809b1ac1
In [1] we are wiring up a role from the tripleo-quickstart repo.
There is already a 'common' role in t-q. Because of the name
clash we can rename the tripleo-ci common role.
[1] https://review.opendev.org/c/openstack/tripleo-ci/+/818222
Change-Id: I2bf7cebcefc19888058e368783a77ff8b524c998
The job definitions are added at [1] and the new
single-centos-9-node nodeset is added in the parent at [2]
Also fixes issue with the 'release' var which is not present
in the check/gate version of these jobs so we try to discover
it using the relevant build-containers tasks.
This also disables the image_sanity check for overcloud-full
because of related-bug.
Finally adds wallaby to the branches negative match for c9
build jobs as we aren't ready for W yet.
Related-Bug: 1950453
[1] https://review.opendev.org/c/openstack/tripleo-ci/+/813618
[2] https://review.opendev.org/c/openstack/tripleo-ci/+/816821
Change-Id: I5c78c975afa3efb2c478339cacd006e064b24e71
scenario010 jobs run better in nested virt environment, use centos 8
nested virt pool for those jobs.
Change-Id: Idb3f3d03cb1d39c259df7858357175dae58ecbdd
Adds image build jobs for master/wallaby and branchful -wallaby
variant for the CI repos. This is just the definitions and
base has nodeset commented out until it is available.
Jobs are wired into the layout with a followup patch (child of
this proposal).
Change-Id: I8f01ef0aa7adeac3c1b4af96cc9291cdef53fb63
scenario010 and ovn-provider-scenario010
have been difficult to get voting/gating across
all branches at the same time. Break the
unbranched job into branched jobs so that
we can move one branch at a time
Change-Id: I7c6ca59356f81e8acfbfc2aef8cec68da6c63f34
1. tripleo-ci-base-standalone-centos-8: has setup.py in irrelevant-files
tripleo-ci-centos-8-content-provider inherits from
tripleo-ci-base-standalone-centos-8 - so has setup.py in irrelevant files
as well
2. tripleo-ci-base-standalone-centos-8 does NOT have setup.py in irrelevant-files
tripleo-ci-centos-8-standalone does NOT have setup.py in irrelevant-files
3. so tripleo-ci-centos-8-standalone wants to run on setup.py,
but it depends on content-provider which does NOT run on setup.py
(see point 1)
Remove setup.py from irrelevant-files of content provider
(actually its parent job) to fix it.
Change-Id: Ie3130c20496e1e77531e2f5a156e53ae31c7da26
It is the latest version of ovb, it brought so many functionality.
It also improves the OVB jobs.
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I960c9a4df5a020c06748dd42a9b1a75c337214ac
For running jobs on CentOS 8 nodes use newer Ansilbe version of
Zuul - 2.9.
Please note, it's an Ansible version of Zuul itself. Not of
tripleo, not of CI quickstart, only Zuul playbooks.
Change-Id: I68149fadd78f86d9b4a29d45dff99592552d489c
Wire-up build-report post playbook on content provider jobs,
and use podman to check built images (buildah was inconsitent).
This change also advertises zuul artifacts using zuul_return and
change the build work dir to ansible user home.
Change-Id: Ie7c26c28e38035783ec1c5f87b3b6bdd6381376a
Patches are not being tested current in CentOS7 consumer
jobs as gating repo provided by provider job is not present
in those. Due to this broken patches are being merged. This
patch enables the playbook to setup gating repo in CentOS7
consumer jobs.
Related-Bug: #1903033
Depends-On: https://review.opendev.org/#/c/763711
Change-Id: Ib365e9dc18072e9e923762c522e3bc1d6ef6af0b