Closed
Bug 931999
Opened 11 years ago
Closed 10 years ago
Get a nucleus.mozilla.org URL pointed at the production instance
Categories
(Websites :: Nucleus, defect)
Websites
Nucleus
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 964971
People
(Reporter: hoosteeno, Unassigned)
References
Details
(Whiteboard: [kb=1163064] )
Once we have a production instance of nucleus running, let's get a DNS change that lets us use nucleus.mozilla.org.
Reporter | ||
Updated•11 years ago
|
Whiteboard: [kb=1163064]
Comment 1•11 years ago
|
||
I've pushed nucleus to the production cluster, but DNS is not set up yet, not even nucleus.paas.mozilla.org, because there is no wildcard DNS set up for the production paas, unlike the dev environment. I've verified that the instance is up and running via ssh, but we cannot yet access it over the web. I'm adding cturra requesting that we get the DNS entry (and SSL cert) set up for this instance
Flags: needinfo?(cturra)
Comment 2•11 years ago
|
||
:jgmize - the lack of a wildcard DNS entry on the production paas is by design. this allows us to be involved before an application is deployed into production the first time. before i move forward with these requests, i want to loop :ulfr into this discussion for security approval on the project.
Flags: needinfo?(cturra) → needinfo?(jvehent)
Comment 3•11 years ago
|
||
:adamm is currently working on the code review, that gates the production deployment.
Depends on: 909847
Flags: needinfo?(jvehent)
Reporter | ||
Comment 4•11 years ago
|
||
I think we should schedule the technical security review for sometime between 2013-12-11 and 2013-12-20 (pushing the DNS work to sometime after that). We're not quite ready right now for a review -- we still have major bits of code to write. Sorry for the mix-up!
Comment 5•11 years ago
|
||
Sorry, I misunderstood the proper procedures. There is security sensitive code (specifically django-browserid authentication for the admin) that I was trying to test in the paas environment prior to merging into the main branch, but issues with the dev paas are preventing me from pushing the code to it. I should have realized the security implications of adding a DNS entry to a mozilla.org subdomain would make a full security review a blocker for that.
Reporter | ||
Comment 6•11 years ago
|
||
There's a sec-review+ on bug 925553. Does that mean we're ungated for this?
Reporter | ||
Comment 7•10 years ago
|
||
We're up against a deadline here, and it's not clear whether we'll have a code review in time for our planned launch (see https://bugzilla.mozilla.org/show_bug.cgi?id=909847#c16). :cturra has confirmed that the code review will not block launch; so, in a pinch, we can move forward without it. It's my strong preference to launch reviewed code. I continue to discuss with the review team.
Reporter | ||
Comment 8•10 years ago
|
||
The repositories for this are linked from the wiki pages: https://wiki.mozilla.org/Websites/Mozilla.org/Publishing https://wiki.mozilla.org/Websites/Mozilla.org/Publishing/RNA These are both components requiring review.
Comment 9•10 years ago
|
||
Can I suggest we also get a dev environment setup and a url assigned to it,
Comment 10•10 years ago
|
||
:satdav there is a dev environment at https://nucleus.paas.allizom.org
Reporter | ||
Comment 11•10 years ago
|
||
Opened a bug for this in the appropriate IT component. Closing this one as a dupe.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•