Instance reservation with no affinity rule
Currently, instance reservation support only ANTI-AFFINITY rule because it is impossible to estimate how much resources will be actually consumed without the anti-affinity rule. This affinity constraint should be abolished, i.e. support AFFINITY and NO-AFFINITY rules, for improving flexibility of reservation. Related to: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Masahito Muroi
- Priority:
- Medium
- Drafter:
- Hiroaki Kobayashi
- Direction:
- Approved
- Assignee:
- Tetsuro Nakamura
- Definition:
- Approved
- Series goal:
- Accepted for stein
- Implementation:
-
Implemented
- Milestone target:
-
stein-3
- Started by
- Pierre Riteau
- Completed by
- Pierre Riteau
Related branches
Related bugs
Sprints
Whiteboard
The feature is supposed to be implemented once Blazar has supported PlacementAPI. See the long-term goal in the instance reservation's spec.
https:/
Addressed by: https:/
Spec: Placement API support for instance reservation
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Change pickup_hosts() to support affinity=True
Addressed by: https:/
Change update_
Addressed by: https:/
Change placement call to consider affinity=True
Addressed by: https:/
Support affinity=True in reallocation
Addressed by: https:/
Start working on no affinity instance reservation
Addressed by: https:/
Update docs for instance reservation affinity
Addressed by: https:/
Support to add reservation inventory
Addressed by: https:/
Distinguish hypervisor_hostname and service_name
Addressed by: https:/
Use oslo_serializat
Work Items
Dependency tree
* Blueprints in grey have been implemented.
