Closed
Bug 891149
Opened 11 years ago
Closed 11 years ago
please deploy browserid train-2013.06.19 to production
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jrgm, Assigned: gene)
References
Details
Gene, please build production stacks for browserid train-2013.06.19. From bug 885160: SHA: 4627b8858a5f5e50095eb178b0829125379ba065 output rpm on r6: /home/jrgm/workspace/browserid/rpmbuild/RPMS/x86_64/browserid-server-0.2013.06.19-3.el6_117672.x86_64.rpm NOTE: this also requires the addition of `"firefoxos_url": "https://firefoxos.persona.org",` to browserid/config/production.json
Reporter | ||
Updated•11 years ago
|
Assignee: nobody → gene
Assignee | ||
Comment 1•11 years ago
|
||
These stacks are built but no dns is pointed to them. These stacks have an identity-bridge-gmail tier though it's not enabled in the webheads. This is in case we want to use this tier on Wednesday. (We'll still need to determine the number of instances and instance size appropriate for load levels based on load testing. https://github.com/mozilla/identity-ops/wiki/Interim-AWS-Stack-List#stack-0710--production--us-west-2 https://github.com/mozilla/identity-ops/wiki/Interim-AWS-Stack-List#stack-0710--production--us-east-1
Assignee | ||
Comment 2•11 years ago
|
||
jrgm : let me know if these look good after which point we can coordinate setting them live with DNS
Flags: needinfo?(jrgm)
Reporter | ||
Comment 3•11 years ago
|
||
gene: something's not right in us-west-2 (haven't looked at us-east-1 yet). When I enter an email address, it immediately shows "Sorry, we already sent an email to that address". This suggests perhaps a problem in talking to the database.
Flags: needinfo?(jrgm)
Reporter | ||
Comment 4•11 years ago
|
||
Hmm, weird. This just "disappeared" at some point (was there for just a few minutes).
Assignee | ||
Comment 5•11 years ago
|
||
John, that was probably right at the time Brandon was doing his staging DB upgrade/maintenance. How do the stacks look otherwise?
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(jrgm)
Assignee | ||
Comment 6•11 years ago
|
||
Sorry that was me being confused, this is unrelated to staging, disregard my Comment 5
Reporter | ||
Comment 7•11 years ago
|
||
I forgot to update here. train-2013.06.19 looks good to go, pending some clarification of a recent report of an issue on b2g and whether we need to hold off changing prod persona.
Flags: needinfo?(jrgm)
Assignee | ||
Comment 8•11 years ago
|
||
John, are we clear to put traffic on this stack?
Flags: needinfo?(jrgm)
Assignee | ||
Comment 9•11 years ago
|
||
Talking to John in Vidyo and we're clear. 10:55 updated yahoo.login.persona.org to the new stack (same code, no change) 11:00 turned down listeners for yahoo.login.persona.org on the old stack to force clients to the new stack
Flags: needinfo?(jrgm)
Assignee | ||
Comment 10•11 years ago
|
||
11:04 updated login.persona.org to point to the new 0710 stack
Assignee | ||
Comment 11•11 years ago
|
||
11:09 80 and 443 listeners are disabled on stack 0625 forcing everyone onto the new stack
Assignee | ||
Comment 12•11 years ago
|
||
deployment complete, site looks good
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•