Allow compute nodes to use shared storage provider for DISK_GB resources

Registered by Tushar Patil on 2019-04-05

Allow compute node resource providers to use DISK_GB inventory configured in a shared storage resource provider by using aggregate relationship.

Shared resource providers are marked with a standard trait called `MISC_SHARES_VIA_AGGREGATE`. This indicates that the provider allows its inventory to be consumed by other resource providers associated via an aggregate link.

For example, assume we have two compute nodes, CN_1 and CN_2, each with inventory of VCPU and MEMORY_MB but not DISK_GB (in other words, these are compute nodes with no local disk). There is a resource provider called
"NFS_SHARE" that has an Inventory of DISK_GB and has the MISC_SHARES_VIA_AGGREGATE trait. Both the "CN_1" and "CN_2" compute node resource providers and the "NFS_SHARE" resource provider are associated with an aggregate called "AGG_1".

Earlier, in Rocky release, an attempt was made to add this support but it wasn't a clean fix for LP bug 1784020.

Blueprint information

Status:
Started
Approver:
None
Priority:
Undefined
Drafter:
Tushar Patil
Direction:
Needs approval
Assignee:
Shilpa Devharakar
Definition:
Pending Approval
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Eric Fried on 2020-01-30

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/support-shared-storage-resource-provider,n,z

Addressed by: https://review.openstack.org/650188
    Allow compute nodes to use DISK_GB from shared storage RP

Gerrit topic: https://review.openstack.org/#/q/topic:bp/support-shared-storage-resource-provider

Gerrit topic: https://review.opendev.org/#/q/topic:bp/support-shared-storage-resource-provider

Addressed by: https://review.opendev.org/650188
    Allow compute nodes to use DISK_GB from shared storage RP

Deferring this out of Train since it wasn't approved and we're about 2 weeks from feature freeze. -- mriedem 20190829

[efried 20200213] My understanding is that we've agreed this needs a Placement API change, and that's not going to be possible in U, so deferring.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.