summaryrefslogtreecommitdiff
path: root/setup.cfg
diff options
context:
space:
mode:
authorZhiteng Huang <zhithuang@ebaysf.com>2014-01-28 14:23:04 +0800
committerZhiteng Huang <zhithuang@ebaysf.com>2014-07-15 17:56:39 +0800
commitc60044693190512fb14c3690ee49bbd1dae9e1e8 (patch)
treec3769f9e7b0a56dd88cc05c6ed50d9cfdb981e87 /setup.cfg
parentf9ae768811fda1a1ac0c1d40b74bb73c416dae52 (diff)
downloadcinder-c60044693190512fb14c3690ee49bbd1dae9e1e8.tar.gz
Add affinity/anti-affinity filters
Cinder has done a good job hiding the details of storage backends from end users by using volume types. However there are use cases where users who build their application on top of volumes would like to be able to 'choose' where a volume be created on. How can Cinder provide such capability without hurting the simplicity we have been keeping? Affinity/anti-affinity is one of the flexibility we can provide without exposing details to backends. The term affinity/anti-affinity here is to to describe the relationship between two sets of volumes in terms of location. To limit the scope, we describe one volume is affinity with the other one only when they reside in the same volume back-end (this notion can be extended to volume pools if volume pool support lands in Cinder); on the contrary, 'anti-affinity' relation between two sets of volumes simply implies they are on different Cinder back-ends (pools). This affinity/anti-affinity filter filters Cinder backend based on hint specified by end user. The hint expresses the affinity or anti-affinity relation between new volumes and existing volume(s). This allows end users to provide hints like 'please put this volume to a place that is different from where Volume-XYZ resides in'. This change adds two new filters to Cinder - SameBackendFilter and DifferentBackendFilter. These two filters will look at the scheduler hint provided by end users (via scheduler hint extension) and filter backends by checking the 'host' of old and new volumes see if a backend meets the requirement (being on the same backend as existing volume or not being on the same backend(s) as existing volume(s)). For example: Volume A is on 'backend 1', to create Volume B on the same backend as A, use: cinder create --hint same_host=VolA-UUID SIZE To create Volume C on different backend than that of A, use: cinder create --hint different_host=VolA-UUID SIZE Now, to create Volume D on different backend other than those of A and C, use: cinder create --hint different_host=VolA-UUID --hint different_host=VolC-UUID SIZE or: cinder create --hint different_host="[VolA-UUID, VolC-UUID]" SIZE implements bp: affinity-antiaffinity-filter DocImpact Change-Id: I19f298bd87b0069c0d1bb133202188d3bf65b770
Diffstat (limited to 'setup.cfg')
-rw-r--r--setup.cfg2
1 files changed, 2 insertions, 0 deletions
diff --git a/setup.cfg b/setup.cfg
index 3d47126b1..82d201f19 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -42,8 +42,10 @@ cinder.scheduler.filters =
AvailabilityZoneFilter = cinder.openstack.common.scheduler.filters.availability_zone_filter:AvailabilityZoneFilter
CapabilitiesFilter = cinder.openstack.common.scheduler.filters.capabilities_filter:CapabilitiesFilter
CapacityFilter = cinder.scheduler.filters.capacity_filter:CapacityFilter
+ DifferentBackendFilter = cinder.scheduler.filters.affinity_filter:DifferentBackendFilter
JsonFilter = cinder.openstack.common.scheduler.filters.json_filter:JsonFilter
RetryFilter = cinder.openstack.common.scheduler.filters.ignore_attempted_hosts_filter:IgnoreAttemptedHostsFilter
+ SameBackendFilter = cinder.scheduler.filters.affinity_filter:SameBackendFilter
cinder.scheduler.weights =
AllocatedCapacityWeigher = cinder.scheduler.weights.capacity:AllocatedCapacityWeigher
CapacityWeigher = cinder.scheduler.weights.capacity:CapacityWeigher