Goals: Provide standard capabilities from drivers that the admins can specify from volume types. Improve the visibility of what policies are possible with your storage solution via Cinder client and Horizon. Capabilities need to be exposed to the admin from Cinder, so that Cinder is not limiting what storage backends can do. These capabilities can include, but are not limited to QoS, replication factor, bandwidth control, etc. http://specs.openstack.org/openstack/cinder-specs/specs/liberty/standard-capabilities.html
Tested using: python-cinder-7.0.1-5.el7ost.noarch openstack-cinder-7.0.1-5.el7ost.noarch python-cinderclient-1.4.0-1.el7ost.noarch [stack@instack ~]$ cinder get-capabilities overcloud-controller-0.localdomain@Netapp1 +---------------------+-----------------------------------------------------------------------+ | Volume stats | Value | +---------------------+-----------------------------------------------------------------------+ | description | None | | display_name | None | | driver_version | 1.0.0 | | namespace | OS::Storage::Capabilities::overcloud-controller-0.localdomain@Netapp1 | | pool_name | None | | storage_protocol | iSCSI | | vendor_name | NetApp | | visibility | None | | volume_backend_name | Netapp1 | +---------------------+-----------------------------------------------------------------------+ +--------------------+---------------------------------------------------------------------------------------------------+ | Backend properties | Value | +--------------------+---------------------------------------------------------------------------------------------------+ | compression | {u'type': u'boolean', u'description': u'Enables compression.', u'title': u'Compression'} | | qos | {u'type': u'boolean', u'description': u'Enables QoS.', u'title': u'QoS'} | | replication | {u'type': u'boolean', u'description': u'Enables replication.', u'title': u'Replication'} | | thin_provisioning | {u'type': u'boolean', u'description': u'Sets thin provisioning.', u'title': u'Thin Provisioning'} | +--------------------+---------------------------------------------------------------------------------------------------+
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0603.html