-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
BU Product Work
-
False
-
OCPSTRAT-350 - Add support to AWS Local Zones (Phase II)
-
-
(description in progress)
{}USER STORY:{}
As a Developer, I want to increase the coverage of the Local Zones location on CI, so I can make sure we are testing a different location every time the CI is running.
{}DESCRIPTION:{}
Currently the e2e is provisioning the cluster, adding the Local Zone location based on the subnet's zone (parent zone), fixed value.[1]
We could increase the coverage by getting ramdomly the zoneName when listing the zones, something like
$ aws --region us-east-1 ec2 describe-availability-zones --filters Name=opt-in-status,Values=opted-in Name=zone-type,Values=local-zone |jq -r .AvailabilityZones[].ZoneName | shuf |head -n1 us-east-1-scl-1a $ aws --region us-east-1 ec2 describe-availability-zones --filters Name=opt-in-status,Values=opted-in Name=zone-type,Values=local-zone |jq -r .AvailabilityZones[].ZoneName | shuf |head -n1 us-east-1-bos-1a (...)
So for each execution we could get a different zone to provision the cluster, running e2e on that zone.
Over the time we may have a good coverage on the given region.
{}Required:{}
...
{}Nice to have:{}
...
{}ACCEPTANCE CRITERIA:{}
TBD
{}ENGINEERING DETAILS:{}
- is duplicated by
-
SPLAT-1029 [aws][local-zones] Create periodic CI job for Phase II
-
- Closed
-
-
SPLAT-728 [aws][local-zone] create CI test to install a cluster in existing Local Zone subnet (Phase I)
-
- Closed
-