Open Stack

2014-02-25 16:25 GMT+01:00 Dina Belova <dbelova at mirantis.com>:

> Why should it require to be part of Keystone to hook up on Climate ?
>
>
> Sorry, can't get your point.
>
>

I'm just asking why we should hack Keystone workflow by adding an hook,
like we did for Nova. From my POV, that's not worth it.



> Provided we consider some projects as 'reservable', we could say this
>> should be a Climate API endpoint like CRUD /project/ and up to the admin
>> responsability to populate it.
>> If we say that new projects should automatically be 'reservable', that's
>> only policy from Climate to whiteboard these.
>
>
> So you propose to make some API requests to Climate (like for hosts) and
> mark some already existing projects as reserved. But how we'll automate
> process of some resource reservation belonging to that tenant? Or do you
> propose still to add some checkings to, for example, climate-nova
> extensions to check this somehow there?
>
> Thanks
>
>

I think it should be a Climate "policy" (be careful, the name is confusing)
: if admin wants to grant any new project for reservations, he should place
a call to Climate. That's up to Climate-Nova (ie. Nova extension) to query
Climate in order to see if project has been granted or not.

Conceptually, this 'reservation' information is tied to Climate and should
not be present within the projects.

-Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140225/cdcc5c1f/attachment.html>