Hi all, Background: at SAP we would like to have OpenStack Identity V3 support in jclouds (see https://issues.apache.org/jira/browse/JCLOUDS-114), and I am working on implementing it. I already implemented OpenStack Identity V3 support in Fog (Ruby's equivalent to jclouds) - see https://github.com/fog/fog/commit/803dedb297023a8ceee17d73e7c9e16764f3b34a for details. Using org.jclouds.keystone.v2_0 as a starting point, it's reasonably clear to me how to go about implementing a v3 equivalent.
My problem is this: I can't figure out how, in the jclouds codebase, to let the user use v3 authentication instead of v2 authentication. Ideally I would like to get the same behaviour as Fog: when creating (for example) a NovaApi object, the code would check to see if the endpoint URL ends in "/v2.0" or "/v3" and use the v2.0 or v3 Identity implementation accordingly. A workable (although suboptimal) alternative would be to let the user somehow specify v3 as an override when creating a NovaApi object, e.g. by passing in the v3 AuthenticationApiModule (which I already tried, but doesn't work as-is). Can anybody help me with this? I'm happy to pair-program with a more experience jclouds dev if that helps. Thanks in advance, Darren Darren Hague Cloud Lifecycle Management: Monsoon DevOps Team, SAP (UK) Limited, Clockhouse Place, Bedfont Road, Feltham TW14 8HD, United Kingdom T +44 208 917-8117, M +44 7764 97-8117, E d.ha...@sap.com