Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUpdate AMI ID for Linux slaves #183
Merged
Conversation
|
r+ |
The AMI of the old ID was private to the Daala AWS account. To copy it to one owned by the Servo account, I followed the instructions at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/CopyingAMIs.html : gave the Servo account permissions on the Daala account's AMI, created a copy in the Servo account, noted the new ID.
|
Old ID was for an instance in US-West-1. Everything else is in US-West-2. Changed ID to a copy in us-west-2 and will figure out why we're in this region later. |
|
Sounds good to me :-) |
edunham
added a commit
that referenced
this pull request
Dec 30, 2015
Update AMI ID for Linux slaves
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
edunham commentedDec 30, 2015
Workflow for switching from Daala AWS account to Servo AWS account:
/srv/pillar/buildbot.slsaws-access-keyandaws-secret-keyto correspond to Servo AWS account's Buildbot user (carefully not running Salt in between these steps)In other words, I'll merge this one by hand at the right time after r+ :)