Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

question 1: user =swift. why swift? I got a user called swift in keystone, I got a user called swift in my Ubuntu OS

This is not the OS user. This is the user you create in Keystone configuration in the service tenant. The user is what Keystone uses to communicate with Swift.

question 2: admin_user=swift How is this swift different from the one above?

This is a proxy-server entry that establishes the Keystone user that will be used to communicate with the proxy services. Again, this is not the OS user. You can make this whatever you want, but it has to be consisted in the proxy-server.conf and in Keystone.

question 3: admin_tenant_name, should this one be "service" or "admin"? The tenant name is service in this case, assuming you are referring to the proxy-server.conf. The tenant is a container for services, objects, accounts, etc.

another thing is about version "v1". Can I use "v2"? But any way, I created the following endpoints for swi

V1 is the authentication method used by Swift. V2 is used by Keystone. You should be using v1 for service endpoint definitions in keystone config. This is what Keystone will use to communicate with Swift. The client will make the connection to v2, through Keystone. Then Keystone will initiate communicate with Swift on v1.

The followings are part of scripts to add zones. My question for this part are the port numbers 6000, 6001, and 6002 are the same for different storage nodes. are these right?

Yes, these ports should be the same for the different storage nodes. These the ports that the different elements of Swift use for communication.

One very useful switch to troubleshoot swift connection is the –debug switch. Use it with the swift stat command. It will give you the curl output of what the command is trying to do. Usually the error you are seeing is an indicator that you have mismatching port configurations between Keystone and Swift. For example, did you configure Keystone over SSL? If so, you should adjust your config and your tests to use HTTPS. If you are using port 8888 for swift in the keystone endpoint config and port 8080 in the proxy-server.conf you will get this error. Also try port 5000 for your Keystone URL. And try to curl to the URL directly to make sure you can establish communication. Finally, make sure our admin token is configured the same in Keystone as it is in proxy-server.conf. Then watch /var/log/messages on the proxy node for any errors and /var/log/keystone/keystone.log for keystone errors.