No, I have custom code running on Android, and I'm testing failures in
curl by copying the JSON and headers that are sent to a shell.
Nick
On Fri, May 25, 2012 at 9:54 PM, Jay Pipes jaypi...@gmail.com wrote:
On 05/25/2012 05:48 AM, Nick Lothian wrote:
In case anyone else is running into this
In case anyone else is running into this problem: I was authenticating
without using a tenant ID. This seems to work on some implementations
(TryStack, Rackspace), but not in others (DevStack, HPCloud).
On Thu, May 3, 2012 at 2:08 PM, Nick Lothian nick.loth...@gmail.com wrote:
I'm having some
On 05/25/2012 05:48 AM, Nick Lothian wrote:
In case anyone else is running into this problem: I was authenticating
without using a tenant ID. This seems to work on some implementations
(TryStack, Rackspace), but not in others (DevStack, HPCloud).
Are you sure that your OS_TENANT_NAME or
On Sat, May 5, 2012 at 12:57 AM, Dolph Mathews dolph.math...@gmail.com wrote:
As a user with the admin role on
35357: http://paste.openstack.org/raw/15160/
Thanks!
This works for me, mostly.
keystone --os_username=admin --os_password=password
--os_auth_url=http://192.168.1.50:35357/v2.0/
Replied inline.
On Thu, May 3, 2012 at 6:08 PM, Nick Lothian nick.loth...@gmail.com wrote:
(Replying to list this time... Is there a reason why the reply-to isn't
set to the list?!)
Is this really the case? Why does service-list require the admin port?
GET /services requires admin
On 05/03/2012 06:38 AM, Nick Lothian wrote:
I'm having some trouble using the Keystone API.
When I run
keystone --os_username=admin --os_password=password
--os_auth_url=http://192.168.1.50:5000/v2.0/ service-list
I get the following:
No handlers could be found for logger
My /etc/keystone/keystone.conf says:
[catalog]
template_file = /etc/keystone/default_catalog.templates
# dynamic, sql-based backend (supports API/CLI-based management commands)
driver = keystone.catalog.backends.templated.TemplatedCatalog
(This is the default from devstack).
I did look at that,
service-list calls the admin API (port 35357), but the auth_url you
provided was port 5000. I don't think the current keystoneclient is smart
enough to try and switch to the correct endpoint. If you have an admin
role, switching to port 35357 should work for you.
Additionally, you won't get a
Nick Lothian (nick.loth...@gmail.com) wrote:
My /etc/keystone/keystone.conf says:
[catalog]
template_file = /etc/keystone/default_catalog.templates
# dynamic, sql-based backend (supports API/CLI-based management commands)
driver = keystone.catalog.backends.templated.TemplatedCatalog
The service-list should give you a list of the services in the catalog, driven
by the template. What's in your catalog file at
/etc/keystone/default_catalog.templates? It sounds like it's empty - that's
what it's reading to report on services. You won't be able to use any of the
add/remove
(Replying to list this time... Is there a reason why the reply-to isn't set
to the list?!)
Is this really the case? Why does service-list require the admin port?
Running against TryStack (note that I don't supply a tenant):
$ curl -k -X 'POST' -v https://nova-api.trystack.org:5443/v2.0/tokens
/etc/keystone/default_catalog.templates looks like
https://github.com/openstack-dev/devstack/blob/master/files/default_catalog.templates
, with http://192.168.1.50 substituted for %SERVICE_HOST%
My curl call uses the username password, since it is to the /tokens URL:
curl -k -X 'POST' -v
I'm having some trouble using the Keystone API.
When I run
keystone --os_username=admin --os_password=password --os_auth_url=
http://192.168.1.50:5000/v2.0/ service-list
I get the following:
No handlers could be found for logger keystoneclient.v2_0.client
Unable to communicate with identity
13 matches
Mail list logo
