Skip to content
This repository has been archived by the owner on Mar 8, 2018. It is now read-only.

Should refactor Blimpy::Box to support different "cloud" providers #17

Closed
rtyler opened this issue Apr 29, 2012 · 4 comments
Closed

Should refactor Blimpy::Box to support different "cloud" providers #17

rtyler opened this issue Apr 29, 2012 · 4 comments
Assignees

Comments

@rtyler
Copy link
Owner

rtyler commented Apr 29, 2012

I can see it making sense to have something like this in your Blimpfile:

Blimpy.fleet do |f|
  f.add do |s|
    s.cloud :aws
    s.name 'amazon'
  end
  f.add do |s|
    s.cloud :openstack
    s.name 'private'
  end
end
@ghost ghost assigned rtyler Apr 29, 2012
@rtyler
Copy link
Owner Author

rtyler commented May 18, 2012

Starting work on this now.

(This message brought to you by Hub board)

@rtyler
Copy link
Owner Author

rtyler commented May 18, 2012

There's a lot of things that need to go into this; major refactor of the Box interactions :(

@rtyler
Copy link
Owner Author

rtyler commented May 19, 2012

I think this can be mostly considered done as of 0.3.0.

Currently there aren't any other cloud boxes fully defined though.

@rtyler
Copy link
Owner Author

rtyler commented May 19, 2012

This work is complete.

(This message brought to you by Hub board)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant