Adrian Cole created JCLOUDS-779:
-----------------------------------
Summary: OpenStack/Rackspace providers might not honor
jclouds.regions property
Key: JCLOUDS-779
URL: https://issues.apache.org/jira/browse/JCLOUDS-779
Project: jclouds
Issue Type: Task
Components: jclouds-core
Reporter: Adrian Cole
JCLOUDS-774 identified an issue where the jclouds.regions property wasn't
uniformly honored, particularly due to how RegionIdToURISupplier was
implemented.
Basically, RegionIdToURISupplier's KeySet is used to identify the available
regions one can choose. As far as I can tell, all implementations ignore the
whitelist users sets via the jclouds.regions property.
Since ec2 is already fixed, the remaining implementations of
RegionIdToURISupplier are openstack or rackspace variants.
There are many of these, and I'm not sure which codebases of
rackspace/openstack work anymore. For example, I'm fairly certain that
rackspace legacy providers should be deleted, so working on that code would be
a waste of time.
At any rate, here are the affected classes.
org.jclouds.openstack.keystone.v1_1.suppliers.RegionIdToURIFromAuthForServiceSupplier
org.jclouds.openstack.keystone.v2_0.suppliers.RegionIdToURIFromAccessForTypeAndVersion
org.jclouds.openstack.keystone.v2_0.suppliers.RegionIdToAdminURIFromAccessForTypeAndVersion
org.jclouds.rackspace.cloudidentity.v1_1.suppliers.RegionIdToURIFromAuthForServiceSupplier
My recommendation would be at least to address the v2_0 suppliers, probably
with the same approach as ec2's DescribeRegionsForRegionURIs class.
Since openstack's tests for the corresponding suppliers are very complex, I'd
recommend rewriting them similar to DescribeRegionsForRegionURIsMockTest as a
part of completing this jira.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
