Closed Bug 1351106 Opened 9 years ago Closed 9 years ago

set up virtual-redirect cluster

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Atoll, Assigned: Atoll)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/4504])

We're migrating virtual-redirect from static to generic, which will require updating hundreds of entries in DNS, so we may as well do it the right way the first time and point them all at a dedicated endpoint just for redirects.
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/4504]
redirects.external.zlb.scl3.mozilla.com A/PTR 63.245.213.17, CHG0011498
Traffic IP Group: redirects.external.zlb.scl3.mozilla.com Virtual Server: redirects-http (HTTP, port 80) Virtual Server: redirects-https (HTTP, port 443, SSL-decrypt) Merged the relevant TS rules from generic (for the pool nodes) and static (for the redirects). Currently routing requests to static pool, will cutover to generic pool gradually.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Assignee: server-ops-webops → rsoderberg
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.