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 services seem to handle multiple versions without them. So, along came experimentation. Turns out, the things that broke could use cinder v2 if the "volume" service used /v2 in the endpoints... to the best of our testing abilities. I hoped cinder would adopt endpoints without a version or some other way to reduce the catalog clutter in Liberty, but no such luck and testing revealed some potential issues with the approach taken in Kilo version of the installation guide. So, we reverted the cinder configuration in the Liberty version of the installation guide [1] to use /v1 in the endpoints for the "volume" service and /v2 in the endpoints for the "volumev2" service. We'll evaluate this situation again for Mitaka.
[1] http://docs.openstack.org/liberty/install-guide-ubuntu/cinder-controller-install.html#prerequisites On Fri, Dec 4, 2015 at 3:40 PM, Anne Gentle <annegen...@justwriteclick.com> wrote: > > > On Thu, Dec 3, 2015 at 9:33 AM, Salman Toor <salman.t...@it.uu.se> 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 create \ >> --publicurl http://*controller*:8776/v2/%\(tenant_id\)s \ >> --internalurl http://*controller*:8776/v2/%\(tenant_id\)s \ >> --adminurl http://*controller*:8776/v2/%\(tenant_id\)s \ >> --region RegionOne \ >> volume >> >> Shouldn’t it be like following (colour in RED) >> >> openstack endpoint create \ >> --publicurl http://*controller*:8776/v1/%\(tenant_id\)s \ >> --internalurl http://*controller*:8776/v1/%\(tenant_id\)s \ >> --adminurl http://*controller*:8776/v1/%\(tenant_id\)s \ >> --region RegionOne \ >> volume >> >> >> Is that a documentation error? Can someone please confirm? >> >> >> > For the install documentation, especially one in use for and tested as > many months as the Kilo one, you can be assured it is not a documentation > error. > > It is a specific choice by our install doc team to ensure that all > requests are redirected to a v2 endpoint. Otherwise your Dashboard will not > display the Block Storage information. > > If you're ever in doubt, feel free to search through fixed documentation > bugs or read the commentary, such as: > https://bugs.launchpad.net/openstack-manuals/+bug/1508355 > > Thanks, > Anne > > >> Thanks in advance. >> >> Regards.. >> Salman. >> >> >> >> _______________________________________________ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> > > > -- > Anne Gentle > Rackspace > Principal Engineer > www.justwriteclick.com > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
