589817 - Push contents of input.stage to production on 8/26

Status: VERIFIED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Aakash Desai [:aakashd]]

We need a push of input.stage.mozilla.com to production on Thursday, 8/26,
sometime between 12AM to 2AM PST.

The only step to perform now (thanks to the amazing shyam) is to run:

/root/bin/input_update.sh 


For more information, take a look at
https://bugzilla.mozilla.org/show_bug.cgi?id=583340#c7

Fred & Dave, please add more information if needed.

Comment 1

[Michael Kurze [:michaelk]]

Thanks for CC’ing me. On the metrics side, everything should update and work automatically. I'll be on IRC to make sure it really does.

Comment 2

[Justin Dow [:jabba]]

Looks like Shyam won't be around for this one. Jlazaro says he'll be awake to push this.

Comment 3

[Fred Wenzel [:wenzel]]

I won't be around (out Thu+Fri). Dave Dash, can you take this over? You guys should arrange for a more civilized time in the Pacific time zone then, considering neither Shyam nor I partake in the process.

What you'll need to do is update the ``prod`` tag to the commit you want to push live, and barring any minor bugs, running the update script on prod should work as promised in comment 0.

(I also usually ``git tag`` that revision, then push this tag to github, but that's purely cosmetic and I can do that when I return).

Comment 4

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

Can do.

jLaz - how bout 1pm?

Comment 5

[matthew zeier [:mrz]]

This is a stage site so from my vantage can get pushed whenever.  Not really clear what the time frame is optimizing for.

Comment 6

[Justin Lazaro [:jlaz] (use needinfo)]

1 PM sounds good :)

Comment 7

[Fred Wenzel [:wenzel]]

Nah, it's not a stage site, it's input.mozilla.com . But from my side that does not block a 1pm push.

Comment 8

[matthew zeier [:mrz]]

Oh, then I totally misunderstood.  This should go during our normal scheduled windows.  (7-11pm, Tues & Thur).

Comment 9

[Aakash Desai [:aakashd]]

Hey Matt, would it be possible to move this to 1pm like Dave Dash mentioned. His schedule varies due to his newborn once the day gets past 4pm and he's not sure if he can be available at 7pm.

Comment 10

[matthew zeier [:mrz]]

1pm is peak traffic.  If you can move peak traffic around, sure.

If Dash can't be available, we should push to a later date.

Comment 11

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

Let's try for 7 - if I'm not around we can delay it.  jlaz - my phone is in the phonebook if I'm not online at the time.

Comment 12

[matthew zeier [:mrz]]

This is going tonight but unless i'm mistaken doesn't really impact users?  Does it need an announcement?

Comment 13

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

It affects beta users, who may be leaving feedback about the product...

Should there be any downtime for this?  Not sure how pushes work, but if we push it to one host, and it checks out, we can propagate it to the rest, there's only minor DB changes that can be done without impacting users.

Comment 14

[Aakash Desai [:aakashd]]

Matt, it affects all Firefox 4 beta users and triagers. We'll be announcing this in a blog post (via my personal site) after the push to production. There's no official announcement from the mozilla.com blog.

Comment 15

[matthew zeier [:mrz]]

Will anything be down during this push?

Comment 16

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

no

Comment 17

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

ALSO:

Update the cron script (manage.py cron clusters) to go */3 hours

and run it once manually.

Comment 18

[Justin Lazaro [:jlaz] (use needinfo)]

Push was successful, shyam updated cron according to comment 17, wewt!

Comment 19

[Stephen Donner [:stephend] Not actively reading bugmail]

Pushed: http://input.mozilla.com.

Verified.