Hi,
I am using stable/essex release and have enabled Quantum with Keystone
authentication. I had to update the authN filter to use the
'keystone.middleware.auth_token:filter_factory' (instead of the default
'keystone.middleware.quantum_auth_token:filter_factory'). However, seems like
enabling Keystone with Quantum is not completely supported (since the
nova-manage network creation fails with authentication error). Looks like the
Quantum Manager in Nova does not support Keystone authentication.
Can someone please confirm whether enabling Quantum with Keystone is completely
supported.
Another observation is that the Nova Quantum client
(https://github.com/openstack/nova/blob/stable/essex/nova/network/quantum/client.py)
is using the Quantum API version 1.1, however, the CURRENT version in Quantum
API
(https://github.com/openstack/quantum/blob/stable/essex/quantum/api/versions.py)
is 1.0 (version 1.1 is PROPOSED). Shouldn't Nova Quantum client (of
stable/essex) be using version 1.0 instead?
Thanks & Regards,
Unmesh Gurjar | Lead Engineer | Vertex Software Private Ltd. | w.
+91.20.6604.1500 x 379 | m. +91.982.324.7631 |
unmesh.gur...@nttdata.com<mailto:unmesh.gur...@nttdata.com> | Follow us on
Twitter@NTTDATAAmericas
______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
