[input] Push Firefox Input 4.2 to production

RESOLVED FIXED

Status

--
minor
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: davedash, Assigned: oremj)

Tracking

Details

(Whiteboard: [6/28/2011])

Preferably on 6/28

Here's some notes:

http://etherpad.mozilla.org:9000/input-4-2-push

Wait for confirmation on tagging and whatnot.

Comment 1

7 years ago
let us when you are ready.
Whiteboard: [6/28/2011]

Updated

7 years ago
Assignee: server-ops → jeremy.orem+bugs

Updated

7 years ago
Depends on: 666290
(Assignee)

Updated

7 years ago
No longer depends on: 666290

Updated

7 years ago
Depends on: 667953
(Assignee)

Comment 2

7 years ago
Should this be tomorrow instead?
I'd be fine with that - we still have that ES_settings blocker too that we'll want to take care of.

What time is good for you?
(Assignee)

Comment 4

7 years ago
4pm today?

Updated

7 years ago
Depends on: 621996

Updated

7 years ago
No longer depends on: 621996

Updated

7 years ago
Depends on: 668363
(Assignee)

Comment 6

7 years ago
bin/update_prod.sh 
+ SVN=/usr/bin/svn
+ INPUT_DIR=/data/input/python/input.mozilla.com/reporter
+ VENDOR_DIR=/data/input/python/input.mozilla.com/reporter/vendor
+ SYNC_DIR=/data/input/www/django/input.mozilla.com/reporter/
+ pushd locale
+ /usr/bin/svn revert -R .
Reverted 'uk/LC_MESSAGES/messages.mo'
Reverted 'zh_TW/LC_MESSAGES/messages.mo'
+ /usr/bin/svn up
At revision 91847.
+ ./compile-mo.sh .
+ popd
+ echo -e 'Updating vendor...'
Updating vendor...
+ cd /data/input/python/input.mozilla.com/reporter/vendor
+ git pull
Already up-to-date.
+ git submodule update --init
+ echo -e 'Updating reporter...'
Updating reporter...
+ cd /data/input/python/input.mozilla.com/reporter
+ git fetch origin
+ git checkout origin/prod
M	bin/update_prod.sh
HEAD is now at 4889f09... Merge pull request #9 from nigelbabu/fix-theme
+ git submodule update --init
+ cd /data/input
+ /usr/bin/rsync -aq --exclude '.git*' --delete /data/input/python/ /data/input/www/django
+ cd /data/input/www/django/input.mozilla.com/reporter/
+ schematic migrations
+ /usr/bin/python26 /data/input/python/input.mozilla.com/reporter/manage.py cron get_highcharts
+ /usr/bin/python26 /data/input/python/input.mozilla.com/reporter/manage.py compress_assets
+ '[' -d /data/input/www/django/input.mozilla.com/reporter//migrations/sites ']'
+ schematic migrations/sites
+ /data/input/deploy
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
QA verified. Site is alive and has a steady heartbeat. Thanks oremj and davedash
Status: RESOLVED → VERIFIED
Re-opening so we can:

unset ES_DISABLED

and run 

./manage.py cron index_all
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 9

7 years ago
Was this dependent on ops taking over ES?
(Assignee)

Comment 11

7 years ago
Corey, are those ES servers ready to use for input?
(In reply to comment #11)
> Corey, are those ES servers ready to use for input?

They are waiting on someone to test them, yes.  I would not put anything production on them until they have been tested..

Details are in bug 665186
(In reply to comment #12)
> (In reply to comment #11)
> > Corey, are those ES servers ready to use for input?
> 
> They are waiting on someone to test them, yes.  I would not put anything
> production on them until they have been tested..
> 
> Details are in bug 665186

Corey/Oremj - for input this would be write-only so if Elastic completely was hosed there would be no public visibility... just noise in the logs.
(Assignee)

Comment 14

7 years ago
I've pointed the config at our new ES cluster. It should take effect on the next update.
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.