canmove, Confirmed users
6,441
edits
ReleaseEngineering/How To/Work with Golden AMIs: Difference between revisions
ReleaseEngineering/How To/Work with Golden AMIs (view source)
Revision as of 15:46, 23 July 2014
, 23 July 2014→Golden AMI
(Created page with "{{Release Engineering How To|Golden_AMI}} = Golden AMI = == Background == Puppet used to be one of the bottlenecks for Releng infra, especially for EC2 instances. Puppet requ...") |
|||
| Line 31: | Line 31: | ||
“Golden” AMIs are generated on aws-manager1 by multiple daily cronjobs, e.g. [http://hg.mozilla.org/build/puppet/file/a09b4e59ae96/modules/aws_manager/manifests/cron.pp#l79 http://hg.mozilla.org/build/puppet/file/a09b4e59ae96/modules/aws_manager/manifests/cron.pp#l79] | “Golden” AMIs are generated on aws-manager1 by multiple daily cronjobs, e.g. [http://hg.mozilla.org/build/puppet/file/a09b4e59ae96/modules/aws_manager/manifests/cron.pp#l79 http://hg.mozilla.org/build/puppet/file/a09b4e59ae96/modules/aws_manager/manifests/cron.pp#l79] | ||
Instances used to generate “golden” AMIs use DNS to | Instances used to generate “golden” AMIs use DNS to make puppet work and rely on proper DNS entries. To reduce possibility of IP collisions they live ina different subnet and require --ignore-subnet-check as a paramter. | ||
If the process is stuck for some reason you need to terminate the instances and kill the process. | If the process is stuck for some reason you need to terminate the instances and kill the process. | ||