ReleaseEngineering/How To/Add New AWS Subnets: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Release Engineering How To|Add_New_AWS_Subnets}} | {{Release Engineering How To|Add_New_AWS_Subnets}} | ||
From {{bug | 1165432}} and notes here https://github.com/mozilla/build-cloud-tools/pull/72 | From {{bug|1165432}} and notes here https://github.com/mozilla/build-cloud-tools/pull/72 | ||
* Add subnets to https://github.com/mozilla/build-cloud-tools/blob/master/configs/subnets.yml | * Add subnets to https://github.com/mozilla/build-cloud-tools/blob/master/configs/subnets.yml | ||
Revision as of 15:31, 7 March 2016
From bug 1165432 and notes here https://github.com/mozilla/build-cloud-tools/pull/72
- Add subnets to https://github.com/mozilla/build-cloud-tools/blob/master/configs/subnets.yml
- run `scripts/aws_manage_subnets.py configs/subnets.yml`
- Open bugs with netops to include new flows
- Update firewall tests to include new subnets (private repo releng/firewall-tests) and ensure tests pass after netops has made the changes
- Update https://github.com/mozilla/build-cloud-tools/blob/master/configs/tst-linux64 and others to include subnets created in previous step