feature(multi-az): adapt provision step to multi-az #6055
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
single-dc, multi-az,: https://jenkins.scylladb.com/view/staging/job/scylla-staging/job/lukasz/job/longevity-mini-test-1h-test/9/ (I abort test after checking all looks fine) |
soyacz
added
test-provision-aws
Currently we aim to test symmetrical clusters and it's easy to make mistake in multi-az tests when number of db nodes don't divide by number of az's. Add additional check in sct-config to verify that.
Currently provision step is disabled in pipeline when using multi-az because it is not supporting this feature. Adapt AWS provision to support multi-az and enable back provision step.
soyacz
force-pushed
the
multi-az-provision-step-aws
branch
from
fe139cf
to
05824a9
Compare
|
all tests executed in jobs looks ok. |
we cloud a pipeline parameter for enabling on_demand so we can rerun the CI with on_demend when needed |
|
provision test are longevity, but without all the exposed pipeline parameters |
fruch
added
backport/5.2
vponomaryov
added a commit
to vponomaryov/scylla-cluster-tests
that referenced
this pull request
May 18, 2023
Recently was added check for the numbers of AZs and DB nodes [1]. The K8S backends are different and specifically EKS one requires at least 2 AZs to be configured. Only the first AZ will be used for node provisioning. So, knowing that, skip the AZ num check on K8S backends. [1] scylladb#6055
7 tasks
vponomaryov
added a commit
to vponomaryov/scylla-cluster-tests
that referenced
this pull request
May 18, 2023
Recently was added check for the numbers of AZs and DB nodes [1]. The K8S backends are different and specifically EKS one requires at least 2 AZs to be configured. Only the first AZ will be used for node provisioning. So, knowing that, skip the AZ num check on K8S backends. [1] scylladb#6055
fruch
pushed a commit
that referenced
this pull request
May 18, 2023
Recently was added check for the numbers of AZs and DB nodes [1]. The K8S backends are different and specifically EKS one requires at least 2 AZs to be configured. Only the first AZ will be used for node provisioning. So, knowing that, skip the AZ num check on K8S backends. [1] #6055
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently provision step is disabled in pipeline when using multi-az
because it is not supporting this feature.
Adapt AWS provision to support multi-az and enable back provision step.
refs: https://github.com/scylladb/qa-tasks/issues/1070
PR pre-checks (self review)
backportlabelssdcm/sct_config.py)unit-test/folder)