Closed Bug 699962 Opened 13 years ago Closed 13 years ago

QA and deploy BrowserID train-2011.11.03 to production

Categories

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

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: lhilaiel, Assigned: jbonacci)

References

()

Details

ChangeLog including issues resolved: 
https://github.com/mozilla/browserid/blob/29a248/ChangeLog#L1-22

[QA] Suggested areas of focus for QA:
  * normal regression testing
  * verify closed bugs referenced in changelog

[RELEASE ENGINEERING]:
  * keysigner is added, requires a /etc/monit/start_keysigner and a /etc/monit.d/keysigner
  * all start scripts need new env vars: 'BROWSERID_URL' and 'KEYSIGNER_URL'
  * paths to all binaries has changed  bin/<binary> rather than <binary>/run.js
  * explicitly must specify ports in start scripts

Practically speaking, to handle the above you should:
  1. copy /etc/monit/start_{browserid,verifier,keysigner} from beta to prod
  2. change diresworb.org to browserid.org in those files
  3. delete /etc/monit.d/*
  4. copy over /etc/monit.d/{keysigner,browserid,verifier} from beta to prod
  5. update /home/git/post-update script - specifically checking new restart url and path to compress.sh and path to ver.txt
  6. git push to server to update code
  7. as the push is running, restart monit (sudo /etc/init.d/monit restart)
No longer depends on: 696415
Assignee: server-ops-labs → jbonacci
Summary: QA and deploy BrowserID train-2011.10.27 to production → QA and deploy BrowserID train-2011.11.03 to production
QA picks up this train for testing.
Status: NEW → ASSIGNED
Noting some additional logs and one new process:

Process:
/usr/local/bin/node /home/browserid/code/bin/keysigner

Logs:
browserid-error.log
verifier-error.log
keysigner-error.log
keysigner.log
Forgot to add that the new *-error logs are empty.
The keysigner.log file is picking up a lot of information of the following type:
{"level":"info","message":"127.0.0.1 - - [Fri, 04 Nov 2011 23:05:25 GMT] \"GET /__heartbeat__ HTTP/1.1\" 200 - \"-\" \"monit/5.0.3\""}
{"level":"info","message":"127.0.0.1 - - [Fri, 04 Nov 2011 23:05:25 GMT] \"GET /__heartbeat__ HTTP/1.1\" 200 - \"-\" \"-\""}
...etc...
OK. QA finally signs off on the 11/03/2011 release in Beta.

Critical fixes for the next Beta:
540: Apparent "uncaughtException" in browserid.log on Stage
548: Beta: seeing unexpected database failure on attempt to sign in with known email/account

Important fixes for the next Beta (so says QA):
418: Beta environment needs a second RP (client site)
which is "blocked" by
35: Unable to log out of beta.myfavoritebooze.org
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
540 and 548 will def make it into the next beta (are already in dev) 418/35 will be fixed immediately after.
beginning production deployment...
train 2011.11.03 is live in production: https://browserid.org/ver.txt
Verified push to Prod.
Status: RESOLVED → VERIFIED
Blocks: 701934
Blocks: 703596
No longer blocks: 703596
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.