Pranali Deore 7a1742c668 Add logging when filtering returns nothing
When hosts are filtered for a request, and no host passes all the
filters, operators can only see the last filter run; they have no
visibility into which filter removed which host. This attempts to
improve this situation by tracking the hosts remaining after each
filter is run and the number of hosts removed. If no host is left,
that information along with volume ID of the request would be logged.

Since that can be a lot of information, it will call LOG.info with
just the counts for all but the final filter, which will contain
the last deleted host names, LOG.debug will output the full record
of each filter and the hosts remaining after each step.

This will better enable operators to determine why a particular host
was not selected.

Change-Id: I3baf75a4a4430c55b30dde1cae86fa5e195ec6d3
2016-07-05 07:26:04 -04:00
2016-06-13 15:21:47 +00:00
2012-05-03 10:48:26 -07:00
2012-05-03 10:48:26 -07:00
2016-07-01 15:08:43 +05:30
2012-05-03 10:48:26 -07:00
2015-06-11 17:19:19 +02:00
2016-03-02 14:33:25 -05:00
2015-09-18 16:37:17 +00:00

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.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://git.openstack.org/openstack/cinder.git

For developer information please see HACKING.rst

You can raise bugs here http://bugs.launchpad.net/cinder

Python client

https://git.openstack.org/cgit/openstack/python-cinderclient

Description
OpenStack Block Storage (Cinder)
Readme 911 MiB
Languages
Python 99.7%
Smarty 0.3%