1208676 - [stage] Update /etc/hosts to point to new bouncer staging env

Status: RESOLVED FIXED

(www.mozilla.org :: Bedrock, defect)

Description

[Matt Brandt [:mbrandt]]

We're in the process of testing the bouncer migration and want to ensure uninterrupted service.

We need a staging instance (or demo) to point to https://bouncer-bouncer.stage.mozaws.net/. pmac noted in #www that updating /etc/hosts might be the simplest route forwards. Please advise the best route forward.

Comment 1

[Matt Brandt [:mbrandt]]

fox2mike, is this something you can help with?

Comment 2

[Shyam Mani [:fox2mike]]

I'm going to be getting on a plane shortly and Jake will be back from PTO on Tuesday. Best way forward is to ping Jake about this and he should be able to help. Thanks!

Comment 3

[Jake Maul [:jakem]]

I don't understand what you're looking for here... as far as I can tell, bouncer-bouncer.stage.mozaws.net *is* a staging instance, so I don't know what I would point to it.


curl -v 'https://bouncer-bouncer.stage.mozaws.net/?product=firefox-39.0-complete&os=win&lang=en-US'

returns

< HTTP/1.1 302 Moved Temporarily
< Location: http://download.cdn.mozilla.net/pub/firefox/releases/39.0/update/win32/en-US/firefox-39.0.complete.mar


Seems to be working to me. What am I not getting?

Comment 4

[Matt Brandt [:mbrandt]]

Sorry for the ambiguous nature of the request.

What I want to do it is update allizom.org to use https://bouncer-bouncer.stage.mozaws.net/ instead of download.mozilla.org.

Comment 5

[Jake Maul [:jakem]]

We (me, mbrandt, and pmac) discussed this in IRC. Here's the highlights:

[10:01:00]  <jakem>	mbrandt: ah, okay, I see what you mean... that's not something I can do, though
[10:01:09]  <jakem>	pmac or jgmize would need to alter the code, I think
[10:01:14]  <jakem>	I don't think that's a setting
[10:01:39]  <jakem>	one of the www-demoX.allizom.org sites would probably be the simplest bet for them

[10:02:15]  <@pmac>	mbrandt: yeah, like I said a few days ago, that's very unlikely to happen.
[10:03:43]  <mbrandt>	pmac: I understand. Correct me if this is poor understanding of how /etc/hosts works. If I update my local /etc/hosts file, would this be a fair approximation of changing it server side?
[10:04:46]  <@pmac>	mbrandt: if you say in your hosts file that download.mozilla.org is a certain IP then it'll just work, but bouncer needs to be expecting that host name

[10:04:20]  <jakem>	curl -v -H 'Host: download.mozilla.org' 'https://bouncer-bouncer.stage.mozaws.net/?product=firefox-39.0-complete&os=win&lang=en-US'
[10:04:21]  <jakem>	fails
[10:04:27]  <jakem>	< HTTP/1.1 503 Service Unavailable
[10:05:03]  <jakem>	that EC2 or ELB instance(s) don't seem to recognize that Host: header name
[10:05:18]  <@pmac>	ah. yeah. so you'd have to update that app to accept d.m.o
[10:05:32]  <@pmac>	which should be possible since that's the plan
[10:05:37]  <jakem>	that'd be a setting on the EC2 instance(s) and/or the associated ELB... whomever runs the instance is your best bet there

[10:06:22]  <mbrandt>	Thanks, both of you.


So, the next step will be to have the bouncer-bouncer.stage.mozaws.net instance of the app modified so it recognizes the Host: header "download.mozilla.org". You can verify if this is working with the "curl" command above... it should return a "302 Found" result, and a "Location:" header in the response. Whomever manages that instance of the app would need to set this up.

Then you can take some test computers, modify their hosts file to point download.mozilla.org to the IP of bouncer-bouncer.stage.mozaws.net, and then try to download Firefox. I would recommend 1) downloading Firefox full installer (Linux or Mac OSX), 2) downloading Stub Installer (Windows), 3) installing Firefox from Stub Installer (again Windows), and 4) updating Firefox from a recent previous version to current (any platform). All 4 of those are critical end-user use cases of download.mozilla.org that have to work and should be tested. RelEng or RelMan may be able to come up with more, but that would be my bare minimum recommendation.


Note that manual hosts file testing will be necessary to test Stub Installer, as well as Firefox updating... there's nothing we (IT or engagement) can do server-side to affect those, as they're baked into either the Firefox codebase, stub installer, or the AUS update XML snippets that go to the whole world.

Comment 6

[Jeremy Orem [:oremj]]

https://bouncer-bouncer.prod.mozaws.net/ is the soon to be production instance. It does support the download.mozilla.org Host header, so you should be able to test against it. The database is a copy from yesterday. I'll resync before we cut over.

Comment 7

[Matt Brandt [:mbrandt]]

An update - I've updated /etc/hosts and run the test suites; bouncer-tests and mcom-tests, in both cases tests all pass. 

Manually, spot checks of the following behave as expected:
- https://www.mozilla.org/firefox/developer/all/
- https://www.mozilla.org/firefox/organizations/all/
- https://www.mozilla.org/firefox/beta/all/

Remaining are:
- test the stub installer
- test the full installer
- test updating Firefox from a previous version

Comment 8

[Matt Brandt [:mbrandt]]

Verified on Windows:
- Download of stub installer works
- Stub installer installs Firefox

Verified on OSX:
- Full installer
- Updating a previous version of Firefox