You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Zack Shoylev (JIRA)" <ji...@apache.org> on 2014/11/12 20:56:36 UTC

[jira] [Created] (JCLOUDS-773) Support consistently versioned endpoints for openstack services

Zack Shoylev created JCLOUDS-773:
------------------------------------

             Summary: Support consistently versioned endpoints for openstack services
                 Key: JCLOUDS-773
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-773
             Project: jclouds
          Issue Type: New Feature
          Components: jclouds-core, jclouds-labs-openstack
    Affects Versions: 1.8.1, 1.8.0
            Reporter: Zack Shoylev
            Assignee: Zack Shoylev
             Fix For: 2.0.0


Glance and Neutron (as well as other openstack services) have the option to use version-agnostic endpoints or endpoints with version-negotiation. For example, https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-glance/src/main/java/org/jclouds/openstack/glance/functions/RegionToEndpointNegotiateVersion.java

Currently openstack services and providers have a lot of freedom do define endpoints. This means parsing the service catalog is fragile, and does not take into account having to negotiate for a version by default, or dealing with endpoints that might or might not contain version information.

The proposed solutions are to
0) Determine what is the right/consistent openstack way to deal with API versioning for endpoints.
1) Move the RegionToEndpointNegotiateVersion up to the openstack level (includes fixing tests and ServiceApis to work).
2) Also make it easier for providers to override endpoints/versioning - if needed




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)