openstack: deploy ctlplane with rootVolume too#41386
openstack: deploy ctlplane with rootVolume too#41386openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
When testing the rootVolume in a deployment, also include the controlplane, so later this can be tested by the CPMS. This might have a negative impact on the performance, since etcd will be on a cinder volume attached via Ceph, and we know the performance impact, so we need to be careful about this change.
|
[REHEARSALNOTIFIER]
A total of 566 jobs have been affected by this change. The above listing is non-exhaustive and limited to 35 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.14-e2e-openstack-kuryr |
|
/hold |
|
/hold cancel /cc mandre |
From https://github.com/openshift/release/blob/29c1c67/ci-operator/step-registry/openstack/conf/resourcenames/openstack-conf-resourcenames-commands.sh#L37-L45, I can see it's only affecting jobs that run on the |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EmilienM, mandre The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/pj-rehearse ack |
|
@EmilienM: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
When testing the rootVolume in a deployment, also include the
controlplane, so later this can be tested by the CPMS.
This might have a negative impact on the performance, since etcd will be
on a cinder volume attached via Ceph, and we know the performance
impact, so we need to be careful about this change.