Last week I made an update[0] on the state of things in the resource provider/placement API universe. That seemed pretty useful, so here's another one. Even though most people were productively involved in reviewing specs before yesterday's deadline, some placement related specs and code merged, and there was good review progress on pending changes.
Below I give a summary of how things changed since last week and what still remains. I've left out some of the descriptive text in some sections where it would have been duplciated from last week. See last week[0] for more info. [0] http://lists.openstack.org/pipermail/openstack-dev/2016-November/107171.html # Stuff What Merged \o/ * Improved 404 responses (1 of 2): https://review.openstack.org/#/c/387674/ * Proper handling of max_unit in resource tracker and placement API (2 of 2): https://review.openstack.org/#/c/395971/ * First bit of aggregates (1 of 3): https://review.openstack.org/#/c/362863/ * Cleaning up the newton resource providers spec to reflect reality: https://review.openstack.org/#/c/366888/ * Spec of the HTTP API on narrowing list of resource providers https://review.openstack.org/#/c/385618/ * Initial docs for placement service: https://review.openstack.org/#/c/396761/ # Leftovers from Newton Things that need reaction to reviews: * Improved 404 responses (1 merged, 1 pending): https://review.openstack.org/#/c/392321/ Things that are ready to review: * Increased gabbi test coverage (stack of 3): https://review.openstack.org/#/c/396363/ * Aggregates support in placement api (stack of 2): https://review.openstack.org/#/c/355263/ Review of this stack identified a race condition which has been fixed but now we're not sure how/if to test it. * Demo inventory update script: https://review.openstack.org/#/c/382613/ This one might be considered a WIP because how it chooses to do things (rather simply and dumbly) may not be in line with expecations. * CORS support in placement API: https://review.openstack.org/#/c/392891/ There are still quite a few things to pick up on the leftovers etherpad[1]. It may be time to filter the etherpad for relevance. [1] https://etherpad.openstack.org/p/placement-newton-leftovers # Filtering compute nodes with the placement API One spec related to this (see above) has merged, with caveats that the details of the API are subject to change during implementation. * Spec for modifying the scheduler to query the api: https://review.openstack.org/#/c/300178/ * Code that satisfies those two specs (stack of 2): https://review.openstack.org/#/c/386242/ # Custom Resource Classes The code for this proceeds apace. Since placement is a priority, the specs related to this and nested resource providers are still in play. * The spec https://review.openstack.org/#/c/312696/ * Code to make them work in the api (stack of 5): https://review.openstack.org/#/c/386844/ # Nested Resource Providers * The spec https://review.openstack.org/#/c/386710/ * Code to implement the object and HTTP API changes (stack of 4): https://review.openstack.org/#/c/377138/ # Allocations for generic PCI devices * Code (stack of 3): https://review.openstack.org/#/c/396963/ # Important stuff not in other categories This section is for lose ends that don't fit in elsewhere. Stuff we're going to need to figure out at some point. ## Placement DB No new discussion or progress on this. The etherpad[2] and related code changes[3] remain the same. The todo here is to resolve the questions on the etherpad and make an explicit plan. [2] https://etherpad.openstack.org/p/placement-optional-db-spec [3] https://review.openstack.org/#/c/362766/ (this is -2d pending resolution of the stuff on the etherpad) ## Placement Docs Matt R made a great start[4] to this setting the foundation for the rest of us to build on. The major portion left as a TODO is docs of the API. Because, for the time being, the API is relatively simple, it has been decided that creating the docs by hand is okay. So the todo here is: get started on the api-ref docs. [4] https://review.openstack.org/#/c/396761/ which resulted in http://docs.openstack.org/developer/nova/placement.html ## Placement Upgrade/Installation issues In his response[5] to this message Matt R pointed out todos for this topic: * get the placement-api enabled by default in the various bits ofocata CI * ensure that microversions are being used on both sides of the
placement API transactions (that's true in pending changes to both the API and the resource tracker) [5] http://lists.openstack.org/pipermail/openstack-dev/2016-November/107177.html # End Thanks for reading. If you think this is useful or could be more useful please let me know. -- Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/ freenode: cdent tw: @anticdent
__________________________________________________________________________ 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
