Aeolus API and DMTF CIMI

Michal Fojtik mfojtik at redhat.com
Wed Nov 21 13:22:48 UTC 2012


On 11/21/2012 01:39 PM, marios at redhat.com wrote:

>> Call me crazy, but this what I was thinking about:
>>
>> * Deltacloud CIMI to provide low-level API (Machine, MachineConfig, etc)
>> * Aeolus API to provide high-level (n-tier, System, SystemTemplate)
>> * Heat API to provider monitoring, event CIMI stuff.
>
> I like the sound of that! There is a natural alignment there with the
> current status quo - Deltacloud for stateless management of resources,
> stateful Conductor one level up allowing organisation of those resources
> into aggregations.
>
> This would solve the (current Deltacloud) problem "we can't support
> systems if the back-end cloud doesn't" - Conductor can create 'pseudo
> systems'.
>
> One issue is it will be messy to have this "CIMI stack" spread across
> components; I mean would you need to use 3 different APIs and talk to 3
> different services? Is it possible to have a single unifying 'Aeolus
> API' giving access to all?

As DC is Rack mountable, it will be easy to just mount it into Conductor :-)

Other components, like Heat can be proxyfied using nginx/httpd :)

   -- michal

>
> marios
>
>
>
>> Having all these three components working together will result in full CIMI
>> stack :-)
>>
>>    -- Michal


-- 

Michal Fojtik <mfojtik at redhat.com>
Deltacloud API, CloudForms



More information about the aeolus-devel mailing list