Hi Nikolaus, thank you for your reply. > With the storage URL above, S3QL will attempt to connect to > https://eocloud.eu:5000/v2.0 (note the different version), which is > probably the source of your problems. > > I am not sure how v2.0 differs from v3, and how much work it would be to > support it. Experimentally, you could just try to change v2.0 to v3 in > src/s3ql/backends/swiftks.py and see what happens. > > In any case, it would be great if you could file a bug at > https://bitbucket.org/nikratio/s3ql/issues. At the very least, the > documentation should be updated to mention that only v2.0 is supported.
Apparently someone had already run into this (see https://bitbucket.org/nikratio/s3ql/issues/203/add-support-for-keystone-v3-for-swift) and from the thread it even seems someone was implementing v3 support. Maybe it led nowhere? The page at http://www.rath.org/s3ql-docs/backends.html#openstack-swift does refer to Keystone (v2), I assumed it would work with v3. I've asked my provider if they support other types/versions of authentication, that would also be a quick way forward for me. I can report a bug, but it's more a duplicate of 203... Thanks again. -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
