On 06/08/2016 03:31 PM, Matt Riedemann wrote: > On 6/6/2016 7:26 AM, Jay Pipes wrote: >> Once the InventoryList and AllocationList objects are merged, then we >> will focus on reviews of the placement REST API patches [3]. Again, we >> are planning on having the nova-compute resource tracker call these REST >> API calls directly (while continuing to use the Nova ComputeNode object >> for saving legacy inventory information). Clearly, before the resource >> tracker can call this placement REST API, we need the placement REST API >> service to be created and a client for it added to OSC. Once this client >> exists, we can add code to the resource tracker which uses it. > > Wait, we're going to require python-openstackclient in Nova to call the > placement REST API? That seems bad given the dependencies that OSC pulls > in. Why not just create the REST API wrapper that we need within Nova > and then split that out later to whichever client it's going to live in?
Yes, that ^^^ Just use keystoneauth1 and hand rolled json. We shouldn't be talking about a ton of code. Pulling python-openstackclient back into Nova as a dependency is really a hard NACK for a bunch of reasons, including the way dependencies work. -Sean -- Sean Dague http://dague.net __________________________________________________________________________ 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