679002 - new VM for BrowserID

Status: RESOLVED INVALID

(Infrastructure & Operations Graveyard :: WebOps: Labs, task)

Description

[Lloyd Hilaiel]

currently the browserid production service is served from a single machine: browserid.vm1.labs.sjc1.mozilla.com.  We would like a new VM on a different physical machine in that same colo so that we can have a degree of redundancy.

Comment 1

[Zandr Milewski [:zandr]]

There have been some hallway conversations about this, but we should capture them here.

If the goal here is redundancy, then we need to move to a different platform, since the labs/foundation cluster only exists in one place (it's multiple nodes in a single chassis).

If the goal is just getting test time on a distributed system, that's easy, but we need to talk about the back-end. (shared storage, shared db?)

Comment 2

[Lloyd Hilaiel]

My goal here was to put production on more than one node just to do it, because the process of doing it will require that we flesh out any issues that need to be addressed once its distributed.  Even if those nodes don't buy us meaningful redundancy, the exercise is still useful because it gives us an environment where we can deploy browserid in a distributed fashion so we've got confidence and can efficiently provision new nodes as they come online.  

as far as the back end, each node will be mysql + node.js + nginx.  The specific mysql configuration is still something I'm working on and will expound in a different forum (probably dev-identity, hopefully today).