Closed
Bug 1122176
Opened 11 years ago
Closed 11 years ago
Please setup DNS name for Loop-Push
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
x86_64
Linux
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: benbangert, Assigned: oremj)
Details
Currently the loop-push DNS names are based on the assumption that we will deploy new clusters and each one will have a DNS name that round-robin's to the machines in that cluster.
For the use of loop-push however, we will be populating a single DNS name with 'available' machines from all clusters. This DNS name should be setup and configured with the current cluster until the script that auto-updates the name is ready.
Perhaps something like wss://push.hello.firefox.com/
![]() |
Reporter | |
Updated•11 years ago
|
Assignee: nobody → oremj
Assignee | ||
Comment 1•11 years ago
|
||
Route53 round robin works by adding and removing multiple records with the same name, rather than altering one record. So there really isn't an prep here, once your script starts adding records, it will just work. In the mean time, I'd rather not add the current cluster, because it would become out of date when we push or if an autoscale event happens.
To get this to production, I'd suggest:
1. Write script (dev)
2. Start running script, on instance with route53 permissions, and wait until record populates (ops)
3. Update loop config to point to our new name (ops)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•