dulwich
dulwich copied to clipboard
jelmer
Swift backend support for keystone v3
Hello,
I see that it can work with keystone v2 but does it support keystone v3?
Sincerely, Alexandr
Hi,
On Thu, Nov 10, 2016 at 02:22:12AM -0800, Alexandr Porunov wrote:
I see that it can work with keystone v2 but does it support keystone v3? @morucci can probably answer that question as well as tell you more about the current state of it.
Hi, I don't think so, the payload to get a token seems to have changed between keystone v2 and v3. Basically a new swift_auth_v3 method would be needed. The Swift support in Dulwich has been maintained due to the coverage of the unittests but honestly I haven't had the time to try time to time this feature against a real Swift cluster so using it will maybe raise issues. I don't think the Swift API has evolved so much in a way that break to much the feature. I can, if this feature shown some interest, think how to run functional test against a real keystone + swift continuously.
I think this feature is awesome. I haven't found solutions like this. It let us use git functions with automatic failover, high availability, load balance and so on. But keystone v2 is is deprecated now. They strongly recommend to use keystone v3. It would be great if this feature supports keystone v3.
As far as I know this feature as not been used in production. I just validated it by doing lot of semi automatic tests against a real swift cluster but I guess it needs some consolidation. But the authentication phase is just a detail IMO and you should try it with the actual supported auth before trying to support v3 if possible.
(SwiftStack maintains a vagrant box for a allinone Swift instance you can I think configure to enable the auth v1 : https://github.com/swiftstack/vagrant-swift-all-in-one)
2016-11-10 16:31 GMT+01:00 Alexandr Porunov [email protected]:
I think this feature is awesome. I haven't found solutions like this. It let us use git functions with automatic failover, high availability, load balance and so on. But keystone v2 is is deprecated now. They strongly recommend to use keystone v3. It would be great if this feature supports keystone v3.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jelmer/dulwich/issues/464#issuecomment-259720282, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFKZ4SSaMVuk7WYDI2yTg5VE7WtYmYVks5q8zjcgaJpZM4KufsP .
Hello, no I'm not working on this.
2018-04-09 4:17 GMT+02:00 Jelmer Vernooij [email protected]:
Are you still working on this?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dulwich/dulwich/issues/464#issuecomment-379607978, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFKZ9f07Ai7XyFGilr__zdHIApGeKs4ks5tmsS4gaJpZM4KufsP .