Open Stack

On 2/24/15, 12:54 PM, "Jesse Keating" <jlk at bluebox.net> wrote:

>On 2/23/15 8:13 PM, Fischer, Matt wrote:
>> What does everyone else do here?
>
>I've been trying to get this to work as well. I thought I had it going
>with just putting the v2 path into the volume endpoint url, and that
>worked from Nova's POV (including novaclient), but cinderclient did not
>like it (nor did openstackclient).
>
>If I have volume and volumev2 services respectively with v1 and v2 URLs
>novaclient and cinderclient are happy, however nova-api winds up picking
>v1 to use instead of v2 and then continues to complain about deprecation
>of the v1 protocol.
>
>To influence nova-api to make use of the v2 end point, when both are in
>the catalog, you have to set catalog_info in the [cinder] section of
>nova.conf, to something like "volumev2:cinderv2:publicURL". In Juno this
>defaults to "volume:cinder:publicURL", but beyond juno it defaults to
>"volumev2:cinderv2:publicURL" thanks to
>https://bugs.launchpad.net/nova/+bug/1390131
>
>SO, on Juno, to use v2 API, it sure seems like you need volumev2 end
>point, a modified catalog_info in nova.conf, and as noted in the other
>message, a configuration to cinderclient to make use of the v2 API.
>
>We will be testing this scenario a bit for functionality, including
>encrypted volumes, over the next week or so, and hopefully should have
>something to report by the midcycle meetup, if anybody is interested.
>
>--
>-jlk


I¹d like to find out your results a the meetup. I think for now we¹re
going to stick with both endpoints enabled and revisit it later so having
that info would be helpful.


This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.