CloudStack CI improvements
Open
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
- [ ] Refactor Cloudstack E2E to use separate CIDR ranges for main and release tests
- [ ] Generate control plane endpoint IPs from the codebuild job instead of individual tests
- [ ] Improve VM cleanup after E2E
- [ ] Add additional zones in Cloudstack for multi-az E2E
- [ ] Set up separate Cloudstack env for CI
Contributor guide
Research direction
Start by reviewing the CloudStack E2E and CodeBuild CI setup to identify where the five checklist items are implemented. Done means separate CIDR ranges, centralized control-plane endpoint IP generation, reliable VM cleanup, additional zones for multi-AZ E2E, and a separate CloudStack CI environment are all in place and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- ci-cd, cloud, infrastructure, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100