settingsLogin | Registersettings

[openstack-dev] [nova] placement/resource providers update 34

0 votes

Update 34 has many links.

Most Important

Besides reviewing all the stuff in this document, another important
thing to do is to make additions and edits on the PTG etherpad

 https://etherpad.openstack.org/p/nova-ptg-queens

There's also now an etherpad for gathering retrospective thoughts. If
you have some ideas on things that went well or less than well in
placement related work it would be great if you could add your
thoughts there:

 https://etherpad.openstack.org/p/nova-pike-retrospective

Help Wanted

Reviewing things that are fixes for backportable problems is the main
thing.

Bugs needing attention

(Bugs which are not yet in progress or beyond.)

Current

Old (need to be flushed or refreshed:?)

Docs

The illustrated guide to scheduling has been published:
https://docs.openstack.org/nova/latest/reference/scheduling.html

Placement docs being linked into useful place:
https://review.openstack.org/#/c/498977/

Main Themes

Alternate Destinations

The complexity of the response data has led to some confusion on how
it should be represented. A spec has been started to try to come to
grips with the issues and resolve to a solution:

 https://review.openstack.org/#/c/498830/

There are a lot of open questions. The code for that work is in a
stack starting at:

 https://review.openstack.org/#/c/486215/

Migration UUIDs in Allocations

As most people have probably noticed, managing allocations during
various types of move operations is chaotic. One way to help make it
more understandable will be to use the uuid of a migration to identify
one of the "claims" used in the "doubling" process. This first
requires a uuid on the migration object. That's starting at:

 https://review.openstack.org/#/c/496933/

You'll see there that there is a large stack including things like
"Revert allocations by migration uuid". That's the goal, but if
implemented with currently available APIs there are some race
conditions so a new spec has been started to add a way to POST
allocation for multiple consumers in one go:

 https://review.openstack.org/#/c/499259/

It has a few options which need to be resolved, and the POC
implementation has exposed some other things will need to be tweaked:

 https://review.openstack.org/#/c/500073/

Traits

Work continues apace on getting filtering by traits working:

    https://review.openstack.org/#/c/489206/

This has some overlap with shared provider handling (below).

Shared Resource Providers

There's some support for shared resource providers on the placement
side of the scheduling equation, but the resource tracker is not yet
ready to support it. There is some work in progress, starting with
functional tests:

   https://review.openstack.org/#/c/490733/

Nested Resource Providers

This will start back up after we clean off the windscreen. The stack
begins at https://review.openstack.org/#/c/470575/5

Other Code

--
Chris Dent (⊙_⊙') https://anticdent.org/
freenode: cdent tw: @anticdent__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

asked Sep 1, 2017 in openstack-dev by cdent_plus_os_at_ant (12,800 points)   2 2 6
...