Affinity and anti-affinity scheduler filter

Registered by Huang Zhiteng

Our consumers who build their application on top of volumes would like to be able to set affinity or anti-affinity between new volumes being created and existing volumes. One use case is DB team build MySQL master onto one volume, they'd prefer to put new volumes for slave DBs to different backends from where the master DB resides, for the sake of high availability. Another use case is a log processing project would like to have fast storage as possible, so they create soft RAID across multiple volumes。 They want to put these volumes as close to each other as possible, ideally on the same storage backend.

Blueprint information

Status:
Complete
Approver:
John Griffith
Priority:
Undefined
Drafter:
Huang Zhiteng
Direction:
Needs approval
Assignee:
Huang Zhiteng
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Huang Zhiteng
Completed by
Sean McGinnis

Related branches

Sprints

Whiteboard

(smcginnis): Marking obsolete as this has been sitting out there for a long time. If this is still needed, please submit a new bp.

Gerrit topic: https://review.openstack.org/#q,topic:bp/affinity-antiaffinity-filter,n,z

Addressed by: https://review.openstack.org/106708
    Add affinity/anti-affinity filters

This BP has been implemented via above change in Icehouse.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.