Closed Bug 1266137 Opened 9 years ago Closed 7 years ago

cut over to 200-inator service in production

Categories

(Data Platform and Tools :: General, defect, P2)

Product:
Data Platform and Tools
Component:
General
Type:
defect
Points:
1

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: thuelbert, Unassigned)

Details

(Whiteboard: [SvcOps])

Assignee: nobody → tblow
Whiteboard: [SvcOps]
as per Travis assigning to :whd to handle early next week. 1 point and p1.
Assignee: tblow → whd
Points: --- → 1
Assignee: whd → nobody
Priority: P1 → --
Hi all, Important update: Please hold off on the actual implementation of this until at least July 2016. FHRv2 decommissioning is being delayed. Sean can provide more context. Thanks. Nushin
Sean, could you update this bug with the go live date for the service? Thanks.
Flags: needinfo?(srich)
Priority: -- → P5
IT ended up setting up their own 200inator, so they don't need ours. Closing this.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(srich)
Resolution: --- → WONTFIX
Reopening this per email discussion. Looks like we should deploy the 200inator after all, since there are still a substantial number of requests hitting the old FHR endpoint. Shyam, are you able to take care of redirecting the network requests to fhr.data.mozilla.com once we have this service set up?
Status: RESOLVED → REOPENED
Component: Metrics: Pipeline → Pipeline Ingestion
Flags: needinfo?(smani)
Priority: P5 → P2
Product: Cloud Services → Data Platform and Tools
Resolution: WONTFIX → ---
Mark, If whd stands this up somewhere, we can surely change the DNS to point there and that should start receiving the FHR requests. I don't think it'll need redirection of any kind. Thanks!
Flags: needinfo?(smani)
I've resurrected this endpoint at https://fhr.r53-2.services.mozilla.com. As :fox2mike mentioned, changing DNS to cut over should be sufficient. https://github.com/mozilla-services/svcops/pull/1406 https://github.com/mozilla-services/puppet-config/pull/2730
Filed CHG0012866 and spoke with :whd, we'll do this on Monday, May 7th at 1100 PDT.
KK - am working on getting test resources in place for go live. Sounds like we'll need to be ready at the above time/date.
I just made the change, DNS will propagate in a bit.
DNS propagated and testing is considered complete. Closing this.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 7 years ago
Resolution: --- → FIXED
Component: Pipeline Ingestion → General
You need to log in before you can comment on or make changes to this bug.