Closed Bug 1311430 Opened 9 years ago Closed 9 years ago

correctly configure golden ami generation for g-w732

Categories

(Infrastructure & Operations :: RelOps: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: arich, Assigned: arich)

Details

Attachments

(1 file)

There are two pieces for g-w732 deployment in AWS. The first is that the config file in build-cloud-tools/configs/g-w732 should have the same base AMI specified as build-cloud-tools/configs/t-w732. The second is that there should be a cron job that builds the golden ami each night (similarly to t-w732). This requires a cron job (which is missing) and a shell script in aws-manager2:/builds/aws_manager/bin/aws_manager-g-w732-ec2-golden.sh The script is there, but the cron job is missing.
Attachment #8802576 - Flags: review?(mcornmesser)
Attachment #8802576 - Flags: review?(mcornmesser) → review+
I haven't heard any issues with instances generated from the new g-w732 AMIs, so calling this done. WIll defer to markco if there are problems with the AMI itself.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Spotted a wee typo at the end of the golden ami cron: + params => "-c ${repo_root}/configs/g-w732 ... --copy-to-region us-west-2 8-w732-ec2-golden"; s/8-w732/g-w732/
Yeah, corrected that with a subsequent checkin when I noticed it, too.
Woo, thanks for fixing this up.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: