Deploy Autograph 3.0.2
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Tracking
(Not tracked)
People
(Reporter: jvehent, Assigned: u581815)
References
(Blocks 1 open bug)
Details
Get db credentials into the autograph config (bug 1533178) then please deploy Autograph 3.0.0 to staging and perform QA testing.
https://mana.mozilla.org/wiki/display/SVCOPS/Autograph#Autograph-QA
TODO: make sure the crypto11 lib update doesn't regress HSM connection timeouts https://github.com/mozilla-services/autograph/pull/132
Deployed to stage w/ DB disabled.
(In reply to Greg Guthe [:g-k] [:gguthe] from comment #2)
TODO: deploy monitor to recognize new signer type
deployed monitor in job 49
(In reply to Greg Guthe [:g-k] [:gguthe] from comment #1)
TODO: make sure the crypto11 lib update doesn't regress HSM connection timeouts https://github.com/mozilla-services/autograph/pull/132
Looks good. Tested signing the lockbox addon from edge (which uses an HSM key) waited 2 minutes and resigned with errors, while watching the logs.
For stage QA:
-
monitoring lambda is passing.
-
content signature is unchanged (so skipping kinto and shield QA)
-
:aki can you test mar signing in stage (now that we have the technology)?
|
||
Comment 6•6 years ago
|
||
Verified in stage.
|
|
||
Updated•6 years ago
|
(In reply to Aki Sasaki [:aki] from comment #6)
Verified in stage.
Thank you!
I think we're OK to deploy prod tomorrow.
I forgot to do this. Let's deploy 3.0.2 to stage this Tuesday and prod on Wednesday.
3.0.2 is deployed to stage.
For stage QA:
-
monitor lambda is passing
-
content signature is unchanged (so skipping kinto and shield QA)
-
:aki do you want to test mar signing in stage again?
|
|
||
Comment 10•6 years ago
|
||
Stage looks good.
|
Assignee | |
Comment 11•6 years ago
|
||
Prod is deployed. Starting QA.
|
|
Assignee | |
Comment 12•6 years ago
|
||
Prod QA:
- monitor is passing
- content signature is unchanged (so skipping kinto and shield QA)
- AMO is using the other stack
Description
•