-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Identity v3 #109
Comments
Keystone isn't really used in the openstack plugin. There is a class for the client, but it isn't called anywhere. All of the connections are handled by the Neutron, Cinder, and Nova clients. They authenticate with Keystone on their own. Currently, I know that Nova does not support V3, and it seems that Neutron and Cinder also do not. |
Upstream is migrating towards using And as far as why using v3 is important: OpenStack Mitaka does not support v2 version anymore, so using v3 is a necessity. |
Guys, is this why I can no longer do anything with Datacentred? I've tried many combinations of keystone endpoint (/, /v2, /v3) with zero success. Every time a resource goes to be provisioned I get something along these lines (using v1.4 of the plugin):
|
@01000101 I don't have the config file with me at the moment, but I think you can work around that by adding /v2.0 to the end of the URL (not just /v2). |
That resolved issues w/ Keystone, but both Krzysztof and I are having a lot of OpenStack plugin issues now w/ Datacentred. |
This looks like it was updated in version 2.0 of the plugin: https://github.com/cloudify-cosmo/cloudify-openstack-plugin/blob/master/CHANGELOG.txt |
Hi!
Since the release of Openstack Havana the preferred version of Identity to use is v3. Some cloud providers have now migrated to only supporting v3 for token generation to get support for domains.
Currently the Cloudify Openstack plugin does not work with providers that require support for Identity v3.
As far as I can see, you're already using keystoneclient.v3.client, so it should basically amount to adding the correct arguments.
Would it be possible to add support for Identity v3 in this project as well?
The text was updated successfully, but these errors were encountered: