
Currently cinder support choosing volume backend according to free_capacity and allocated_capacity. Volume Num Weighter is that scheduler could choose volume backend based on volume number in volume backend, which could provide another mean to help improve volume-backends' IO balance and volumes' IO performance, see details in ref [1] and [2]. blueprint support-volume-num-weighter Ref: [1]https://blueprints.launchpad.net/cinder/+spec/support-volume-num-weighter [2]https://review.openstack.org/#/c/99683/ Change-Id: Id9275ed954f1b35ee8d7bee0f0b61cc3a7c48f63
The Choose Your Own Adventure README for Cinder
You have come across a storage service for an open cloud computing service. It has identified itself as "Cinder." It was abstracted from the Nova project.
To monitor it from a distance: follow @openstack on twitter.
To tame it for use in your own cloud: read http://docs.openstack.org
To study its anatomy: read http://cinder.openstack.org
To dissect it in detail: visit http://github.com/openstack/cinder
To taunt it with its weaknesses: use http://bugs.launchpad.net/cinder
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING.rst
Description
Languages
Python
99.7%
Smarty
0.3%