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?
>
>
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?
>
>