4 ms·

Speaking of deployment, anyone has a good suggestion for a simple deploying system in AWS? Ideally a generic EC2 instance is booted up with an apptype passed i

by ww520 15y ago

Speaking of deployment, anyone has a good suggestion for a simple deploying system in AWS? Ideally a generic EC2 instance is booted up with an apptype passed in, and based on the apptype it downloads the app code from S3 and starts up the app. The code is pushed to S3 by dev when it's ready. Is there such a system?

jat850 15y ago
Are you think of something like chef? http://www.opscode.com/chef/ http://www.opscode.com/chef/ It maybe doesn't fit the bill of simple, but it's not too dreadfully hard to get set up if you only want it to fulfill some relatively straightforward tasks like you describe.
- ww520 15y ago
  Thanks. I'll take a look at it again. The last time I looked at it (along with Puppet and others), it seemed to be rather complicated with setting up Chef Server, CouchDB, RabbitMQ, and Solr. Ideally Chef just runs at the boot time of a EC2 instance, reads the recipes off from S3 and continues from there.
  - joevandyk 15y ago
    You want chef-solo. No need for chef server.
  - pedoh 15y ago
    Chef and Puppet can definitely do this for you, without servers involved. Another great use of Chef and Puppet can be seen in Vagrant (http://vagrantup.com/ http://vagrantup.com/). Vagrant uses VirtualBox (http://www.virtualbox.org/ http://www.virtualbox.org/) to create virtual instances easily (REALLY easily) and then can automatically provision them via Chef or Puppet. Sweet stuff. I love the ability to bring up a new server with the things I want to have so quickly.
  - davnola 15y ago
    opscode now have a hosted chef server platform https://manage.opscode.com/ https://manage.opscode.com/
- snprbob86 15y ago
  I did a whole bunch of research into DevOps and Chef (or Puppet) were the clear winners. That's really kinda sad because Heroku's model is just sooo much more pleasant as a developer... at least to start. I'd really love to see a better abstraction than "idempotent wrappers for shell commands" which is what Chef and Puppet basically are. Most applications are simple enough to run as a single process with a read-only file system and log to standard out. Surely someone could use the Heroku Procfile model a reasonable starting point and create escape hatches down to lower levels as you need them.
pedoh 15y ago
We're using Puppet for our deployments, and not just initial deployments, but for code deployments as well. The puppet node classifier talks to a MySQL database that has the "right" versions for a particular server in it; upgrading consists of changing the version for a server to the desired version, and then running Puppet. I think you could create an EC2 instance that automatically runs Puppet (or Chef) on startup pretty easily. And as someone else mentioned here, you don't have to do a complicated setup with a server to get going, either with Chef or Puppet.
cwp 15y ago
I use a system based on Fabric. It fires up an instance, connects via SSH, installs and configures everything needed for the app, saves an AMI, then terminates the instance. Then deployment is just a matter of launching an instance with that AMI.
- mattdeboard 15y ago
  I built out one of these at work, and while it is indeed pretty neat, it still has a lot of pain points and complexity -- at least in our case -- that could be ameliorated by and is better suited for Puppet/Chef.

by ww520 15y ago

jat850 15y ago

Are you think of something like chef? http://www.opscode.com/chef/ http://www.opscode.com/chef/ It maybe doesn't fit the bill of simple, but it's not too dreadfully hard to get set up if you only want it to fulfill some relatively straightforward tasks like you describe.

ww520 15y ago
Thanks. I'll take a look at it again. The last time I looked at it (along with Puppet and others), it seemed to be rather complicated with setting up Chef Server, CouchDB, RabbitMQ, and Solr. Ideally Chef just runs at the boot time of a EC2 instance, reads the recipes off from S3 and continues from there.
- joevandyk 15y ago
  You want chef-solo. No need for chef server.
- pedoh 15y ago
  Chef and Puppet can definitely do this for you, without servers involved. Another great use of Chef and Puppet can be seen in Vagrant (http://vagrantup.com/ http://vagrantup.com/). Vagrant uses VirtualBox (http://www.virtualbox.org/ http://www.virtualbox.org/) to create virtual instances easily (REALLY easily) and then can automatically provision them via Chef or Puppet. Sweet stuff. I love the ability to bring up a new server with the things I want to have so quickly.
- davnola 15y ago
  opscode now have a hosted chef server platform https://manage.opscode.com/ https://manage.opscode.com/
snprbob86 15y ago
I did a whole bunch of research into DevOps and Chef (or Puppet) were the clear winners. That's really kinda sad because Heroku's model is just sooo much more pleasant as a developer... at least to start. I'd really love to see a better abstraction than "idempotent wrappers for shell commands" which is what Chef and Puppet basically are. Most applications are simple enough to run as a single process with a read-only file system and log to standard out. Surely someone could use the Heroku Procfile model a reasonable starting point and create escape hatches down to lower levels as you need them.

pedoh 15y ago

We're using Puppet for our deployments, and not just initial deployments, but for code deployments as well. The puppet node classifier talks to a MySQL database that has the "right" versions for a particular server in it; upgrading consists of changing the version for a server to the desired version, and then running Puppet. I think you could create an EC2 instance that automatically runs Puppet (or Chef) on startup pretty easily. And as someone else mentioned here, you don't have to do a complicated setup with a server to get going, either with Chef or Puppet.

cwp 15y ago

I use a system based on Fabric. It fires up an instance, connects via SSH, installs and configures everything needed for the app, saves an AMI, then terminates the instance. Then deployment is just a matter of launching an instance with that AMI.

mattdeboard 15y ago
I built out one of these at work, and while it is indeed pretty neat, it still has a lot of pain points and complexity -- at least in our case -- that could be ameliorated by and is better suited for Puppet/Chef.