# amxmachine's profile - activity

2014-06-19 14:26:27 -0600 answered a question swift keystone configuration no handlers 401 failure

While bootstrapping the identity v2 (did not realize v3 is out) I have to type in commands as follows to get them to work

keystone --token secrettoken --endpoint http://127.0.0.1:35357/v2.0/

this is because my environment variables are screwy. even, 1. using the export command and 2. sourcing a .sh file did not fix my issues. I probably misconfigured something along the lines (the tenantName I posted below seemed out of place), but I am just going to reinstall and try v3 since its dev.

2014-06-19 14:16:25 -0600 asked a question How to setup multiple authorization nodes (keystone HA)?

I am in charge of supplying a service utilizing swift, keystone, and a custom front end that needs to have High-Availability and security as its main function. This is my first development project of any kind so I may be missing some glaringly obvious things. I want to build a setup that spans 4 geographical locations, that will scale from there if need be. So far my plan is two of the nodes will include object storage and the other two nodes will supply authorization, identity v3, ssl termination, and load balancing services. I understand how to implement storage and proxy services, and I have all the goodies for a high-availability storage cluster; however, it is the load balancing and identity that I am stuck at. My questions are:

1. is there a built in function for keystone to sync between two nodes? I have failed to find it anywhere
2. is it even safe for me to terminate ssl at the auth node considering they will be colocated in different geographical regions?
3. is there a better solution that does not leave me with an authorization bottleneck?
2014-06-17 13:28:22 -0600 commented answer swift keystone configuration no handlers 401 failure

I got around to running debug on it and this is what I get minus the traceback.

# keystone --debug user-create --name swift --tenant_id swift --pass secretpassword --email me@secretdomain.com

connect: (localhost, 5000) send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: localhost:5000\r\nContent-Length: 113 \r\ncontent-type: application/json\r\naccept-encoding: gzip, deflate\r\nuser-age nt: python-keystoneclient\r\n\r\n{"auth": {"tenantName": "johnswift", "passwor dCredentials": {"username": "keystonehost admin account", "password": "keystone host admin password"}}}' reply: 'HTTP/1.1 401 Not Authorized\r\n' header: Content-Type: application/json header: Vary: X-Auth-Token header: Date: Tue, 17 Jun 2014 21:06:07 GMT header: Transfer-Encoding: chunked No handlers could be found for logger "keystoneclient.client" send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: localhost:5000\r\nContent-Length: 113 \r\ncontent-type: application/json\r\naccept-encoding: gzip, deflate\r\nuser-age nt: python-keystoneclient\r\n\r\n{"auth": {"tenantName": "johnswift ...

2014-06-16 16:08:53 -0600 asked a question swift keystone configuration no handlers 401 failure

Hi,

I am setting up a solo swift environment using keystone authentication. after following these instructions... http://docs.openstack.org/icehouse/install-guide/install/apt/content/keystone-install.html (http://docs.openstack.org/icehouse/in...)

I came into an issue at the beginning of this guide. http://docs.openstack.org/icehouse/install-guide/install/apt/content/general-installation-steps-swift.html (http://docs.openstack.org/icehouse/in...)

for this step: $keystone user-create --name=swift --pass=** --email=@**.com I get this error: No handlers could be found for logger "keystoneclient.client" Invalid user / password (HTTP 401) I found one answer on the web saying I need to make sure my$SERVICE_TOKEN is the same as the admin token I generated, but I cannot find this \$SERVICE_TOKEN variable anywhere. am I looking in the right direction?