yahoo-eng-team team mailing list archive

[Armando Migliaccio <1169686@xxxxxxxxxxxxxxxxxx>]

AFAIK, the API version shouldn't be mandatory because clients should be
free to choose which API to talk to; furthermore, in case of services
like Glance or Ceilometer the API version needs to be omitted (as in, it
freaks out the client if you add it). That's particularly true from
OpenStack releases like Grizzly.

Since you are referencing Essex in your example, version enforcement
might have been true back then, but things move pretty fast in
Openstack-land :)

Your safest bet is DevStack and how endpoints are created there. If you
have a look at it, you'll see that there is no rule when it comes to
specifying the version.

Hope this helps!
Armando 

** Changed in: quantum
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1169686

Title:
  quantum api endpoint in keystone does not include api version

Status in OpenStack Quantum (virtual network service):
  Invalid

Bug description:
  The quantum api endpoint registered in keystone does not include the
  api version.  Other services include the api version in their keystone
  endpoints, and our users have come to expect to see the api version in
  the endpoint URL.  Why is quantum different in this regard?

  For example, from network admin guide: --publicurl
  "http://10.211.55.17:9696/";

  Other service examples can be seen at http://docs.openstack.org/essex
  /openstack-compute/starter/content/Creating_Endpoints-d1e469.html, for
  example:

  nova-compute: http://10.10.10.2:8774/v2/$(tenant_id)s
  glance: http://10.10.10.2:9292/v1
  swift: http://10.10.10.2:8080/v1/AUTH_$(tenant_id)s
  keystone: http://10.10.10.2:5000/v2.0

  Please note that the quantum client 2.2.0 automatically adds 'v2.0' to
  the endpoint URL returned by keystone (i.e. simply adding '/v2.0' to
  the quantum endpoint url causes the quantum client to issue requests
  on x.x.x.x:9696/v2.0/v2.0 which of course does not work).

  Although this is more a question than a bug, I am filing as a bug per
  discussion with Salvatore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1169686/+subscriptions