Mozilla.com/Bedrock/Staging: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 9: Line 9:
= Status =
= Status =


* ''IT, please put your status here''
# Set up bedrockadm VM... no bug yet, need this provisioned to replace bedrockadm.seamicro.phx1 node, which has insufficient disk space.
# Migrate www-dev.allizom.org and www.allizom.org over to bedrockadm and the associated dev/stage servers.
# Set up a dev/stage database... will use the dev.db cluster that's already live in PHX1.
# Set up prod web cluster in PHX1... will need to order hardware.
# Migrate www.mozilla.org (prod site) to bedrock prod cluster, controlled by bedrockadm.
# Set up prod DB cluster in PHX1.
# Set up prod DB cluster in SCL3, master-master replication with PHX1.
 
Other things:
 
* Convert to github repo??? Bound to happen eventually, but no info on this yet.

Revision as of 18:56, 30 September 2011

Bedrock Staging Instance

This page tracks the progress of getting Bedrock dev/staging instances up. Hopefully we can set it up to make the future transition of mozilla.org to django as easy as possible (actually creating a production django environment).

Bugs

Status

  1. Set up bedrockadm VM... no bug yet, need this provisioned to replace bedrockadm.seamicro.phx1 node, which has insufficient disk space.
  2. Migrate www-dev.allizom.org and www.allizom.org over to bedrockadm and the associated dev/stage servers.
  3. Set up a dev/stage database... will use the dev.db cluster that's already live in PHX1.
  4. Set up prod web cluster in PHX1... will need to order hardware.
  5. Migrate www.mozilla.org (prod site) to bedrock prod cluster, controlled by bedrockadm.
  6. Set up prod DB cluster in PHX1.
  7. Set up prod DB cluster in SCL3, master-master replication with PHX1.

Other things:

  • Convert to github repo??? Bound to happen eventually, but no info on this yet.