Conductor API versioning

Tomas Sedovic tsedovic at redhat.com
Wed Apr 11 15:54:51 UTC 2012


On 04/11/2012 03:37 PM, Matt Wagner wrote:
> On Tue, Apr 10, 2012 at 02:41:18PM +0200, Maros Zatko wrote:
>> Good news everyone!
>>
>> we held a meeting, and besides other things we've been discussing API
>> and it's versions too.
>>
>> We haven't decided if we're going to support versioned API in the sense that
>> the client could make a choice what version of API is going to be
>> used in communication
>> with Conductor.
>
> Is there a discussion going on about the API in general? I don't have a
> strong opinion on versioning, but I do have a strong opinion on *having*
> an API, which we really don't right now. I didn't see a planning page /
> email for that, but I've been known to miss things right under my nose.

There is indeed an effort to create a complete and consistent API for 
Conductor. The goal is to have an API that lets you do anything the UI 
can do.

It seems to be split in to multiple wiki pages (page per feature):

https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Conductor_Image_Management_API
https://www.aeolusproject.org/redmine/projects/aeolus/wiki/V2_Conductor_API_Provider_Management_BDD
https://www.aeolusproject.org/redmine/projects/aeolus/wiki/V2_Conductor_API_Provider_Account_Management_BDD

>
> -- Matt




More information about the aeolus-devel mailing list