Enable anti-affinity check for instance reservation

[Hiroaki Kobayashi]

The affinity/anti-affinity checks of Nova do not work correctly since Pike [1] because upcalls from the computes to the scheduler (or other control services) cannot occur in deployments with multiple (v2) cells [2]. These affinity/anti-affinity checks have to be enabled for instance reservation.

[1] https://docs.openstack.org/releasenotes/nova/pike.html#id10
[2] https://docs.openstack.org/nova/latest/user/cellsv2-layout.html#operations-requiring-upcalls

[Masahito Muroi (muroi-masahito)]

Need a design to fix the problem though the use of placement API in Blazar is still under the discussion.

[Tetsuro Nakamura (tetsuro0907)]

We close this bug providing affinity = None option as default in https://blueprints.launchpad.net/blazar/+spec/no-affinity-instance-reservation

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/627857
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=122c61ad8874891f772cf69ec360ab63661ce33a
Submitter: Zuul
Branch: master

commit 122c61ad8874891f772cf69ec360ab63661ce33a
Author: Tetsuro Nakamura <email address hidden>
Date: Mon Dec 31 06:03:50 2018 +0000

    Expose instance reservation affinity support

    For instance reservation, blazar has checked the affinity policy and
    raised an exception if it is None or True. Since we are now ready to
    support affinity=None/True, this patch deletes the check and adds a
    migration script to accept a NULL value for the affinity column in the
    database.

    This patch also updates the CLI usage document of the instance
    reservation and adds the release note for the instance reservation
    affinity policy.

    Change-Id: Icf26d1b7dffe64f82d7084dcebb5df1c7c9f106d
    Closes-Bug: #1737676
    Blueprint: no-affinity-instance-reservation

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/blazar 3.0.0.0rc1 release candidate.