[...] > > 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. > [...]
That does not work since Keystone 2 and 3 are quite different. Keystone 2 has the concepts of "users" and "tenants" (one tenant can have multiple users) and Keystone 3 has "users" "projects" and "domains". (One domain can have multiple projects and multiple users. users can be part of a project) AFAIK, with Keystone 3 you also need to do a second request to the service catalog in order to actually get the Swift server URL. For Keystone 3 support in the swiftks backend having https://bitbucket.org/nikratio/s3ql/issues/202/allow-specifying-backend-options-in would probably be preferable. Then the swiftks backend could have options that would be more natural ("api-version", "user-name", "user-id", "tenant-name", "tenant-id", "project-name", "project-id", "domain-name", "domain-id", "password") -- 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.
