Bug 1412019

Summary: HPE [RFE] [Blazar] Resource reservation
Product: Red Hat OpenStack Reporter: hrushi <hrushikesh.gangur>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED DEFERRED QA Contact: Prasanth Anbalagan <panbalag>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: asimonel, berrange, dasmith, eglynn, fbaudin, hrushikesh.gangur, jdonohue, kchamart, markmc, mburns, sbauza, sferdjao, sgordon, smerrow, srevivo, vromanso
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-15 20:30:56 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1419948, 1465537    

Description hrushi 2017-01-11 01:33:01 UTC 
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
Comment 2 Stephen Gordon 2017-01-24 18:56:37 UTC 
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.