Closed Bug 485609 Opened 16 years ago Closed 16 years ago

Set up and document hot-swappable deployment plan for mozilla.com

Categories

(mozilla.org Graveyard :: Server Operations: Projects, task)

Product:
mozilla.org Graveyard
Component:
Server Operations: Projects
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: morgamic, Unassigned)

References

Details

(Whiteboard: 2009Q2)

Currently, mozilla.com pushes are suboptimal: - takes too much time - best-case, site temporarily gets stuck in a quasi-state - worst-case, site gets stuck in said state for a while We should: - keep another docroot with mozilla.com on it, naming it something fun - perform all deployment operations on that alternate docroot - instantaneously switch from the "hot" docroot to the updated docroot - repeat for subsequent releases How IT decides to implement it is up to them, but the main idea is to avoid ever having mozilla.com in a non-solid state (which could potentially happen no matter what RCS you use).
An added advantage of this is you can revert quickly as well.
For smaller mozilla.com changes via kubla, we don't need to do this but when we're pushing hundreds of new files for a dot release we should implement this strategy since there is a higher risk of delay or failure.
I think is is going to be a pretty large project/rework of our current system. Q2 goal?
What if we just used a symlink? :)
Assignee: server-ops → nobody
Component: Server Operations → Server Operations: Projects
Whiteboard: 2009Q2
Beltzner - :)
Sadly, Beltzner alone will not be able to solve this problem for you, though he will cheer from the sidelines, complete with a fuzzy-finger if it will help.
I was just cc-ing you because you asked me to.
Depends on: 488762
Has anybody had time to look at this? As the sites grows larger we're having more problems with git/svn/deployment.
Currently it depends on bug 488762, which is a Q2 goal.
Group: infra
Any progress on this? Would really suck to try to update 3.5 content then have it fail on us again because of SVN. We should avoid that.
3.5 is being tracked over in bug 495326.
We did this for 3.5 and have made changes to how quickly we can push stuff out too. I feel like we can call this done.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.