We just merged an initial pass at direct access to the placement service . See the test_direct suite for simple usage examples.
Note that this was written primarily to satisfy the FFU use case in blueprint reshape-provider-tree  and therefore likely won't have everything cinder needs. So play around with it, but please do not put it anywhere near production until we've had some more collab. Find us in #openstack-placement. -efried  https://review.openstack.org/572576  https://review.openstack.org/572583 On 06/04/2018 07:57 AM, Jay S Bryant wrote: > > > On 6/1/2018 7:28 PM, Chris Dent wrote: >> On Wed, 9 May 2018, Chris Dent wrote: >> >>> I've started an etherpad for the forum session in Vancouver devoted >>> to discussing the possibility of tracking and allocation resources >>> in Cinder using the Placement service. This is not a done deal. >>> Instead the session is to discuss if it could work and how to make >>> it happen if it seems like a good idea. >>> >>> The etherpad is at >>> >>> https://etherpad.openstack.org/p/YVR-cinder-placement >> >> The session went well. Some of the members of the cinder team who >> might have had more questions had not been able to be at summit so >> we were unable to get their input. >> >> We clarified some of the things that cinder wants to be able to >> accomplish (run multiple schedulers in active-active and avoid race >> conditions) and the fact that this is what placement is built for. >> We also made it clear that placement itself can be highly available >> (and scalable) because of its nature as a dead-simple web app over a >> database. >> >> The next steps are for the cinder team to talk amongst themselves >> and socialize the capabilities of placement (with the help of >> placement people) and see if it will be suitable. It is unlikely >> there will be much visible progress in this area before Stein. > Chris, > > Thanks for this update. I have it on the agenda for the Cinder team to > discuss this further. We ran out of time in last week's meeting but > will hopefully get some time to discuss it this week. We will keep you > updated as to how things progress on our end and pull in the placement > guys as necessary. > > Jay >> >> See the etherpad for a bit more detail. >> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev