Open Stack

Only problem here is that we'll remove admin climate user in the future and
will use only trusts, so how you'll get needed info?

I think we may keep info unduplicated only in one case: use trust from
admin user who marked tenant as reservable to get needed info later.

In this case storing needed info in keystone is ok for me.

Dina

On Thursday, February 27, 2014, Sanchez, Cristian A <
cristian.a.sanchez at intel.com> wrote:

> I don't think that duplicating the information in Climate is a really good
> idea. Why don't let Keystone manage the tenant dates information? Moreover,
> we can also add that to Horizon.
> Then, during Lease creations, Climate should query Keystone to get the
> tenant dates.
>
> What do you think?
>
> From: Dina Belova <dbelova at mirantis.com <javascript:;><mailto:
> dbelova at mirantis.com <javascript:;>>>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org <javascript:;><mailto:
> openstack-dev at lists.openstack.org <javascript:;>>>
> Date: miércoles, 26 de febrero de 2014 02:10
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org <javascript:;><mailto:
> openstack-dev at lists.openstack.org <javascript:;>>>
> Subject: Re: [openstack-dev] [Climate] Lease by tenants feature design
>
> Also we have to mention Adam's letter - cause now he said he loves to see
> start/end date functionality in keystone.
>
> If so, we may store this info in Keystone - but anyway, I suppose that it
> might be somehow duplicated in Climate not to process one more request to
> Keystone when it'll be needed. I still have no clear idea how that will be
> looking speaking about user rights.
>
> Now we're using trusts + special admin user. We'll get rid of this special
> user in future. But to work with projects we still need admin's rights.
>
> Any ideas?
>
> On Wednesday, February 26, 2014, Dina Belova <dbelova at mirantis.com<javascript:;>
> <mailto:dbelova at mirantis.com <javascript:;>>> wrote:
> Don't think it's needed in this case. We may store this info in Climate
> not to intersect with Keystone without serious reasons.
>
> On Wednesday, February 26, 2014, Sanchez, Cristian A <
> cristian.a.sanchez at intel.com <javascript:;><javascript:_e(%7B%7D,'cvml','
> cristian.a.sanchez at intel.com <javascript:;>');>> wrote:
> One question to clarify: the project will be marked as reservable by
> calling Keystone API (from Climate) to store that info in the project extra
> specs in Keystone DB.
> Is this correct?
>
> From: Sylvain Bauza <sylvain.bauza at gmail.com <javascript:;><mailto:
> sylvain.bauza at gmail.com <javascript:;>>>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org <javascript:;><mailto:
> openstack-dev at lists.openstack.org <javascript:;>>>
> Date: martes, 25 de febrero de 2014 17:55
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org <javascript:;><mailto:
> openstack-dev at lists.openstack.org <javascript:;>>>
> Subject: Re: [openstack-dev] [Climate] Lease by tenants feature design
>
>
>
>
> 2014-02-25 17:42 GMT+01:00 Dina Belova <dbelova at mirantis.com<javascript:;>
> <mailto:dbelova at mirantis.com <javascript:;>>>:
>
> >>> 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.
>
> Now I think that it'll be better, yes.
> I see some workflow like:
>
> 1) Mark project as reservable in Climate
> 2) When some resource is created (like Nova instance) it should be checked
> (in the API extensions, for example) via Climate if project is reservable.
> If is, and there is no special reservation flags passed, it should be used
> default_reservation stuff for this instance
>
> Sylvain, is that ira you're talking about?
>
>
> tl;dr : Yes, let's define/create a new endpoint for the need.
>
> That's exactly what I'm thinking, Climate should manage reservations on
> its own (including any new model) and projects using it for reserving
> resources should place a call to it in order to get some information.
>
> -Sylvain
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org <javascript:;>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
>
> Best regards,
>
> Dina Belova
>
> Software Engineer
>
> Mirantis Inc.
>
>
>
> --
>
> Best regards,
>
> Dina Belova
>
> Software Engineer
>
> Mirantis Inc.
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org <javascript:;>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 

Best regards,

Dina Belova

Software Engineer

Mirantis Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140227/cfd41867/attachment.html>