Both customers and ETSI standard demand resource reservation feature to be provided by VIM. HPE is actively participating in bring back openstack blazar back into works. This requirement suggest making blazar as part of RHOSP.
- https://blueprints.launchpad.net/blazar/+spec/stop-using-customized-filter - Stop using customized scheduler filter to improve interoperability
- https://blueprints.launchpad.net/blazar/+spec/update-reserved-capacity - Allow users to update reserved resource capacity
- https://blueprints.launchpad.net/blazar/+spec/terminate-lease-at-anytime - Allow users to terminate lease at anytime
https://review.openstack.org/#/c/406666/ - Updated versions of few required libraries
https://review.openstack.org/#/c/403369/ - Replace tempest logging module with oslo_log
https://review.openstack.org/#/c/407202/ - Update default environment list
https://review.openstack.org/#/c/409067/ - Use jsonutils from oslo.serialization
I do not envisage we will have scope to include this in the RHOSP 12 release cycle. The easiest way to assist with speeding things up from a partner perspective would be to contribute packaging, puppet, etc. related enablement in the relevant upstreams. Flagging for re-evaluation in 13 cycle.