judo 0.4.1 → 0.4.2
Sign up to get free protection for your applications and to get access to all the features.
- data/TODO +5 -33
- data/VERSION +1 -1
- data/lib/judo/base.rb +1 -1
- data/lib/judo/commandline_helpers.rb +1 -1
- metadata +3 -3
data/TODO
CHANGED
@@ -1,43 +1,15 @@
|
|
1
1
|
### NEEDED for new gem launch
|
2
2
|
|
3
|
-
### [ ] snapshot percent complete in do_snapshots()
|
4
|
-
### [ ] judo swap (x) (y) -> swaps elastic IP's and name
|
5
|
-
### [ ] snapshots/init/virgin
|
6
|
-
### [ ] bind kuzushi gem version version
|
7
|
-
### [ ] should be able to do ALL actions except commit without the repo!
|
8
|
-
### [ ] ssh - put pem into s3
|
9
|
-
### [ ] store s3 bucket in config
|
10
|
-
### [ ] saw a timeout on volume allocation - make sure we build in re-tries - need to allocate the server all together as much as possible
|
11
3
|
### [ ] round robin or specified availability_zone
|
12
|
-
### [ ]
|
13
|
-
### [ ]
|
4
|
+
### [ ] implement auto security_group creation and setup
|
5
|
+
### [ ] start and stop services in parallel
|
6
|
+
### [ ] retry volume creation timeout (happened once)
|
14
7
|
|
15
8
|
### MAYBE
|
16
|
-
### [ ] store things in s3 by sha1sum
|
17
9
|
### [ ] ebs backed root disk + start/stop
|
18
|
-
### [ ]
|
19
|
-
### [ ]
|
20
|
-
|
21
|
-
### [ ] two phase delete (1 hr)
|
22
|
-
### [-] refactor availability_zone (2 hrs)
|
23
|
-
### [ ] pick availability zone from config "X":"Y" or "X":["Y","Z"]
|
24
|
-
### [ ] assign to state on creation ( could delay till volume creation )
|
25
|
-
|
10
|
+
### [ ] two phase delete
|
11
|
+
### [ ] write specs
|
26
12
|
### [ ] store git commit hash with commit to block a judo commit if there is newer material stored
|
27
|
-
|
28
|
-
### [ ] use a logger service (1 hr)
|
29
|
-
### [ ] write specs (5 hr)
|
30
|
-
|
31
|
-
### Error Handling
|
32
|
-
### [ ] no availability zone before making disks
|
33
|
-
### [ ] security group does not exists
|
34
|
-
|
35
|
-
### Do Later
|
36
13
|
### [ ] use amazon's new conditional write tools so we never have problems from concurrent updates
|
37
|
-
### [ ] 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
|
38
|
-
### [ ] ruby 1.9.1 support
|
39
|
-
### [ ] find a good way to set the hostname or prompt to :name
|
40
|
-
### [ ] enforce template files end in .erb to make room for other possible templates as defined by the extensions
|
41
14
|
### [ ] zerigo integration for automatic DNS setup
|
42
|
-
### [ ] 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?"
|
43
15
|
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.4.
|
1
|
+
0.4.2
|
data/lib/judo/base.rb
CHANGED
metadata
CHANGED
@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
|
|
5
5
|
segments:
|
6
6
|
- 0
|
7
7
|
- 4
|
8
|
-
-
|
9
|
-
version: 0.4.
|
8
|
+
- 2
|
9
|
+
version: 0.4.2
|
10
10
|
platform: ruby
|
11
11
|
authors:
|
12
12
|
- Orion Henry
|
@@ -14,7 +14,7 @@ autorequire:
|
|
14
14
|
bindir: bin
|
15
15
|
cert_chain: []
|
16
16
|
|
17
|
-
date: 2010-
|
17
|
+
date: 2010-06-01 00:00:00 -04:00
|
18
18
|
default_executable: judo
|
19
19
|
dependencies:
|
20
20
|
- !ruby/object:Gem::Dependency
|