[openstack-dev] [Cinder][Horizon] Cinder v2 endpoint name: volumev2 is required? volume is okay?

Ivan Kolodyazhny e0ne at e0ne.info
Thu Oct 15 16:16:05 UTC 2015


Hi Akihiro,

Cinder itself doesn't care what keystone endpoint name is configured for
it. python-cinderclient uses cinderv2 for service name [1], [2] by default.

AFAIK, some other components like Rally expects "volumev2" endpoint for API
v2. "volume" is used for Tempest by default.

[1]
https://github.com/openstack/python-cinderclient/blob/92f3d35d5b6ba54704096288fb2a5ae93f5e1985/cinderclient/v2/shell.py#L206
[2]
https://github.com/openstack/python-cinderclient/blob/92f3d35d5b6ba54704096288fb2a5ae93f5e1985/cinderclient/shell.py#L585

Regards,
Ivan Kolodyazhny

On Wed, Oct 14, 2015 at 2:46 PM, Akihiro Motoki <amotoki at gmail.com> wrote:

> Hi Cinder team,
>
> What is the expected service name of Cinder v2 API in keystone catalog?
> DevStack configures "volumev2" for Cinder v2 API by default.
>
> Can we "volume" for Cinder v2 API or do we always need to use "volumev2"
> in deployments with only Cinder v2 API (i.e. no v1 API) ?
>
> The question was raised during the Horizon review [1].
> The current Horizon code assumes "volumev2" is configured for Cinder v2
> API.
> Note that review [1] itself makes Horizon work only with Cinder v2 API.
> I would like to know Horizon team need to consider "volume" endpoint
> for Cinder v2 API or not.
>
> [1] https://review.openstack.org/#/c/151081/
> [2] https://bugs.launchpad.net/horizon/+bug/1415712
>
> Thanks,
> Akihiro
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151015/033765ea/attachment.html>


More information about the OpenStack-dev mailing list