ReleaseEngineering/How To/Add New AWS Subnets: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
m (typo fix)
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Release Engineering How To|Add_New_AWS_Subnets}}
{{Release Engineering How To|Add_New_AWS_Subnets}}


== Subnets ==
Below you can find the steps to add new aws subnets
 
== Create new subnets ==
* 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
** run `scripts/aws_manage_subnets.py configs/subnets.yml`
** run `scripts/aws_manage_subnets.py configs/subnets.yml` from aws-manager server to create the subnets in VPC
 
Please check in AWS the new VPC subnets
 
More details {{bug|1165432}} or {{bug|1239263}} and notes here https://github.com/mozilla/build-cloud-tools/pull/72
 
== Update firewall rules ==
* Open bugs with netops to include new flows, eg {{bug|1254144}}
* Add the subnets to https://github.com/mozilla/build-cloud-tools/blob/master/configs/securitygroups.yml
* Add the subnets to https://github.com/mozilla/build-cloud-tools/blob/master/configs/securitygroups.yml
** run `scripts/aws_manage_securitygroups.py configs/securitygroups.yml` from aws-manager server to create the security groups
'''NOTE:''' After the firewall rules has been added by netops team and the new subnets in securitygroups.yml, the changes will be applied overnight.  Or you can ask dustin to run the command manually. (We don't have permissions to sudo to fwunit)


From {{bug|1165432}} and notes here https://github.com/mozilla/build-cloud-tools/pull/72
<pre>
dmitchell@fwunit1 ~/firewall-tests [master] $ sudo su - fwunit
-sh-4.1$ umask 022
-sh-4.1$ cd /opt/fwunit/releng/src/tests/
-sh-4.1$ source /opt/fwunit/releng/bin/activate
(releng)-sh-4.1$ fwunit aws_releng
[2016-03-09 14:19:09,178] running aws_releng
...
(releng)-sh-4.1$ fwunit releng
...
</pre>


== Firewall ==
* 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 ( more details https://mana.mozilla.org/wiki/display/IT/How+to+Run+Flow+Tests )
* Update firewall tests to include new subnets (private repo releng/firewall-tests) and ensure tests pass after netops has made the changes ( more details https://mana.mozilla.org/wiki/display/IT/How+to+Run+Flow+Tests )


== Increase size of the pool ==
* Updated the size limit https://github.com/ciobancai/build-cloud-tools/blob/master/configs/watch_pending.cfg


* Update https://github.com/mozilla/build-cloud-tools/blob/master/configs/tst-linux64 and others to include subnets created in previous step
== Add the new platforms in build-cloud-tools==
=== tst-linux64 ===
* Add the new subnets for tst-linux64: https://github.com/mozilla/build-cloud-tools/blob/master/configs/tst-linux64

Latest revision as of 22:32, 19 January 2017


Below you can find the steps to add new aws subnets

Create new subnets

Please check in AWS the new VPC subnets

More details bug 1165432 or bug 1239263 and notes here https://github.com/mozilla/build-cloud-tools/pull/72

Update firewall rules

NOTE: After the firewall rules has been added by netops team and the new subnets in securitygroups.yml, the changes will be applied overnight. Or you can ask dustin to run the command manually. (We don't have permissions to sudo to fwunit)

dmitchell@fwunit1 ~/firewall-tests [master] $ sudo su - fwunit
-sh-4.1$ umask 022
-sh-4.1$ cd /opt/fwunit/releng/src/tests/
-sh-4.1$ source /opt/fwunit/releng/bin/activate
(releng)-sh-4.1$ fwunit aws_releng
[2016-03-09 14:19:09,178] running aws_releng
...
(releng)-sh-4.1$ fwunit releng
...

Increase size of the pool

Add the new platforms in build-cloud-tools

tst-linux64