Ask Your Question

What is the impact of changing default_swift_cluster in proxy-server.conf?

asked 2011-06-30 10:49:41 -0500

irmatov gravatar image

During initial installation of Swift servers we had default_swift_cluster setting in proxy-server.conf set set to 'local#'.

Now, as we upload more than hundred thousand objects and slowly moving into production, we would like to change that setting to 'local#'. This is needed because when one remotely authenticates at the proxy, he sees X-Storage-Url as pointing to localhost.

What is the impact of changing default_swift_cluster? Do we need to perform additional actions?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2011-07-01 12:09:34 -0500

irmatov gravatar image

Thanks David Cole, that solved my question.

edit flag offensive delete link more

answered 2011-06-30 16:36:13 -0500

Hi Timur,

I came across this problem also... The X-Storage-Url is stored by swauth on a per-account basis when you first crate the account. Take a look at the following page: ( . You can use curl to update the X-Storage-Url that a user will be given when they authenticate. Here is an example of how I changed from a private IP to a public ( one :

$ curl -v -k -XPOST -D - ( -H "X-Auth-Admin-User: .super_admin" -H "X-Auth-Admin-Key: xxxxxxx" --data-binary '{ "storage": {"local": ""}'


edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2011-06-30 10:49:41 -0500

Seen: 24 times

Last updated: Jul 01 '11