search

midasplatform / infrastructure

Tools for deploying Midas Server instances
Apache License 2.0
3 stars 0 forks source link

provision an AWS midas #12

Open mgrauer opened 11 years ago

mgrauer commented 11 years ago

use boto, puppet

create an instance where the webroot is midas, https only

mgrauer commented 11 years ago

use ebs for the assetstore, not the filesystem of the machine itself.

may want to store the machine image in s3 after it is set up.

mgrauer commented 11 years ago

I created an ebs based ubuntu 12.04 amd64 machine today and provisioned it using puppet, although not with https.

This will need to wait until I start on #16, breaking out a separate midas puppet module, which will give me https support.

Then I'll bring in an https profile for midas, along with setting up an ebs block for the assetstore. Finally I'll want to save a bootstrapped machine image if possible, one that only needs to have puppet provisioning run on it.

mgrauer commented 11 years ago

All of these should consider: OS, mounted from an AMI (either a public, or a custom public), stored on EBS? Midas, stored on EBS?, current state is in terms of git commit, configuration files, and DB DB, stored on EBS?, on a separate server or the same server, are transactions necessary? assetstore, stored on EBS?

Other areas to consider, most likely should be broken out into separate issues:

how to deal with backups how to restore an instance (apparently an EC2 instance can die at any time) how to deal with updates how to monitor instances *investigate the possibility of failover, or what guarantees we can make about uptime