canmove, Confirmed users
6,441
edits
ReleaseEngineering/How To/Work with Golden AMIs: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Work with Golden AMIs (view source)
Revision as of 15:48, 23 July 2014
, 23 July 2014→Golden AMI
| 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 make puppet work and rely on proper DNS entries. To reduce possibility of IP collisions they live | 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 in a 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. | ||