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.sanc...@intel.com> 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.ba...@gmail.com <javascript:;><mailto: > sylvain.ba...@gmail.com <javascript:;>>> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org <javascript:;><mailto: > openstack-dev@lists.openstack.org <javascript:;>>> > Date: martes, 25 de febrero de 2014 17:55 > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org <javascript:;><mailto: > openstack-dev@lists.openstack.org <javascript:;>>> > Subject: Re: [openstack-dev] [Climate] Lease by tenants feature design > > > > > 2014-02-25 17:42 GMT+01:00 Dina Belova <dbel...@mirantis.com<javascript:;> > <mailto:dbel...@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@lists.openstack.org <javascript:;> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Best regards, Dina Belova Software Engineer Mirantis Inc.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
