Closed Bug 1064438 Opened 10 years ago Closed 10 years ago

Staging & production should be running on the same configuration machine

Categories

(Tree Management :: Treeherder: Infrastructure, defect, P3)

Product:
Tree Management
Component:
Treeherder: Infrastructure
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1080595

People

(Reporter: emorley, Unassigned)

Details

Currently staging & dev are running on AWS, whereas production is running on IT managed infrastructure. 

AWS is running a different OS version amongst other things - in an ideal world we'd have the same setup on at least staging and production - and possibly also dev (though dev will likely still want to run non-minified assets, so is always going to be different to some extent anyway).
Priority: -- → P3
Summary: Staging & production (and possible dev) should be running the same configuration machine → Staging & production should be running on the same configuration machine
Blocks: 1072681
Depends on: 1079230
Now that the new stage VMs have been set up in bug 1079230, what work is left to get them up and running? Guessing:
1) Checking that puppet set up the dependencies correctly
2) Performing initial manage.py setup tasks
3) Switching DNS entries for the stage domain
:edmorley it's all in :fubar 's hands now.
Depends on: 1080595
No longer depends on: 1079230
Blocks: 1074927
Blocks: 1080757
No longer blocks: 1072681
No longer blocks: 1080757
Component: Treeherder → Treeherder: Infrastructure
stage & prod are now equivalent, from the infrastructure POV. eventually, it'll end up in AWS and then all three will match.
\o/
No longer blocks: 1074927
Status: NEW → RESOLVED
Closed: 10 years ago
No longer depends on: 1080595
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.