- From: snacktime <snacktime@gmail.com>
- To: chef@lists.opscode.com
- Subject: Evalutating Chef for ec2 management
- Date: Sat, 28 Mar 2009 14:10:40 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=x3J9KoxqSSJC+0834PpiY2jRW2KbqeUl4zZDcuKKYWxBFmway1H2SuIfdfzNUv9VJ8 NTWcjng4VPAYl8LZHgI011hM9VhUf1Iq0jV7Qozr9yM8CvoNJIWETkl+/9ISe/tcW6vU DGzzsmae+UBYhIxjDskukjJnSy5QcKmZt1N9Y=
I'm brand new to chef and looking at it as a possible solution for configuring ec2 instances. The project I am working on is a job scheduler that uses ec2 nodes. It's designed to start up and configure ec2 nodes, then hand out jobs to the running instances, monitor them, start/stop new servers based on various conditions, etc.. Similar to the Condor scheduler but all in ruby/rails.
One of the main goals is to be able to use any ami, which means the system has to be able to configure a new instance from the ground up when it boots. So far I've been designing around using Capistrano + custom tasks. Creating a bunch of rake tasks works fine, but something like Chef could help standardize things more. Would Chef solo be a good fit here? Could I push out recipes to a new instance with capistrano and run them without having to use a Chef server?
Chris
- Evalutating Chef for ec2 management, snacktime, 03/28/2009
Archive powered by MHonArc 2.6.16.