Closed
Bug 624777
Opened 15 years ago
Closed 15 years ago
Update bounceradmin in production
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wenzel, Assigned: jabba)
References
Details
(Whiteboard: [01/13/2011 @ 4pm][no-announce])
Release engineering needs Bouncer to pick up locale changes by default. I made the necessary code changes, and now we need them deployed, please. This is *only* the admin interface to bouncer, so only a single host, not an update of all our download.m.o webheads.
- go to the tuxedo sourcecode dir
- activate the tuxedo virtualenv
- git pull origin master
- pip install -e git://github.com/fwenzel/django-mozilla-product-details#egg=django-mozilla-product-details
- run: ./manage.py update_product_details
Then set up a cron job to run this manage.py command (within the virtualenv!) every few hours. Please make sure that it's run as the user that owns the JSON files.
By default, the JSON files will live in tuxedo/inc/product-details/json within the code base. If you don't want that, please set PROD_DETAILS_DIR = '...' appropriately in local_settings.py.
Thanks!
Reporter | ||
Comment 1•15 years ago
|
||
Let's find a time and person to do this, go ahead and lower the severity after you triage it.
If forgot to add:
- End user impact: None.
- Internal impact: Releng can't use the Tuxedo API while the update is underway. But they can't anyway (bug 624658), which is why we are doing this in the first place.
Comment 2•15 years ago
|
||
I'm getting conflicting signals - is this critical enough to do outside of a window or should we wait for a window?
Reporter | ||
Comment 3•15 years ago
|
||
CCing Rail and Armen: How urgent is this, do we need to push this ASAP, or is waiting for a window (say, Thursday) fine?
Comment 4•15 years ago
|
||
It should be done at least some hours before Firefox 4 beta9 release. AFAIK, it's planned this Friday, so Thursday sounds good.
Comment 5•15 years ago
|
||
Ok thanks, we will do this 11/13 @4
Severity: critical → normal
Whiteboard: [11/13 @4:00]
Comment 6•15 years ago
|
||
(In reply to comment #5)
> Ok thanks, we will do this 11/13 @4
Won't November be a bit late?
Reporter | ||
Comment 7•15 years ago
|
||
(In reply to comment #6)
> (In reply to comment #5)
> > Ok thanks, we will do this 11/13 @4
>
> Won't November be a bit late?
haha.
Whiteboard: [11/13 @4:00] → [1/13 @4:00]
Updated•15 years ago
|
Flags: needs-downtime+
Whiteboard: [1/13 @4:00] → [01/13/2011 @ 4pm][no-announce]
Reporter | ||
Comment 8•15 years ago
|
||
Corey: Who'll pick this up tonight?
Updated•15 years ago
|
Assignee: server-ops → jlazaro
Reporter | ||
Comment 10•15 years ago
|
||
All right, I landed this on master:
http://github.com/fwenzel/reporter/commit/ca42a0f
Will file an IT bug to get this cron job set up on stage, then close this.
Status: NEW → ASSIGNED
Reporter | ||
Comment 11•15 years ago
|
||
(In reply to comment #10)
> All right, I landed this on master:
Ignore this: This comment has nothing to do with this bug. Sorry!
Updated•15 years ago
|
Assignee: jlazaro → jdow
Assignee | ||
Comment 12•15 years ago
|
||
Push is done.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•6 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
•