dcdce87822
When FilterScheduler was first introduced into Cinder, drivers were required for the first time to report capacity. Some drivers preferred to report 'infinite' or 'unknown' capacity because they were doing thin-provisioning or the total capacity kept increasing. Now that we have better support for thin-provisioning and we do find unrealistic capacity couldn't do us any good in making optimal scheduling decision, because 'infinite' and 'unknown' would always have the highest weight when the weight multiplier is positive, which in most cases it is. Drivers are expected to avoid sending 'infinite' 'unknown' capacity anymore, instead, should report an actual real number for total/free capacity. This fix doesn't fix the driver, instead a small tweak is added to CapacityWeigher in order to downgrade those drivers who report 'infinite' or 'unknown' as free capacity. In particular, those who report 'infinite'/'unknown' free capacity will be adjusted to be the one has lowest weight, no matter in 'spreading' (weight multiplier>0) or 'stacking' (weight multiplier<0) mode. DocImpact Change-Id: Ied087386a1a2f43e6a77499a817d5c637ef448f6 Partial-bug: #1350638
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