Re: [Openstack-operators] Cinder V1 endpoints

2015-12-07 Thread Jesse Keating
Reading that linked bug, it does indeed seem like the use of v2 in the path for both volume and volumev2 was indeed a mistake. Further supported by http://lists.openstack.org/pipermail/openstack-operators/2015-December/009092.html It may have been intended for the documentation at the time, but

Re: [Openstack-operators] Cinder V1 endpoints

2015-12-04 Thread Anne Gentle
On Thu, Dec 3, 2015 at 9:33 AM, Salman Toor wrote: > Hi, > > In the following link of Kilo document the cinder V1 endpoints have v2 in > it. > > > http://docs.openstack.org/kilo/install-guide/install/yum/content/cinder-install-controller-node.html > > openstack endpoint

Re: [Openstack-operators] Cinder V1 endpoints

2015-12-04 Thread Matt Kassawara
Updates for the Kilo version of the installation guide included adding support for cinder v2. The initial approach involved disabling cinder v1, but we quickly found out that broke certain things. However, having two separate service entries and groups of endpoints didn't make sense because other

Re: [Openstack-operators] Cinder V1 endpoints

2015-12-03 Thread Jesse Keating
Yes, that appears to be a documentation error. - jlk On Thu, Dec 3, 2015 at 7:33 AM, Salman Toor wrote: > Hi, > > In the following link of Kilo document the cinder V1 endpoints have v2 in > it. > > >

[Openstack-operators] Cinder V1 endpoints

2015-12-03 Thread Salman Toor
Hi, In the following link of Kilo document the cinder V1 endpoints have v2 in it. http://docs.openstack.org/kilo/install-guide/install/yum/content/cinder-install-controller-node.html openstack endpoint create \ --publicurl http://controller:8776/v2/%\(tenant_id\)s \ --internalurl

Re: [Openstack-operators] Cinder V1 endpoints

2015-12-03 Thread Salman Toor
Thanks! /Salman. PhD, Scientific Computing Researcher, IT Department, Uppsala University. Senior Cloud Architect, SNIC. Cloud Application Expert, UPPMAX. Visiting Researcher, Helsinki Institute of Physics (HIP). salman.t...@it.uu.se