tempest/releasenotes/notes/14.0.0-volume-clients-as-library-309030c7a16e62ab.yaml

---
features:
  - |
    Define volume service clients as libraries.
    The following volume service clients are defined as library interface,
    so the other projects can use these modules as stable libraries without
    any maintenance changes.

    * volumes_client(v1)
    * volumes_client(v2)
    * capabilities_client(v2)
    * scheduler_stats_client(v2)
Move volume service clients under tempest.lib Tempest provides a stable library interface and I think we can use it for volume clients. Partially implements blueprint consistent-service-method-names Change-Id: Ia2d87360a6d88e5f54ecd00efbf6730b06484c99 2016-09-15 10:37:57 +03:00			`---`
			`features:`
			`- \|`
			`Define volume service clients as libraries.`
			`The following volume service clients are defined as library interface,`
			`so the other projects can use these modules as stable libraries without`
			`any maintenance changes.`

			`* volumes_client(v1)`
			`* volumes_client(v2)`
Create two new clients under tempest.lib libary There are two API v2 actions that only admin has the permission to excute, according to: http://developer.openstack.org/api-ref-blockstorage-v2.html#listPools http://developer.openstack.org/api-ref-blockstorage-v2.html#showBackendCapabilities Currently, those actions reside on BaseVolumesClient class and I think we should separate them to new files: tempest/lib/services/volume/v2/capabilities_client.py tempest/lib/services/volume/v2/scheduler_stats_client.py Partially implements blueprint consistent-service-method-names Change-Id: I48e5e19331dd636a093e1817e5c2ea31534ae2c3 2016-09-04 12:36:04 +03:00			`* capabilities_client(v2)`
			`* scheduler_stats_client(v2)`