On 06/08/11 - 04:11:14PM, Mark McLoughlin wrote:
Hey,
I started looking at this:
https://www.aeolusproject.org/redmine/issues/1200
"Use deltacloud api for provider names"
but decided to think through things from a higher level again.
I've a fairly jumbled set of notes below, but I'd summarize my
conclusions as:
1) We should move to using a single instance of deltacloud
Absolutely.
2) We should drop current provider management UI in Conductor
3) The provider account UI should allow you to supply details of a
RHEV-M or VMWare instance that is not currently known to Conductor
or deltacloud. Or, indeed, choose from any of the known instances.
I'd just squash 2 and 3 together (otherwise it is a bit confusing). That is,
we should definitely let the user specify paths to drivers/providers that
are not pre-configured. We need to modify the provider UI to do this.
4) You shouldn't have to re-enter your EC2 credentials for each region
I guess that matches up with what EC2 does. Once we do 1), this might become
easier.
5) Image factory should use the provider/driver details from the
deltacloud API, once some more details are exposed
6) aeolus-image should be able to supply the RHEV-M or VMWare
instance URL to image_factory when doing a push; it gets this URL
from Conductor
7) Similarly, it looks like image_factory requires some other details
for each RHEV-M and VMWare instance. This would need to be in the
'Add Provider Account' dialog and passed by aeolus-image to
image_factory
Meh, that's quite a random set of work items. Anyone have any better
ideas?
No, these are the sorts of things I've been thinking about for a while. Just
haven't had time to do anything about them :).
--
Chris Lalancette