Read domain info from context when contacting nova
When we make a keystoneauth Session instance we are not looking at domain
info. This way we're always creating v2Password auth plugin, which will
obviously fail in an Identity v3-only scenario.
This patch makes domain information (i.e user_domain_id and project_domain_id)
be read from the context so that we can issue v3Password plugin as well.
Also, the logic behind auth plugin creation has been changed, as long as the
loading mechanism is designed to read options from config files, which is not
the case. Creating the plugin directly seems to fit better here.
This change is backwards compatible, since identity.Password can figure
out what Identity version is in use and will ignore domain info if v2.0
Reviewed: https:/ /review. openstack. org/337322 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=4fe3f4cfdaf 3ed08cd61ed18a8 e31ecf4b36f682
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4fe3f4cfdaf3ed0 8cd61ed18a8e31e cf4b36f682
Author: Clenimar Filemon <email address hidden>
Date: Mon Jul 4 13:40:59 2016 -0300
Read domain info from context when contacting nova
When we make a keystoneauth Session instance we are not looking at domain
info. This way we're always creating v2Password auth plugin, which will
obviously fail in an Identity v3-only scenario.
This patch makes domain information (i.e user_domain_id and project_domain_id)
be read from the context so that we can issue v3Password plugin as well.
Also, the logic behind auth plugin creation has been changed, as long as the
loading mechanism is designed to read options from config files, which is not
the case. Creating the plugin directly seems to fit better here.
This change is backwards compatible, since identity.Password can figure
out what Identity version is in use and will ignore domain info if v2.0
Change-Id: I687a73cce4230e 1d98d5c42fdc815 49d5bc6ab1a
Closes-Bug: #1599168