Seems we got ahead of ourselves in commit 25a2ea7f and broke the S3 api by changing the swift3 middleware config to something that is not supported until the Newton version (1.11) of swift-s3-plugin. In the swift-proxy charm for >= Kilo we currently have:
[filter:swift3]
use = egg:swift3#swift3
--------------------
but that is broken in two ways; firstly swift3 (swift-s3-plugin) didnt switch to use auth_uri until 1.11 which is not available until Newton and secondly, when you switch to 1.11 you then need to change the s3token config to:
--------------------
[filter:s3token]
use = egg:swift3#s3token
auth_uri = http://127.0.0.1:35357/
[filter:swift3]
use = egg:swift3#swift3
--------------------
Seems we got ahead of ourselves in commit 25a2ea7f and broke the S3 api by changing the swift3 middleware config to something that is not supported until the Newton version (1.11) of swift-s3-plugin. In the swift-proxy charm for >= Kilo we currently have:
------- ------- ------ factory = keystonemiddlew are.s3_ token:filter_ factory
[filter:s3token]
paste.filter_
auth_uri = {{ auth_protocol }}://{{ keystone_host }}:{{ auth_port }}
[filter:swift3] ------- ------
use = egg:swift3#swift3
-------
but that is broken in two ways; firstly swift3 (swift-s3-plugin) didnt switch to use auth_uri until 1.11 which is not available until Newton and secondly, when you switch to 1.11 you then need to change the s3token config to:
------- ------- ------ 127.0.0. 1:35357/
[filter:s3token]
use = egg:swift3#s3token
auth_uri = http://
[filter:swift3] ------- ------
use = egg:swift3#swift3
-------