| ghanshyam | f2f4384 | 2018-08-09 07:13:46 +0000 | [diff] [blame] | 1 | --- | 
|  | 2 | deprecations: | 
|  | 3 | - | | 
|  | 4 | The v2 volume API has been deprecated since Pike release. | 
|  | 5 | Volume v3 API is current and Tempest volume tests can | 
|  | 6 | be run against v2 or v3 API based on config option | 
|  | 7 | ``CONF.volume.catalog_type``. If catalog_type is ``volumev2``, then | 
|  | 8 | all the volume tests will run against v2 API. If catalog_type is | 
|  | 9 | ``volumev3`` which is default in Tempest, then all the volume | 
|  | 10 | tests will run against v3 API. | 
|  | 11 | That makes below config options unusable in Tempest which used to | 
|  | 12 | select the target volume API for volume tests. | 
|  | 13 |  | 
|  | 14 | * ``CONF.volume-feature-enabled.api_v2`` | 
|  | 15 | * ``CONF.volume-feature-enabled.api_v3`` | 
|  | 16 |  | 
|  | 17 | Tempest deprecate the above two config options in Rocky release | 
|  | 18 | and will be removed in future. Alternatively ``CONF.volume.catalog_type`` | 
|  | 19 | can be used to run the Tempest against volume v2 or v3 API. |