Adds rackspace cloudnetworks-us provider

Specifically for this PR - the plan is to provide something for users as a stopgap solution for a very-much evolving API until we can address this in openstack-core. And yes, unfortunately this has been done before (glance in labs). Not an excuse - just pointing out that we should have sufficient incentive, I hope, to address this problem in openstack-core next. Because I don't fully understand the possible issues/intricacies of the openstack service catalog versioning (yet) and how to get it to work with our keystone module, and because it does not affect the user-facing aspects of the API, it seems to be an acceptable, temporary trade-off - to me at least.

In conclusion, regardless of how/if this PR makes it in, our priority will be on figuring out versioning on the openstack level next - as I already mentioned, this seems to not be limited to Neutron.

________________________________
From: Adrian Cole [notifications@github.com]
Sent: Wednesday, November 12, 2014 10:54 AM
To: jclouds/jclouds-labs-openstack
Cc: Zack Shoylev
Subject: Re: [jclouds-labs-openstack] Adds rackspace cloudnetworks-us provider (#169)


In openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/NeutronApi.java:

> @@ -41,7 +40,7 @@
>  /**
>   * Provides access to the OpenStack Networking (Neutron) v2 API.
>   */
> -@Path("{" + Constants.PROPERTY_API_VERSION + "}")
> +@Path("v2.0")


I think it is correct to say we disagree. You are spaghetting around addressing openstack core, which is a fairly regular behaviour not specific to you. I hope that developers out of a sense of duty to the project stop thinking they can only work in labs, add tons of code then wait for others to address code upstream. This is not a technical issue it is a cultural one.

—
Reply to this email directly or view it on GitHub<https://github.com/jclouds/jclouds-labs-openstack/pull/169/files#r20232160>.