spread e2e targets over multiple AZs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
In https://github.com/hashicorp/nomad/pull/7266 we pinned the deployment of instances to a specific AZ so that we could pair EC2 instances with an EFS volume. Previously the spread across AZs was undefined. A better approach would be to spread the e2e cluster across multiple AZs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing pull request #7266 and the e2e cluster deployment configuration it changed, focusing on how EC2 instances are paired with EFS across availability zones. Determine how to distribute the e2e targets across multiple AZs while preserving EFS access, then run the relevant e2e deployment checks to verify the cluster is spread as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100