Closed
Bug 707761
Opened 13 years ago
Closed 12 years ago
Move and rename developer-stage9.mozilla.org to developer.allizom.org
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: stephend, Assigned: nmaul)
References
()
Details
(Whiteboard: [start on 12/20])
https://developer-stage9.mozilla.org needs a new cert: developer-stage9.mozilla.org uses an invalid security certificate. The certificate expired on 12/2/2011 2:55 AM. The current time is 12/5/2011 11:00 AM. (Error code: sec_error_expired_certificate)
Comment 2•13 years ago
|
||
Going to punt to jakem. Jake, this needs to go to allizom, since it's a stage server.
Assignee: server-ops → nmaul
Updated•13 years ago
|
Summary: developer-stage9.mozilla.org needs a new certificate → Move developer-stage9.mozilla.org to developer-stage9.allizom.org
Assignee | ||
Comment 3•13 years ago
|
||
The MDN devs have indicated they would like to hold off on this until around Dec 20, at which point they'll be past their current integration efforts and will be ready to do this (and other) changes to -stage9. Also, the new name should be developer.allizom.org... the -stage9 moniker was only useful during the MindTouch 9->10 upgrade. Might as well clean that up while we're here.
Whiteboard: [start on 12/20]
Reporter | ||
Comment 4•13 years ago
|
||
Jake: should it be developer-dev.allizom.org, though, to be consistent? It's updated from master, right?
Summary: Move developer-stage9.mozilla.org to developer-stage9.allizom.org → Move and rename developer-stage9.mozilla.org to developer.allizom.org
Comment 5•13 years ago
|
||
We're going to copy the SUMO setup, so: developer-dev.allizom.org will track our 'master' branch developer.allizom.org will track our 'next' branch And we'll want to use fredo and chief if we can.
Comment 6•12 years ago
|
||
Bump. I realize it's approaching the end of the quarter here, but an ETA would be good. We'd really like to get this changed before we start doing things like adding KumaScript services and other things that will make this more challenging later.
Assignee | ||
Comment 7•12 years ago
|
||
@cshields: I don't recall... did we decide if we want to move devmo to SCL3 or PHX1? I'm ambivalent about it. Either way, this seems like a good job for: VM admin node VM dev node VM stage node Seamicro Xeon prod nodes Seem reasonable? Within a couple weeks I think we can be good to go in either place with something like that.
Assignee | ||
Comment 8•12 years ago
|
||
We're actually not going to do this after all. Instead, we're spinning up a new "developer-dev.allizom.org" node to become the new primary Django-only dev node (ultimately replacing kuma-stage, once there's no need for that anymore). Then we'll do a Django-only stage node (developer.allizom.org), and finally a django-only prod cluster, when Kuma/Kumascript are ready to take over for Mindtouch. -stage9 will remain the primary Django+Mindtouch dev/staging site until Mindtouch is retired and it's no longer needed. We've moved the VMs to SCL3, so there's no hurry for this on IT's end of things. The live prod site is moving on Tuesday, and will be in a similar situation... it will remain in use until Django takes over completely.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•