-
Notifications
You must be signed in to change notification settings - Fork 95
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
Please document how to configure multiple dc test and the config option syntax #9278
Comments
Update: Setting scylla_ami_id to be empty will not work either. It failed
|
I tested the config in the web like below: It failed with:
|
I tried:
Failed too:
I am out of idea what is the correct way to set multiple amis. |
it's a bug in the perf pipeline, that dates to 2019, when it was introduced if [[ ! -z "${params.byo_scylla_branch}" ]] ; then
echo "Skipping 'scylla_ami_id', 'scylla_version' and 'scylla_repo' checks because BYO ScyllaDB was enabled"
elif [[ ! -z "${params.scylla_ami_id}" ]] ; then
export SCT_AMI_ID_DB_SCYLLA=${params.scylla_ami_id}
elif [[ ! -z "${supportedVersions}" ]]; then
export SCT_SCYLLA_VERSION=${supportedVersions}
elif [[ ! -z "${params.scylla_version}" ]] ; then
export SCT_SCYLLA_VERSION=${params.scylla_version}
elif [[ ! -z "${params.scylla_repo}" ]] ; then
export SCT_SCYLLA_REPO=${params.scylla_repo}
elif [[ "${params.backend ? params.backend : ''}" == *"k8s"* ]] ; then
echo "Kubernetes backend can have empty scylla version. It will be taken from defaults of the scylla helm chart"
else
echo "need to choose one of SCT_AMI_ID_DB_SCYLLA | SCT_SCYLLA_VERSION | SCT_SCYLLA_REPO"
exit 1
fi the values of the exports should be escaped with |
this pipeline was never used for multidc cases, and was missing multiple feature that exists on longevity pipeline, like handling correctly the regions, and quoting correctly possible space seperated pipeline parameters Fixes: scylladb#9278
@asias and the expect way should be configure: from jenkins: the failure:
we introduce long ago, to make sure we fail fast on if one didn't supply those, which is the main usage case of SCT jobs. anyhow we dropped this check from longevity pipeline, and can consider dropping it from all pipelines |
this pipeline was never used for multidc cases, and was missing multiple feature that exists on longevity pipeline, like handling correctly the regions, and quoting correctly possible space seperated pipeline parameters Fixes: scylladb#9278 (cherry picked from commit 30305d8)
Id' be more than happy to try it. jenkins, should I use scylla_ami_id: 'ami-09952611d7ecc2ebd ami-0ed83900fba44c6a9' or scylla_ami_id: ami-09952611d7ecc2ebd ami-0ed83900fba44c6a9
|
the 2nd, you shouldn't need to quote it
|
OK. So far so good. It seems the PR has fixed the issue. It has passed the point where it failed previously. Btw, can we make jekins take the same format of space separated parameter for region.
|
this pipeline was never used for multidc cases, and was missing multiple feature that exists on longevity pipeline, like handling correctly the regions, and quoting correctly possible space seperated pipeline parameters Fixes: #9278
For example:
availability_zone: 'a,b,c'
n_db_nodes: '6 6'
n_loaders: '2 1'
Why is the availability_zone separated by "," while the others are separated by space.
How do we specify multiple dc region or ami ids?
region_name: 'eu-west-1 us-east-1'
ami_id_db_scylla: 'ami-09952611d7ecc2ebd ami-0ed83900fba44c6a9'
On the jenkins web, e.g., https://jenkins.scylladb.com/job/scylla-master/job/tier1/job/longevity-multidc-schema-topology-changes-12h-test/46/parameters/, it also has the region configs, but the syntax is different. And It fails to start the test if I set scylla_ami_id. I have to left scylla_ami_id to be empty and I have to set region with a different syntax (it can not be empty)
region: ["eu-west-1", "us-east-1"]
scylla_ami_id: must be empty
The text was updated successfully, but these errors were encountered: