omeone when doing this step.
>
> Step 4: Implement the rest of the Identity V3 API.
>
> Does that sound OK to everyone?
>
> All the best,
> Darren
>
> -Original Message-
> From: Hague, Darren [mailto:[email protected]]
> Sent: 21 May 2015 13:03
> To: dev@jclouds.
ent the rest of the Identity V3 API.
Does that sound OK to everyone?
All the best,
Darren
-Original Message-
From: Hague, Darren [mailto:[email protected]]
Sent: 21 May 2015 13:03
To: [email protected]
Subject: RE: Implementing OpenStack Identity v3 API
" so the v3.0 codebase wo
ct: Re: Implementing OpenStack Identity v3 API
Hi Darren,
The Rackers or the Googlers can probably help more but to answer as best
I can--
As you probably know the usual jclouds pattern is to treat different
versions of an API as clean-room impls, so the v3.0 codebase wouldn't
share much if an
Hi Darren,
The Rackers or the Googlers can probably help more but to answer as best
I can--
As you probably know the usual jclouds pattern is to treat different
versions of an API as clean-room impls, so the v3.0 codebase wouldn't
share much if any code with the v2.0 codebase. If a user wan
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
