Closed Bug 1134694 Opened 9 years ago Closed 9 years ago

masterfirefoxos.mozilla.org DNS change

Categories

(Infrastructure & Operations :: SSL Certificates, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jgmize, Unassigned)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/608] )

We are currently scheduled to launch the new masterfirefoxos.mozilla.org site on Feb 25th. The last step will be this DNS change.

masterfirefoxos.mozilla.org is currently an A record pointing to 162.209.58.188, which is mozilla.kineo.com. We would like to change the record to a CNAME pointing to prod.masterfirefoxos.com.

Let's schedule a specific time based on the assignee's availability to make this change.
Depends on: 1134685
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/608]
A few (hopefully quick) questions:

  1. What time do you want to make this change?
  2. In the move from Kineo, does the review process in bug 877456 still hold (i.e. no Mozilla data (corporate or employee) stored on the system other than the materials on Firefox OS necessary for training)?
  3. If there are reported technical issues with this site, who do I route them to?
  4. If there are reported political issues with this site, who do I route them to?  (This is usually the person responsible for the $$ being used to pay for site hosting. =) )
cyliang - can you cc me on 877456 so I can verify.

Below is what I know

Time - TBD, we should know tomorrow.
Tech Issues
- Josh Mize, Giorgos Logiotatidis, Benjamin Sternthal

Political Issues
- Natalia MartinezWinter, Escalate to John Bernard.

I will update mana with this info
Ben: You've been CCed on the bug in question.  =)
Same security review applies here. We are not storing any user information, no changes really in this area from the existing site.
On further reflection and discussion, we think it would be better to map masterfirefoxos.mozilla.org directly to the ELB created and configured in https://bugzilla.mozilla.org/show_bug.cgi?id=1134685#c4, masterfirefoxos-mozilla-org-1196681076.us-east-1.elb.amazonaws.com, instead of prod.masterfirefoxos.com.
Sounds good to me.  What time do you want this change to kick in?
How about 1.30PM Pacific Time (josh if this works for you).

I would ask that you come to #masterfirefoxos and confirm we are good to go before pulling the switch.
I've got a meeting running from 12:30 PM - 1:30 PM Pacific. =\  Does 2:00 PM Pacific work?  (That should give me some room in case the meeting runs long.)
I emailed our dev team asking about the meeting time, let's wait till I confirm before we move forward.
(In reply to C. Liang [:cyliang] from comment #8)
> I've got a meeting running from 12:30 PM - 1:30 PM Pacific. =\  Does 2:00 PM
> Pacific work?  (That should give me some room in case the meeting runs long.)

Sure, just ping me in #masterfirefoxos when you get out of your meeting.
I believe this has been updated.


$ dig masterfirefoxos.mozilla.org

; <<>> DiG 9.8.5-P1 <<>> masterfirefoxos.mozilla.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1074
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 1

;; QUESTION SECTION:
;masterfirefoxos.mozilla.org.	IN	A

;; ANSWER SECTION:
masterfirefoxos.mozilla.org. 60	IN	CNAME	masterfirefoxos-mozilla-org-1196681076.us-east-1.elb.amazonaws.com.
masterfirefoxos-mozilla-org-1196681076.us-east-1.elb.amazonaws.com. 60 IN A 54.209.193.123
masterfirefoxos-mozilla-org-1196681076.us-east-1.elb.amazonaws.com. 60 IN A 54.88.217.170
masterfirefoxos-mozilla-org-1196681076.us-east-1.elb.amazonaws.com. 60 IN A 54.208.115.178

;; AUTHORITY SECTION:
us-east-1.elb.amazonaws.com. 223 IN	NS	ns-1119.awsdns-11.org.
us-east-1.elb.amazonaws.com. 223 IN	NS	ns-934.awsdns-52.net.
us-east-1.elb.amazonaws.com. 223 IN	NS	ns-1793.awsdns-32.co.uk.
us-east-1.elb.amazonaws.com. 223 IN	NS	ns-235.awsdns-29.com.
Thanks :cyliang!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.