On 07/14/11 - 11:12:50AM, Carl Trieloff wrote:
>>> DC API ontop of Conductor, is the big missing item.
Don't care about
>>> admin API for v1, but DC API needs to be there.
>>>
>>> Carl.
>> Ahh... well, we were talking about what features we would promote for
>> the release we're about to do *right now*, not one that is some time
>> in the future, and since the DC API isn't started yet we can't very
>> well promote it for this release.
>>
>> Having said that, would you mind describing for everyone what exposing
>> a DC API in front of Conductor would buy us?
> I've been wondering about this as well. The DC API doesn't seem to map
very
> well onto the conductor; the concepts are not even the same. It feels like
> jamming a square peg into a round hole. What benefit would we gain from doing
> this, and do customers actually care about it?
>
All clouds that are worth anything have a public API, ours is
deltacloud. If I stand up aeolus for my private cloud, I want to be able
to use it via the API in the same way I can do with EC2, rackspace,
openstack etc.
Don't get me wrong, I'm not arguing against a public API. I definitely
believe we should have one of those. I'm just not sure that it should be the
deltacloud API, as the concepts don't easily map over to the conductor.
--
Chris Lalancette