-
Notifications
You must be signed in to change notification settings - Fork 83
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
feature(multi-az): adapt provision step to multi-az #6055
Conversation
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) |
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.
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 |
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.
LGTM
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
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
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
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)
backport
labelssdcm/sct_config.py
)unit-test/
folder)