Closed Bug 1060809 Opened 6 years ago Closed 6 years ago
Update soft-start client to point to final DNS record
But 1055319 adds a mechanism to soft-start the Loop/Hello feature. Currently, it uses the name "soft-start.loop-dev.stage.mozaws.net" for testing purposes, but we probably want to move this to a different place than the Loop development staging subdomain. Alexis / Natim: Could you figure out where this should live for the launch and put the final name in here? Thanks.
soft-start.loop.services.mozilla.com sounds the right host to point to.
I agree with Alexis. I can configure it if it works for you. Can you tell me what is the first value you want us to configure?
Flags: needinfo?(rhubscher) → needinfo?(adam)
I've seen: https://wiki.mozilla.org/Loop/Load_Handling So I suppose we should set: soft-start.loop.services.mozilla.com A 127.25.153.153 Is that correct?
(In reply to Rémy Hubscher (:natim) from comment #3) > I've seen: https://wiki.mozilla.org/Loop/Load_Handling > > So I suppose we should set: > > soft-start.loop.services.mozilla.com A 127.25.153.153 > > Is that correct? That seems as good a place to start as any, yes.
Ok. Benson — I don't have access to that Route 53 Zone. Could you add this record for us please? Thank you.
Assignee: nobody → bwong
Status: NEW → ASSIGNED
Assigned to Dean as he's the head ops engineer on loop now.
Assignee: bwong → dwilson
What is the ip addresses 127.25.153.153? What's behind it?
Dean the IP address is not bind to anything, we are using the DNS to serve an integer. See https://wiki.mozilla.org/Loop/Load_Handling for more information about the Load Handling soft start protocol.
Interesting document - thanks. I've added the DNS records and it should all appear within the hour.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Dean -- Thanks for adding the record. I had actually filed this bug to land a change on Firefox that points to the selected record (which is why it's open on Loop/Client rather than infrastructure), so I'm going to re-open it until we get that landed. Also, to verify: what TTL did you end up setting on this record?
Assignee: dwilson → adam
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Adam — The TTL is set to 300 seconds (5 minutes). I could verify that it is set to 127.25.153.153
Comment on attachment 8489682 [details] [diff] [review] Set throttle hostname to soft-start.loop.services.mozilla.com r=dmose
Attachment #8489682 - Flags: review?(dmose) → review+
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
Is there anything here that needs manual verification? Does this need on-going smoketest coverage?
I verified it with https://hg.mozilla.org/mozilla-central/rev/fd86082fb7a4#l1.13
Status: RESOLVED → VERIFIED
Comment on attachment 8489682 [details] [diff] [review] Set throttle hostname to soft-start.loop.services.mozilla.com Approval Request Comment Uplift request for patches staged and tested on Fig
Attachment #8489682 - Flags: approval-mozilla-aurora?
Comment on attachment 8489682 [details] [diff] [review] Set throttle hostname to soft-start.loop.services.mozilla.com I worked with Randell and Maire on uplifting a large number of Loop bugs at once. All of the bugs have been staged on Fig and tested by QE before uplift to Aurora. As well, all of the bugs are isolated to the Loop client. Randell handled the uplift with my approval. I am adding approval to the bug after the fact for bookkeeping.
Attachment #8489682 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
You need to log in before you can comment on or make changes to this bug.