Set up staging, dev and live VMs for ignite

RESOLVED FIXED

Status

--
major
RESOLVED FIXED
7 years ago
2 years ago

People

(Reporter: sschipper, Unassigned)

Tracking

Details

(Reporter)

Description

7 years ago
+++ This bug was initially created as a clone of Bug #678204 +++

We'd like to set up two VMs for the development and staging environments for he "Ignite" project here.  This project will have the same infrastructure needs as the betafarm project.  Should be able to clone the VM's from that project (Bug #678204).

1) Dev - Code from the dev branch will be hosted here.  We would like ignite-dev.mozillalabs.com to point here.

2) Staging - Code from the staging will be hosted here. We'd like ignite-stage.mozillalabs.com (or similar) to point here. 

Thanks!
Blocks: 694010
Apologies - have added in an extra VM for live.

The idea is that we have:
 
- one dev VM - used for weekly iterations and as a way to gather community feedback,
- one staging VM - used for developer controlled iterations to allow stake-holder review/feedback
- one live VM (URL to be decided)
Summary: Set up staging and dev VMs for ignite → Set up staging, dev and live VMs for ignite
ignite1.vm1.labs.sjc1.mozilla.com          IN  A    10.110.4.73
ignite-stage1.vm1.labs.sjc1.mozilla.com    IN  A    10.110.4.74
ignite-dev1.vm1.labs.sjc1.mozilla.com      IN  A    10.110.4.75

MPT-VPN, and ross has sudo. Please open a new bug when you want them exposed to the world.

These are 'blank' VMs, not clones of the existing betafarm nodes, because I remember paul saying that the betafarm nodes would want to cluster.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.