settingsLogin | Registersettings

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

0 votes

Placement Update 31

What Matters Most

rc1 was just cut. There was (and still is) a lot of last minute
change going on in code related to placement, the resource tracker
and the scheduler. No one will be surprised if there are additional
issues to resolve. So at this point important things to be doing are:

  • watching for new bugs tagged placement, scheduler or resource-tracker
  • inspecting the logs of tempest runs (even those that have passed)
    for unexpected log messages related to managing inventory or
  • using the code, especially to do things like resize, migrate,
    evacuate, etc
  • reviewing code

What's Changed

The scheduler and the resource tracker are now doing a little dance
with allocations that's being called "doubling". When an instance
needs to be in two places at once for a while (during any kind of
migration) the allocations related to that instance need to be
doubled. Conceptually this is pretty simple but various limitations
with the way we manage data and with the way we might have both pike
and ocata compute nodes at the same time make it rather involved.

The effort and attention required to get that working has meant that
shared resource providers, though somewhat working on the placement
side, are not yet supported on the nova side.

Early in queens we should add a uuid to migrations. This will be a
first step in making the doubling actions easier to process and clean

Help Wanted

See the beginning of this message.

Main Themes

Custom Resource Classes for Ironic

Some last minute issues were discovered with the management of
custom resource classes and existing inventory for Ironic. A recent
change which reflects the situation is:

The code to migrate flavors is still under review, mostly waiting to
see if stuff that uses it works:


Work continues apace on getting filtering by traits working:

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

Support for using traits in any practical way did not make it in Pike.

Traits on /resource_providers:

Shared Resource Providers

Though sharing providers didn't make their debut in Pike either, Alex
did find (and fix) some bugs, starting at:

Nested Resource Providers

This will start back up after we clean off the windscreen.


A very small number of docs patches left to do for the api-ref:

There are two changes which depend on that stack merging. A placement
publishing job:

and an addition of 'placement' to service-type-authority

Real live genuine placement docs will be totally awesome. Nearly

Other Code

(A lot of the stuff in this list is a loose end created in the last
two weeks of racing to rc1. Some of it is stuff that's just been
around for a while. I've tried to put more relevant stuff at the top
of the list.)

Chris Dent (⊙_⊙')
freenode: cdent tw: @anticdent__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)

asked Aug 11, 2017 in openstack-dev by cdent_plus_os_at_ant (12,800 points)   2 2 6