Provide CNAMEs for AWS-based machines

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: rail, Assigned: rail)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [reit-ops])

Attachments

(2 attachments)

ATM we can use releng.{use1,usw2}.mozilla.com domain names for AWS-based machines. We usually also use CNAMEs in build.mozilla.org domain for convenience.

AFAIK, there are some difficulties with CNAME entries (inventory related?). Amy may have more details.
There is no way to automate changes to the mozilla.org zones since they are not under inventory control (unlike the forward and reverse zones for AWS).  I'll hand this over to the folks who are working on migrating zones for an update about when that eventually happens (there is quite a bit of difficulty in driving that via inventory, I believe just because of the kinds of hosts that are in the mozilla.org zone).
Assignee: server-ops-releng → juber
Component: Server Operations: RelEng → Server Operations
QA Contact: arich → shyam
You can create build.mozilla.org CNAMEs in Inventory now.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Due to technicality (we don't yet have build.m.o CNAMES created) I'm moving this over to releng (to reflect where the work lies) and reopening.
Assignee: juber → nobody
Status: RESOLVED → REOPENED
Component: Server Operations → Release Engineering
QA Contact: shyam
Resolution: FIXED → ---
The following command should do the trick:
invtool CNAME create --fqdn cname.build.mozilla.org --target longlong.usw2.mozilla.com --private --description "Bug 864325" 

I list of existing hosts can be grabbed from http://cruncher.build.mozilla.org/~buildduty/hosts. We need to filter the list by removing non-FQDN and we should verify if all of the entries have appropriate DNS entries (A+PTR)
Created attachment 773301 [details]
AWS masters' CNAMEs
Product: mozilla.org → Release Engineering
Created attachment 828171 [details]
add_them.sh

generated by:

invtool search -q "type=:A /^(try|bld|tst)-linux(64|32)-ec2-[0-9].*"  | awk '{print $2}' | sed 's/\.$//' | grep -v ^$ | sort > slaves

for slave in `cat slaves`; do
 short=$(echo $slave | awk -F. '{print $1}')
 cname="${short}.build.mozilla.org"
 echo "invtool CNAME create --fqdn $cname --target $slave --private --description 'bug 864325'"
done > add_them.sh
Attachment #828171 - Flags: review?(hwine)
Assignee: nobody → rail
Comment on attachment 828171 [details]
add_them.sh

Looks good -- two questions, but non-blocking if they aren't needed

1. do we need --no-public option? Or is that default? (not clear to me)

2. should --description be --comment, and maybe add --description "RelEng Convention"
Attachment #828171 - Flags: review?(hwine) → review+
(In reply to Hal Wine [:hwine] (use needinfo) from comment #7)
> Comment on attachment 828171 [details]
> add_them.sh
> 
> Looks good -- two questions, but non-blocking if they aren't needed
> 
> 1. do we need --no-public option? Or is that default? (not clear to me)

That's default AFAIK, at least it's not set in the UI.
 
> 2. should --description be --comment, and maybe add --description "RelEng
> Convention"

Fixed and ran!
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.