CI / promotion: Nova isn't aware of the nodes that were registered with Ironic

It looks like Nova isn't aware of the nodes that were registered with ironic.

introspection passed and the ironic logs show the nodes being powered up and down fine

But when nova tries to schedule a node to boot the scheduler has no nodes to choose from

2017-03-19 07:19:34.157 13121 DEBUG nova.filters [req-702e96af-318d-4611-af19-d6a1f3321c6a 7727004211f045abb45f22d0773242e3 c8da1df6de9841d5a922d5da5b69ff92 - - -] Starting with 0 host(s) get_filtered_objects /usr/lib/python2.7/site-packages/nova/filters.py:70

"Starting with 0 host(s)"

I would expect that "0" to be a "3"

So the new code sets a min_unit equal to the max_unit:

2017-03-21 03:54:38.198 9771 INFO nova.scheduler.client.report [req-1bbd4b23-5c6d-4644-a82b-3fd15c3d2e10 - - - - -] Inventory data after processing custom resource classes for provider e717ea77-1bd5-4122-ba13-60cd4d1342e4: {'VCPU': {'allocation_ratio': 1.0, 'total': 4, 'reserved': 0, 'step_size': 1, 'min_unit': 4, 'max_unit': 4}, 'MEMORY_MB': {'allocation_ratio': 1.0, 'total': 8192, 'reserved': 0, 'step_size': 1, 'min_unit': 8192, 'max_unit': 8192}, 'DISK_GB': {'allocation_ratio': 1.0, 'total': 40, 'reserved': 0, 'step_size': 1, 'min_unit': 40, 'max_unit': 40}}

Since the tripleo flavors undersubscribe (e.g. request 1 vcpu), the resource providers here don't match. This previously worked because tripleo doesn't use the exact match filters. I think to maintain old behavior, we want to:

* set a smaller (1?) min_unit for these properties
* allocate all resources for baremetal resources, even if the flavor is smaller than the resource (this may already be done, I'm not sure)

Folks who want to continue using the exact match filters can do so. The transition to custom resource classes will eliminate the discussion, as we won't be using cpu/ram/disk anymore.

I'll have a patch up for this today sometime, btw.

Fix proposed to branch: master
Review: https://review.openstack.org/448098

Reviewed: https://review.openstack.org/448098
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fe8415060ca452990d7019a03eaaa4b92aadfe8b
Submitter: Jenkins
Branch: master

commit fe8415060ca452990d7019a03eaaa4b92aadfe8b
Author: Jim Rollenhagen <email address hidden>
Date: Tue Mar 21 13:32:35 2017 +0000

    Ironic: hardcode min_unit for standard resources to 1

    We've always left users a choice whether to do exact matching or
    "at least" matching for baremetal flavors, by installing the
    exact match scheduler filters. The patch to add get_inventory
    broke this by setting min_unit and max_unit to be equal for
    baremetal resources.

    Set min_unit to 1 for these resources so that deployers can continue
    to use the exact match filters to decide how they want baremetal
    flavors to be matched.

    Change-Id: I04fdcb73674eb7193e82a61d856747d7985a2b65
    Closes-Bug: #1674236

This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.