Closed Bug 975572 Opened 12 years ago Closed 12 years ago

please deploy fxa content-server 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: jrgm, Assigned: gene)

Details

The train-01 rpm that was in stage is: s3://net.mozaws.ops.rpmrepo-stage/6/x86_64/fxa-content-server-svcops-0.9.0-20140211git66de7e2.el6.x86_64.rpm Gene: can you please build a production fxa-p-c-N stack with that rpm.
Status: NEW → ASSIGNED
new stack is up, this is the elb fxa-p-c-4-ContentS-3HMH5R5LHWTI-1903824586.us-west-2.elb.amazonaws.com
Flags: needinfo?(jrgm)
Okay, QA signs off on putting train-01 fxa-content-server in production.
Flags: needinfo?(jrgm)
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.