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)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: arich, Assigned: arich)
Details
Attachments
(1 file)
|
2.21 KB,
patch
|
markco
:
review+
|
Details | Diff | Splinter Review |
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.
Comment 1•9 years ago
|
||
| Assignee | ||
Comment 2•9 years ago
|
||
Attachment #8802576 -
Flags: review?(mcornmesser)
Updated•9 years ago
|
Attachment #8802576 -
Flags: review?(mcornmesser) → review+
| Assignee | ||
Comment 3•9 years ago
|
||
| Assignee | ||
Comment 4•9 years ago
|
||
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
Comment 5•9 years ago
|
||
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/
| Assignee | ||
Comment 6•9 years ago
|
||
Yeah, corrected that with a subsequent checkin when I noticed it, too.
Comment 7•9 years ago
|
||
Woo, thanks for fixing this up.
You need to log in
before you can comment on or make changes to this bug.
Description
•