Closed
Bug 1256328
Opened 9 years ago
Closed 9 years ago
Set copy.loop.services.mozilla.com DNS record for initial copy panel rollout testing
Categories
(Cloud Services :: Operations: Miscellaneous, task, P1)
Cloud Services
Operations: Miscellaneous
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Mardak, Assigned: dmaher)
References
Details
Similar to bug 1060809, we want copy.loop-webapp-dev.stage.mozaws.net to be 127.0.0.25 to test a 10% nightly rollout of the feature implemented in bug 1239965.
Alternatively, we could just point the add-on to a more "final" hostname: copy.loop.services.mozilla.com (?) and set the DNS A record to 127.0.0.25.
Standard8, any thoughts on using a stage.mozaws.net hostname vs services.mozilla.com?
Doesn't directly block bug 1239965 as the feature will just be turned off until the DNS entry exists (effectively treating it as a 127.0.0.0 record).
|
Reporter | |
Updated•9 years ago
|
Flags: needinfo?(standard8)
|
||
Comment 1•9 years ago
|
||
I think we can probably just use the final hostname, unless there's a specific reason for a staging server (which I can't think of).
Flags: needinfo?(standard8)
|
||
Comment 2•9 years ago
|
||
Dan or JP: can you handle this?
Component: Server → Operations
Flags: needinfo?(jschneider)
Flags: needinfo?(dmaher)
Product: Hello (Loop) → Cloud Services
Whiteboard: [triage]
|
|
Reporter | |
Comment 3•9 years ago
|
||
Let's do..
copy.loop.services.mozilla.com A 127.0.0.25
The TTL used in bug 1060809 was 300 seconds / 5 minutes.
Summary: Set DNS record for initial copy panel rollout testing → Set copy.loop.services.mozilla.com DNS record for initial copy panel rollout testing
|
||
Updated•9 years ago
|
Rank: 9
Priority: -- → P1
|
||
Comment 4•9 years ago
|
||
Thanks for the ping here.
:mardak will this require SSL? If so, we may want to consider avoiding the period after 'copy', and instead have something like copy-loop.services.mozilla.com
Flags: needinfo?(jschneider)
Flags: needinfo?(edilee)
Flags: needinfo?(dmaher)
|
|
Reporter | |
Comment 5•9 years ago
|
||
Nothing should actually try to connect to copy.loop.services.mozilla.com, and if it did, it would end up looping back to itself (127.0.0.0/8), so SSL isn't required.
Flags: needinfo?(edilee)
|
|
Reporter | |
Comment 6•9 years ago
|
||
Do you need any additional information before setting
copy.loop.services.mozilla.com A 127.0.0.25
with 300 second TTL?
|
Assignee | |
Comment 7•9 years ago
|
||
07:38:40 <@ckolos> jp phrawzty: I took the liberty of doing 1256328 for you. If
this isn't what you wanted, please let me know and I can
easily revert.
07:40:04 < phrawzty> ckolos: seems like exactly what the customer asked for
$ dig copy.loop.services.mozilla.com | grep 127
copy.loop.services.mozilla.com. 120 IN A 127.0.0.25
Please verify and comment / close this bug as appropriate. Thanks!
Assignee: nobody → dmaher
Status: NEW → ASSIGNED
Flags: needinfo?(jschneider)
Flags: needinfo?(dmaher)
|
|
Reporter | |
Comment 8•9 years ago
|
||
Works for me!
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•