Closed
Bug 786820
Opened 12 years ago
Closed 12 years ago
New bouncer cluster
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cshields, Assigned: cturra)
References
Details
(Whiteboard: [tracker][2012q3][waiting][webtools][qa])
bouncer on pp-app-dist* needs to be replaced. I won't call it "unmaintainable" in its current state, but it certainly is not up to our standards. Now that we know it is going to be kept and actively developed, we will build a new adm, dev, stage, prod environment for it that meets our current standards.
Assignee | ||
Comment 1•12 years ago
|
||
bouncer-notes etherpad from initial discussions: https://etherpad.mozilla.org/bouncer-notes
Reporter | ||
Comment 2•12 years ago
|
||
Docs to fill out for this cluster: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=26414718
Comment 3•12 years ago
|
||
The current setup of bouncer stage / download.allizom.org (the PHP public side app) is out of Git (https://github.com/fwenzel/tuxedo/tree/master/bouncer) and should be able to be copied (the directory layout and Apache virtual host config) to the new cluster and also used to get the new dev and prod going The bounceradmin side, which is a Django app, is going to require a few more steps to copy/setup The current stage and prod setups are using a virtualenv (which we don't use in production deployments anywhere else) and it only has a https://github.com/fwenzel/tuxedo/blob/master/requirements.txt There is currently not a vendor submodule, like our Django/Playdoh apps, and I'm unsure of the level of effort to get the pure python dependencies packaged into a submodule
Comment 4•12 years ago
|
||
After reviewing https://etherpad.mozilla.org/bouncer-notes I realize I'd forgotten about the Perl sentry cron job stuff This part I never did finish getting working in staging, I was focused on just verifying the PHP side worked in bug 750798, so that is an unknown quantity of work, as it's a set of Perl scripts and dependencies that were installed on a RHEL 5.5 box in SJC1, then we P2V'd into a VM in SCL3. I suspect this will take the longest and we may need a little help from :justdave to verify it's working, but all is possible with Mozilla IT Let me know if I can shed any more light on things, as I did the bouncer stage setup and the migration of im-sentry01 to SCL3
Assignee | ||
Updated•12 years ago
|
Whiteboard: [tracker][2012q3][pending triage] → [tracker][2012q3][pending testing]
Comment 6•12 years ago
|
||
The dev and stage environments are alive and in use. The new prod environment is completed, but not currently in "production"... need QA/webtools sign-off to do that after some testing.
Whiteboard: [tracker][2012q3][pending testing] → [tracker][2012q3][waiting][webtools][qa]
Comment 7•12 years ago
|
||
I think we're done here. Chris, anything left you're still planning to do or can we close this bug out? :)
Flags: needinfo?(cturra)
Assignee | ||
Comment 8•12 years ago
|
||
:jakem - thnx for the reminder. yes, this bug can be closed. marking r/fixed.
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(cturra)
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•