-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare crc job for architecture repo #1794
Conversation
Skipping CI for Draft Pull Request. |
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/a3093d29b9544bef8268e52770a253a2 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 38m 32s |
edb4cd5
to
75508b0
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/a26a3535f4bc4ebba975cb082c04a9f8 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 37m 29s |
75508b0
to
fd154d9
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/29d9fd51e04c4b8ea2ab5d8f81553935 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 31m 16s |
fd154d9
to
02e9210
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
recheck |
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
02e9210
to
caea06f
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
recheck |
Unable to freeze job graph: Job cifmw-architecture-crc-hci does not specify a run playbook |
928c776
to
fc84295
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/eee7775f3fe34cad9cfe1d0ef549d4f9 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 43m 10s |
7b8587d
to
0a35ad7
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/299c68c8dba14ee7af3438d2f1042835 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 10m 13s |
0a35ad7
to
fe58ada
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
fe58ada
to
7317c3f
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/0106a912a837473197809cc66c91db62 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 43m 37s |
7317c3f
to
603a461
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/2b910b2eb8b3403c873ccf071d67f22a ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 43m 14s |
603a461
to
f0f85b9
Compare
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/73a0aa3cc03a4ddeaf50afcbcb02e1ae ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 37m 46s |
699cf8f
to
a74e33c
Compare
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/e6be06e33da74045accd5d30023ae2c0 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 37m 55s |
a74e33c
to
fa973da
Compare
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/efcb418b1bc247d5a6b8fc57a672a7b6 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 56m 23s |
92e0f72
to
04bad98
Compare
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/824c21bcf3d947669c59afccdf443dfd ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 28m 26s |
04bad98
to
c71ca13
Compare
}} | ||
ci_framework_src_dir: "{{ ansible_user_dir }}/src/github.com/openstack-k8s-operators/ci-framework" | ||
pre_tasks: | ||
- name: Create needed directories |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this could be done via the ci_setup/directories tasks file (you have to provide directory_state: directory
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's a good idea, but I'd still need an extra task to create parameters
dir, since it's not created by the ci_setup
- "{{ cifmw_manifests | default(cifmw_ci_setup_basedir ~ '/artifacts/manifests') }}/\ |
interfaces-info.yml
file
/approve Won't block on the directory creation comment, might be a follow-up. Seeing this coming is pretty cool! |
Create a job that can deploy the HCI VA with an extracted crc layout. This change introduces the jobs definition and playbooks for such a job. It creates and extracted crc layout using ci-bootstrap role and then calls networking mapper to get the required networking config to deploy a VA. It needs to generate an interfaces-info file. Additionally, it changes the 06-deploy-architecture playbook to allow ssh access from any network to the compute nodes. It also modifies the multinode-customizations playbook to work with a 'ctlplane' network in the crc, instead of a 'default' one. It makes use of scenario inhertance proposed in [1] to reuse most of the existing HCI VA scenario. [1] #1491 Depends-On: #1491
c71ca13
to
8d96de7
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cjeanner, son-vyas The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
Create a job that can deploy the HCI VA with an extracted crc layout.
This change introduces the jobs definition and playbooks for such a job.
It creates and extracted crc layout using ci-bootstrap role
and then calls networking mapper to get the required networking config to
deploy a VA. It needs to generate an interfaces-info file.
Additionally, it changes the 06-deploy-architecture playbook to allow
ssh access from any network to the compute nodes. It also modifies the
multinode-customizations playbook to work with a 'ctlplane' network in
the crc, instead of a 'default' one.
It makes use of scenario inhertance proposed in [1] to reuse most of the
existing HCI VA scenario.
[1] #1491
As a pull request owner and reviewers, I checked that: