Closed
Bug 815296
Opened 12 years ago
Closed 11 years ago
need a simple way to resolve amazon host names
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
Details
These slaves regularly hang up reconfigs. We need one of the following ASAP: - Working DNS - A well maintained file that maps them - Clear instructions on how to resolve with ec22ip.py, and easy access to the secrets Filing as critical because when Catlee and Rail are both gone this gets a lot more painful.
Comment 1•12 years ago
|
||
(In reply to Ben Hearsum [:bhearsum] from comment #0) > - Clear instructions on how to resolve with ec22ip.py, and easy access to > the secrets I created this doc last week: https://wiki.mozilla.org/ReleaseEngineering/How_To/Resolve_AWS_names Option 1 (DNS) would be the best solution. That's still in the TODO list.
Comment 2•12 years ago
|
||
@arr: Do you think that it would be possible to maintain AWS DNS records? How about this: Releng dumps hostname -> IP mappings (in bind configuration format) and IT refreshes that list every x hours (or we push it somewhere)
Comment 3•12 years ago
|
||
Rail: This is a question for the infrastructure folks (mozilla-> server ops: infrastructure) since they run DNS. Since IT doesn't manage any of the AWS stuff for releng, I'm not sure how this will be best done.
Reporter | ||
Comment 4•11 years ago
|
||
I think this is fixed now that we have DNS entries?
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•