Closed Bug 1009096 Opened 11 years ago Closed 11 years ago

Deploy tokenserver and browserid-verifier tag 0.2.1 to Production

Categories

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

Product:
Cloud Services
Component:
Operations: Deployment Requests - DEPRECATED
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jbonacci, Assigned: mostlygeek)

References

Details

(Whiteboard: [qa+])

No description provided.
Whiteboard: [qa+]
Depends on: 996763
Deployment steps: 1. Create the new browserid-verifier stack 2. Update the TokenServer servers w/ new secrets, manage_puppet -as -o '-v' - do one to make sure the current system works w/ the new config ok - this just adds an https:// scheme to where the verifier servers are 3. update the remaining TokenServer machines 4. swap the DNS for verifier.accounts.firefox.com to the new stack 5. make sure traffic is flowing normally 6. tear down the old stack
Assignee: nobody → bwong
:mostlygeek do you have a schedule in mind for these changes and the deployment?
Status: NEW → ASSIGNED
Tomorrow afternoon.
As noted in Bug 996763, this depends on config change here: https://github.com/mozilla-services/puppet-config/pull/477
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Awesome. Thanks.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.