[SERVER-742] remove java ec2 management with libcloud Created: 12/Mar/10 Updated: 12/Jul/16 Resolved: 26/Apr/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Richard Kreuter (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
http://incubator.apache.org/libcloud/ |
| Comments |
| Comment by Richard Kreuter (Inactive) [ 26/Apr/10 ] |
|
Closed in commit a41766b (with incorrect commit message including " |
| Comment by Richard Kreuter (Inactive) [ 26/Apr/10 ] |
|
I think this is done now. mdirolf and I have both gotten used to working with libcloud for ec2, so that aspect of the case is also good. |
| Comment by Richard Kreuter (Inactive) [ 26/Apr/10 ] |
|
I've transitioned the only thing I could find that used the java tools over to libcloud. Cleaning out gunk now. |
| Comment by Richard Kreuter (Inactive) [ 22/Mar/10 ] |
|
libcloud developers added the multi-sec-group feature over the weekend. |
| Comment by Richard Kreuter (Inactive) [ 18/Mar/10 ] |
|
Note to self: as of 18 March, libcloud doesn't support specifying multiple security groups for an EC2 instance. This is an issue for our way of using security groups. SHouldn't be too hard to fix, though. |