Closed Bug 974675 Opened 12 years ago Closed 12 years ago

please deploy fxa train-01 branch 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:
RESOLVED FIXED

People

(Reporter: edwong, Assigned: gene)

Details

:jrgm from stage - So I've run remote and a mild load test against stage and looks good (mild load, to not trigger using up on all the mysql connections, which I subsequently have now done). SO the rpm that is s3 can go to production for fxa-auth-server: s3://net.mozaws.ops.rpmrepo-stage/6/x86_64/fxa-auth-server-svcops-0.9.0-20140219gite43ef01.el6.x86_64.rpm
Assignee: nobody → gene
OS: Mac OS X → All
Hardware: x86 → All
:gene how we looking on a deploy today?
Status: NEW → ASSIGNED
stack fxa-p-a-2 is up in us-west-2 (new IAM). Check it out and upon approval I'll point DNS to it.
Flags: needinfo?(edwong)
ELB for fxa-p-a-2 is fxa-p-a-2-AuthServ-1IS8VI3WMMLEK-1240517833.us-west-2.elb.amazonaws.com
my bad - I didn't ask to deploy both content and auth-server rpms. jrgm can you hand off the content server rpm. thanks.
Flags: needinfo?(edwong) → needinfo?(jrgm)
content server deploy to prod logged here: bug 975572
Flags: needinfo?(jrgm)
Okay, QA signs off on putting train-01 fxa-auth-server in production.
DNS is updated to bring the new stack live
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.