judo 0.4.1 → 0.4.2

data/TODO

@@ -1,43 +1,15 @@
 ### NEEDED for new gem launch
 
-### [ ] snapshot percent complete in do_snapshots()
-### [ ] judo swap (x) (y) -> swaps elastic IP's and name
-### [ ] snapshots/init/virgin
-### [ ] bind kuzushi gem version version
-### [ ] should be able to do ALL actions except commit without the repo!
-###     [ ] ssh - put pem into s3
-###     [ ] store s3 bucket in config
-### [ ] saw a timeout on volume allocation - make sure we build in re-tries - need to allocate the server all together as much as possible
 ### [ ] round robin or specified availability_zone
-### [ ] clean up the --group stuff in the code - get it out of judo
-### [ ] want 'judo destroy :ronin ^server1' 
+### [ ] implement auto security_group creation and setup
+### [ ] start and stop services in parallel
+### [ ] retry volume creation timeout (happened once)
 
 ### MAYBE
-### [ ] store things in s3 by sha1sum
 ### [ ] ebs backed root disk + start/stop
-### [ ] implement auto security_group creation and setup (6 hrs)
-### [ ] fix ruby 1.8.6 - test 1.9.1
-
-### [ ] two phase delete (1 hr)
-### [-] refactor availability_zone (2 hrs)
-###     [ ] pick availability zone from config "X":"Y" or  "X":["Y","Z"]
-###     [ ] assign to state on creation ( could delay till volume creation )
-
+### [ ] two phase delete
+### [ ] write specs
 ### [ ] store git commit hash with commit to block a judo commit if there is newer material stored
-
-### [ ] use a logger service (1 hr)
-### [ ] write specs (5 hr)
-
-### Error Handling
-### [ ] no availability zone before making disks
-### [ ] security group does not exists
-
-### Do Later
 ### [ ] use amazon's new conditional write tools so we never have problems from concurrent updates
-### [ ] I want a "judo monitor" command that will make start servers if they go down, and poke a listed port to make sure a service is listening, would be cool if it also detects wrong ami, wrong secuirity group, missing/extra volumes, missing/extra elastic_ip - might not want to force a reboot quite yet in these cases
-### [ ] ruby 1.9.1 support
-### [ ] find a good way to set the hostname or prompt to :name
-### [ ] enforce template files end in .erb to make room for other possible templates as defined by the extensions
 ### [ ] zerigo integration for automatic DNS setup
-### [ ] How cool would it be if this was all reimplemented in eventmachine and could start lots of boxes in parallel?  Would need to evented AWS api calls... Never seen a library to do that - would have to write our own... "Fog Machine?"
 

data/VERSION

@@ -1 +1 @@
-0.4.1
+0.4.2

data/lib/judo/base.rb

@@ -195,7 +195,7 @@ module Judo
 
     def get_group(name)
       group = groups.detect { |g| g.name == name }
-      group ||= Judo::Group.new(self, name, 0)
+      group ||= Judo::Group.new(self, name)
       group
     end
 

data/lib/judo/commandline_helpers.rb

@@ -33,7 +33,7 @@ module JudoCommandLineHelpers
   def mk_groups(judo, args, &blk)
     args.each do |name|
       if name =~ /:(.+)$/
-        blk.call(Judo::Group.new(judo, $1))
+        blk.call(judo.get_group($1))
       else
         raise JudoError, "Invalid group name '#{name}'"
       end

metadata

@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
   segments: 
   - 0
   - 4
-  - 1
-  version: 0.4.1
+  - 2
+  version: 0.4.2
 platform: ruby
 authors: 
 - Orion Henry
@@ -14,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-05-31 00:00:00 -04:00
+date: 2010-06-01 00:00:00 -04:00
 default_executable: judo
 dependencies: 
 - !ruby/object:Gem::Dependency