Closed
Bug 1207867
Opened 9 years ago
Closed 9 years ago
Redirect Sync 1.1 traffic to the EOLinator.
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Cloud Services
Operations: Miscellaneous
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bobm, Assigned: bobm)
References
Details
Beginning 10/1/2015 start redirecting Sync 1.1 traffic to the EOLinator service. This includes all of the various Sync 1.1 properties: AP, REG, JPAKE, as well as the Sync 1.1 server nodes. The privacy notice should be redirected to the Firefox accounts privacy notice.
A basic, high level plan:
1. Redirect the DNS for one or two Sync 1.1 nodes to the EOLinator service.
2. Observe and let some amount of time pass.
3. Evaluate outcome, and if everything is go, resume redirecting the rest of the Sync 1.1 nodes to the EOLinator.
4. Redirect the AP, REG, and JPAKE properties to the EOLinator service.
5. Redirect the privacy policy.
6. Begin hardware decomission.
Comment 1•9 years ago
|
||
> 4. Redirect the AP, REG, and JPAKE properties to the EOLinator service.
FWIW, these may be better served by a separate service that just sends out 503s in the same manner as the 401inator, rather than re-using the custom EOLinator service designed for the storage nodes. I believe the storage-node EOLinator will give a 404 on URLs it doesn't recognize, rather than a 503.
(Or we could change sync11eol server to 503 requests to unknown URLs instead of a 404)
Assignee | ||
Comment 2•9 years ago
|
||
(In reply to Ryan Kelly [:rfkelly] from comment #1)
> (Or we could change sync11eol server to 503 requests to unknown URLs instead
> of a 404)
We can do that at the Nginx layer with an appropriate location directive for the 503 error page:
proxy_intercept_errors on;
error_page 404 =503 /503.html; # Change 404s to 503s
Comment 3•9 years ago
|
||
> We can do that at the Nginx layer with an appropriate location directive for the 503 error page:
SGTM
Assignee | ||
Comment 4•9 years ago
|
||
Starting decommission with three database hosts, representing 90 logical Sync nodes.
Assignee | ||
Comment 5•9 years ago
|
||
Step 3. completed. Moving on to the rest.
Assignee | ||
Comment 6•9 years ago
|
||
Tracking remaining work in Bug 1216024. Closing this bug.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 7•9 years ago
|
||
Marking this VERIFIED to get it off my to-do list.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•