Openstack rackspace compatibility

So, what specifically is broken so I can update the api usage?

I believe the problems manifest themselves when pointed at Rackspace Cloud.

Everything ;-)

So we need to maintain compatibility with diablo/hpcloud and essex. The
core of the changes are nova-volume and nova-network split out into
separate services (cinder & quantum). We'll need to do some more magic
around svc catalog introspection and dispatch of capabilities handling to
appropriate endpoint.

-k

On Thu, Sep 27, 2012 at 12:22 PM, Martin Packman <
<email address hidden>> wrote:

> So, what specifically is broken so I can update the api usage?

This is also what rackspace public cloud v2 offering is on. Their service
catalog is a bit complicated because it also has multiple nova endpoint
versions advertised in it (relating to the fact they really have more than
one implementation to choose from).

-k

On Tue, Oct 2, 2012 at 12:22 PM, Kapil Thangavelu <
<email address hidden>> wrote:

> Everything ;-)
>
> So we need to maintain compatibility with diablo/hpcloud and essex. The
> core of the changes are nova-volume and nova-network split out into
> separate services (cinder & quantum). We'll need to do some more magic
> around svc catalog introspection and dispatch of capabilities handling to
> appropriate endpoint.
>
> -k
>
> On Thu, Sep 27, 2012 at 12:22 PM, Martin Packman <
> <email address hidden>> wrote:
>
>> So, what specifically is broken so I can update the api usage?
>
>

I've tested trunk against Canonical's internal "canonistack" folsom region, as has Martin Packman, and it seems to work fine. This seems to be specifically about RAX.

I'll target this at 0.7 then, as I suspect it may be a lot of work, and not just a simple backportable fix.

Rackspace Cloud appears to use different tenants for cloud and object-store resources. This causes an error when juju tries to determine which services are available for the specified tenant, and only finds compute or object-store.