988692 - Deploy revision 34eb2426155c01636a01f2847ceef321cf80d852 of browserid-verifier

Status: VERIFIED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[Ryan Kelly [:rfkelly]]

(Benson, I'm not sure what tagging conventions or what-have-you are in use here, happy to adjust whatever as appropriate)

Please deploy browserid-verifier revision 34eb2426155c01636a01f2847ceef321cf80d852 to fxa-verifier stage, and eventually through to prod.  This version gives the ability to tweak the max-lag value via config file settings, which is needed to continue investigation of Bug 988101.

Comment 1

[Benson Wong [:mostlygeek]]

I've been tagging master with the anticipation that we're inching closer to 1.0.0.

Comment 2

[Benson Wong [:mostlygeek]]

Deployed. When :jbonacci says ok to swap the DNS over I'll do that and tear down the old stack (fxa-s-bv-2013-03-20).

Comment 3

[James Bonacci [:jbonacci]]

:mostlygeek go for it. We need to test with this new deploy.
I will start the verification as soon as you swap the DNS.

Comment 4

[Benson Wong [:mostlygeek]]

Swapped over. I'll tear down the old stack after you've verified the new one.

Comment 5

[James Bonacci [:jbonacci]]

:mostlygeek or :rfkelly
Is this merged fixe in the deployment?
https://github.com/mozilla/browserid-verifier/pull/29

Comment 6

[James Bonacci [:jbonacci]]

And what about this merged fix?
https://github.com/mozilla/browserid-verifier/pull/30

Comment 7

[Benson Wong [:mostlygeek]]

:jbonacci Yup. https://github.com/mozilla/browserid-verifier/commits/master. Commit:  34eb242 has #29 and #30 in it.

Comment 8

[James Bonacci [:jbonacci]]

I verified the deployment to Stage and the code version.
I ran a short load test - the Verifier logs look pretty clean.