Bug 1126532

Summary:	[RFE] Assign seperate compute nodes for separate projects?
Product:	Red Hat OpenStack	Reporter:	Sadique Puthen <sputhenp>
Component:	openstack-nova	Assignee:	Sylvain Bauza <sbauza>
Status:	CLOSED WONTFIX	QA Contact:	Shai Revivo <srevivo>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	eglynn, kschroed, sbauza, sgordon, srevivo
Target Milestone:	Upstream M2	Keywords:	FutureFeature, Triaged
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-05 17:08:36 UTC	Type:	Bug
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:	1154162

Description Sadique Puthen 2014-08-04 16:30:13 UTC

Description of problem:

customer would like to assign dedicated compute node for specific projects .So, every VM of that project should scheduled on that compute node.

Eg, We have three compute nodes A, B, C & two tenants TenA, TenB.

Our requirement is to schedule TenA Vms  onto Node A and all other tenants(TenB etc) VM can go either on B or C node. A reserve for particular tenants.

There is a blueprint started upstream to make this possible. https://blueprints.launchpad.net/nova/+spec/whole-host-allocation

Once this is done, customer would like this to be included in RHEL-OSP release.

Comment 1 Sylvain Bauza 2014-08-22 17:42:17 UTC

I just discussed upstream with the owner of whole-host-allocation (Phil Day), he will provide two specs for Kilo, one for dedicating hosts and one for pclouds idea.

On my side, I'll discuss with Belmiro from CERN to see when he wants to do https://review.openstack.org/99476. If not, I'll provide by myself the patch for Kilo (it should be easy to backport to Juno if so)

There are also 2 patches upstream for the same thing, but I disagree with the implementation :
https://review.openstack.org/116194
https://review.openstack.org/115824


All of this work will be happen on Kilo anyway.

Comment 5 Sylvain Bauza 2016-04-12 14:32:28 UTC

No clear sign of life yet. Belmiro was wanting to work on it by Kilo (as I said earlier) but it seems he left that out finally.

Comment 8 Stephen Gordon 2017-01-24 21:37:52 UTC

*** Bug 1204979 has been marked as a duplicate of this bug. ***