sumo 0.1.0 → 0.1.1

data/README.rdoc

@@ -17,7 +17,26 @@ Later...
     $ sumo terminate
     ec2-67-202-17-178.compute-1.amazonaws.com scheduled for termination
 
-You can also manage multiple instances via "sumo list" and specifying hostname or instance id as arguments to the launch, ssh, and terminate commands.
+You can manage multiple instances via "sumo list" and specifying hostname or instance id as arguments to the ssh or terminate commands.
+
+== Service installation with Chef
+
+The launch command takes an argument, which is a server role (from roles/#{role}.json inside your cookbooks repo):
+
+    $ sumo launch redis
+    ---> Launch instance...       i-b96c73d0 (1.3s)
+    ---> Acquire hostname...      ec2-75-101-191-220.compute-1.amazonaws.com (36.1s)
+    ---> Wait for ssh...          done (9.0s)
+    ---> Bootstrap chef...        done (61.3s)
+    ---> Setup redis...           done (11.9s)
+    ---> Opening firewall...      ports 6379 (5.2s)
+
+    Your instance is exporting the following resources:
+      Redis: redis://:8452cdd98f428c972f08@ec2-75-101-191-220.compute-1.amazonaws.com:6379/0
+
+The instance can assume multiple roles if you like:
+
+    $ sumo launch redis,solr,couchdb
 
 == Setup
 
@@ -31,6 +50,7 @@ Then create ~/.sumo/config.yml containing:
     access_id: <your amazon access key id>
     access_secret: <your amazon secret access key>
     ami: ami-ed46a784
+    cookbooks_url: git://github.com/adamwiggins/chef-cookbooks.git
 
 If you run any production machines from your EC2 account, I recommend setting up a separate account for use with Sumo.  It does not prompt for confirmation when terminating an instance or differentiate between instances started by it vs. instances started by other tools.
 
@@ -40,6 +60,8 @@ Launch, ssh to, and terminate instances.
 
 Sumo creates its own keypair named sumo, which is stored in ~/.ssh/keypair.pem.  Amazon doesn't let you upload your own ssh public key, which is lame, so this is the best option for making the launch-and-connect process a single step.
 
+It will also create an Amazon security group called sumo, so that it can lower the firewall for services you configure via cookbook roles.
+
 == Anti-features
 
 Sumo is not a cloud management tool, a monitor tool, or anything more than a way to get an instance up right quick.  If you're looking for a way to manage a cluster of production instances, try one of these fine tools.

data/VERSION

@@ -1 +1 @@
-0.1.0
+0.1.1

data/lib/sumo.rb

@@ -1,4 +1,4 @@
-require 'ec2'
+require 'AWS'
 require 'yaml'
 require 'socket'
 
@@ -172,7 +172,7 @@ class Sumo
 
 	def create_security_group
 		ec2.create_security_group(:group_name => 'sumo', :group_description => 'Sumo')
-	rescue EC2::InvalidGroupDuplicate
+	rescue AWS::EC2::InvalidGroupDuplicate
 	end
 
 	def open_firewall(port)
@@ -183,10 +183,10 @@ class Sumo
 			:to_port => port,
 			:cidr_ip => '0.0.0.0/0'
 		)
-	rescue EC2::InvalidPermissionDuplicate
+	rescue AWS::EC2::InvalidPermissionDuplicate
 	end
 
 	def ec2
-		@ec2 ||= EC2::Base.new(:access_key_id => config['access_id'], :secret_access_key => config['access_secret'])
+		@ec2 ||= AWS::EC2::Base.new(:access_key_id => config['access_id'], :secret_access_key => config['access_secret'])
 	end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: sumo
 version: !ruby/object:Gem::Version 
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors: 
 - Adam Wiggins
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-08-19 00:00:00 -07:00
+date: 2009-08-31 00:00:00 -07:00
 default_executable: sumo
 dependencies: []