On Wed, 2011-07-27 at 10:36 -0400, Matt Wagner wrote:
Hi Mark,
I think we're envisioning slightly different things here, so I wanted to
try to understand if I was unclear, or if you're describing a better way
of doing things -- and if so, what the advantages are.
On Wed, Jul 27, 2011 at 10:30:35AM +0100, Mark McLoughlin wrote:
>
> 2) If we go with the design above where users launch instances from
> the images list, a big part of what this feature needs will be the
> images list and the ability to import images
Yes, I agree that the features are fairly closely related. Mostly, I
just wanted to break them apart into two smaller tasks -- give the
ability to launch images from Warehouse, and give (err, bring back) the
ability to import images using a tool in Conductor. They should both be
done, though image importation isn't required for standalone launch.
I would note that we already do this in aeolus-image _via factory), so
it may be simpler/better to just require the import command from that
lib and call it instead of writing up something new. If this means
aolus-image needs any tweak, fine, but I think it should mostly 'just
work' already. The same sentiment applies to what you said about
listing things from iwhd - that is something aeolus-image already does,
though we absolutely should share a common base model (Scott and I had
talked about active model for both). I would lean toward not making
this yet another gem though, I kind of think it can just go in
aeolus-image if conductor is using it already anyway.
As an aside, the aeolus-image library was designed to either be used
from cli (as we are at the moment) _or_ as an api for apps like
conductor. In the latter case, you would just set it up as a regular
gem dep and load the command object you are interested in using. You
are perfectly free to pass in your config via your own yml/config file
as well, provided it map to the expected options properly.
-j