Closed Bug 983184 Opened 11 years ago Closed 11 years ago

Deploy Loop server on AWS

Categories

(Hello (Loop) :: Server, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: alexis+bugs, Unassigned)

References

Details

(Whiteboard: [qa!])

So it seems we're almost ready to deploy something for the MLP; I would love to hear some feedback from ops about what we should provide for you to have it working well. Please, enlighten me :)
Blocks: loop_mlp
For max compatibility: - we deploy on Scientific Linux 6.3 - we have our own nodejs RPMs - when we deploy we burn all things into RPMs and deploy as RPMs If you deploy in us-west-2 use this AMI: ami-6afe9e5a If you deploy in us-east-1 use this AMI: ami-059ea16c Do a `yum install nodejs-svcops` and you should be able to use `npm install` on your repo. It is ok to do a git clone/npm install for now. We use circus to supervise nodejs and usually nginx in front as a reverse proxy.
yeah! http://ec2-54-203-132-224.us-west-2.compute.amazonaws.com/ Still need to define a way to auto update it there (when something lands on master), but at least we've got something working :) Also needs some circus config files in the repo :)
I've setup a CNAME on http://loop.dev.mozaws.net/ that should show up pretty soon.
We've got some problems when installing MongoDB. For further reference, here is the logs we had: /usr/bin/mongod: symbol lookup error: /usr/bin/mongod: undefined symbol: _ZN7pcrecpp2RE4InitEPKcPKNS_10RE_OptionsE Solution was to compile it ourselves with the normal options. Default package may not be working well with AWS libraries. It's running smoothly right now, closing this bug, it's deployed!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
I assume this bug is strictly for all current/future Prod deployments. I attached the Stage ticket as a dependency for now... I can Verify this bug once I verify Prod.
Depends on: 1006698
This was specifically for the first dev version of loop. Prod / Stage is a different bug.
ah ok then.
Status: RESOLVED → VERIFIED
QA Contact: jbonacci
Whiteboard: [qa!]
You need to log in before you can comment on or make changes to this bug.