Closed
Bug 1471319
Opened 7 years ago
Closed 7 years ago
[TCW] migrate hgmo from SCL3 to MDC1
Categories
(Developer Services :: Mercurial: hg.mozilla.org, enhancement)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: fubar, Assigned: fubar)
References
Details
Filing bug for CAB / TCW.
We're expecting to migrate services from SCL3 to MDC1 on July 14th during the next TCW. We'll need to have support from IT either on hand, or readily available - sanvm on-hand for final cutover of NFS data, netops and webops available for any flow or zlb issues, and someone to assist with the DNS change itself.
Flags: needs-treeclosure?
Comment 1•7 years ago
|
||
How should we handle communication of the hg.mo outage during the TCW? I know previously Hal sent out notifications for TCW. Not sure if he's still doing that in his new role.
While it's my intention for https://hg.mozilla.org/ (the HTTP endpoint) to be available for the duration of the TCW if possible, there's a chance it won't. To my knowledge, this service hasn't disappeared off the net in... years. IMO that warrants a wide notification net.
We have taken ssh://hg.mozilla.org/ (the SSH/writable) endpoint offline during TCW before. Or at least we've made the service read-only before. This warrants communication. But I don't think the impact is as severe as the read-only HTTP endpoint.
Flags: needinfo?(klibby)
| Assignee | ||
Comment 2•7 years ago
|
||
He's not; Kim, would you send out the announcements? Hal would send them to dev-planning, dev-tree-management, and dev-platform. The MOC will still be sending out their own message, but it will probably be light on details.
Keeping https:// up seems reasonable; it's a RO endpoint and the replication will already be in place.
Flags: needinfo?(klibby) → needinfo?(kmoir)
Comment 3•7 years ago
|
||
Sure, I can send out the announcement. (I apologize for the delay in responding, I was on PTO last week). I'll craft a message and share it with Kendall and Greg for review.
Flags: needinfo?(kmoir)
Comment 4•7 years ago
|
||
Kendall, looking at Hal's past notices re TCW, they list all the bugs associated with the TCW for the day. Should this notice also do this or just note the service disruptions for hg.m.o. Is there a spreadsheet for other bugs? I noticed in other TCW Linda (not here anymore :-() had a spreadsheet with estimated timeframes and impact.
Flags: needinfo?(klibby)
| Assignee | ||
Comment 5•7 years ago
|
||
AFAIK there isn't currently a spreadsheet; the folks that once did all that have moved on, so the process is in flux...
I think I'd just link to bug 1472833, which is the overall tracker and has links to the work being performed.
Flags: needinfo?(klibby)
| Assignee | ||
Comment 6•7 years ago
|
||
Actually, belay that. I'd copy what's in that bug and email it around, because BMO will be dark for up to 8hrs that day!
Comment 7•7 years ago
|
||
The TCW is behind us. I'm pretty sure that means this bug can be closed.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needs-treeclosure?
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•