867718 - set up fhr.data.mozilla.com as a CNAME to data.mozilla.com

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Mike Connor [:mconnor]]

After much discussion on IRC, let's do this.

* CNAME is obvious
* This will require SSL, so we'll need a cert.
* we'll want to make sure we record the host sanely in the log format

Comment 1

[Chris Turra [:cturra]]

*note - currently all fhr services are through fhr.mozilla.*net* which is the generic top level domain we use for our offsite assets. in this case, as you know, being served through our CDN partners.

to clarify what you're looking for: fhr.data.mozilla.net on https? if that the case, it actually might make more sense to simply host it at the same place we host fhr.mozilla.net, but do a http 301 to data.mozilla.com instead for fhr.data.mozilla.net requests.

Comment 2

[Mike Connor [:mconnor]]

(To clarify, though we sorted this on IRC):

* This has nothing to do with the CDN-hosted report, which has a stable domain and a cert.
* This is for the metrics frontend (Bagheera) so we can isolate incoming traffic from clients if needed.

Comment 3

[Jake Maul [:jakem]]

For those reading along...

FHR is 2 halves (from an IT/Ops perspective). fhr.cdn.mozilla.net is one half, and fhr.data.mozilla.com is the other.

fhr.cdn.mozilla.net mentioned in comment 1 refers to the static assets that we deliver to support the "about:healthreport" user-visible interface. That's unrelated here... totally separate thing.

This bug is about changing the stuff that the Health Report feature uses to send data to Mozilla... FHR is user-visible *and* can optionally share data with Mozilla. This bug is all about the service which backs the latter. Right now it sends to data.mozilla.com. Before it lands in Release, we'd like to change that to fhr.data.mozilla.com. This bug is the IT side to that (there are Firefox config changes too).


We need to set up the CNAME, buy a cert, add the cert to the Zeus Vserver (in SCL3), and double-check if the logging for the 80 and 443 Vservers includes the 'Host' header. If it doesn't, we need to work with :deinspanjer to make it so. :)

Comment 4

[Chris Turra [:cturra]]

grabbing ownership of this bug to start working through it.

Comment 5

[bhavana bajaj [:bajaj]]

Bug 867737 - Update FHR reporting URL which is dependent on this bug needs to be resolved asap as that is currently blocking our final FX21 Beta which is targeted to go-to-build Monday morning PT.Hence any prioritization to this bug will be very helpful.

Comment 6

[Chris Turra [:cturra]]

CNAME, SSL and load balancer configurations in place as requested.

 $ dig +short @ns1.mozilla.org fhr.data.mozilla.com
 data.mozilla.com.
 63.245.215.38

 $ curl -I https://fhr.data.mozilla.com
 HTTP/1.1 200 OK
 Transfer-Encoding: chunked
 Connection: Keep-Alive