Mailing-List: contact user-help@jclouds.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@jclouds.apache.org
Received-SPF: pass (athena.apache.org: domain of everett.toews@rackspace.com
 designates 173.203.4.135 as permitted sender)
From: Everett Toews <everett.toews@RACKSPACE.COM>
To: "user@jclouds.apache.org" <user@jclouds.apache.org>
Subject: Re: OpenStack Keystone endpoints
Thread-Topic: OpenStack Keystone endpoints
Thread-Index: AQHP51WWIG1BLjK4/UWQWERVb8eGGZwvzqyA
Date: Tue, 14 Oct 2014 11:48:26 +0000
Message-ID: <156F0566-817B-4839-887A-B99ABE17EFA9@rackspace.com>
References: <543C8885.9000208@yahoo.com>
In-Reply-To: <543C8885.9000208@yahoo.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="windows-1251"
Content-ID: <636C023D0BDCEC4DAA71AD6D9E7C394C@RACKSPACE.CORP>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Yury,

I think you=92re referring to the OS-KSCATALOG admin extension

http://developer.openstack.org/api-ref-identity-v2.html#os-kscatalog-ext

If so, you=92re correct. It has not been implemented.

You=92re welcome to raise an issue for this at=20

https://issues.apache.org/jira/browse/JCLOUDS

Please include a description what it is, what it does, and what motivates t=
he addition of this API. This helps keep developers aware of things they ma=
y not be tracking closely and also helps us understand how jclouds is used.

Of course, if you have the time and desire to implemented this yourself, yo=
u can learn how at

https://wiki.apache.org/jclouds/How%20to%20Contribute

Thanks,
Everett


On Oct 13, 2014, at 9:20 PM, Yury Kats <yurykats@yahoo.com> wrote:

> Keystone server allows me to list/manage endpoints via /v2_0/endpoints UR=
L.
> I can't find corresponding APIs in jClouds. Have those not been implement=
ed or am I missing something?
>=20
> Example REST calls:
> $ keystone --debug --os-token ADMIN --os-endpoint http://127.0.0.1:4010/v=
2.0/  endpoint-list
> DEBUG:keystoneclient.session:REQ: curl -i -X GET http://127.0.0.1:4010/v2=
.0/endpoints -H "User-Agent: python-keystoneclient" -H "X-Auth-Token: ADMIN=
"
>=20
> $ keystone --debug --os-token ADMIN --os-endpoint http://127.0.0.1:4010/v=
2.0/  endpoint-create --service swift --publicurl qq
> DEBUG:keystoneclient.session:REQ: curl -i -X POST http://127.0.0.1:4010/v=
2.0/endpoints -H "User-Agent: python-keystoneclient" -H "Content-Type: appl=
ication/json" -H "X-Auth-Token: ADMIN" -d '{"endpoint": {"adminurl": null, =
"service_id": "e7573e3ef683477491766ff955221c94", "region": "regionOne", "i=
nternalurl": null, "publicurl": "qq"}}'
>=20
> $ keystone --debug --os-token ADMIN --os-endpoint http://127.0.0.1:4010/v=
2.0/  endpoint-delete 642503c6e32047b5a2f95c6558732a17
> DEBUG:keystoneclient.session:REQ: curl -i -X DELETE http://127.0.0.1:4010=
/v2.0/endpoints/642503c6e32047b5a2f95c6558732a17 -H "User-Agent: python-key=
stoneclient" -H "X-Auth-Token: ADMIN"
>=20
> Thanks,
> Yury