`os_admin_project_domain_name` in configuration is not reflected

[Tetsuro Nakamura]

As it is noted in blazar sample configuration [1], we have the following options.
* os_admin_user_domain_name: A domain name the os_admin_username belongs to. (string value)
* os_admin_project_domain_name: A domain name the os_admin_project_name belongs to (string value)

[1] https://docs.openstack.org/blazar/latest/configuration/samples/blazar-conf.html

They are used for keystone authentication.
However, the ``os_admin_project_domain_name`` in the configuration file is not reflected.
This is because internally in the blazar server ``os_admin_user_domain_name`` is used for both *project* domain name and *user* domain name wrongly.

This doesn't affect　users who set neither of the values explicitly in the cofiguration file,
because the default values of the options are both set to "Default".
But this affect users who set either of the values explicitly.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/578029
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=3a7f6303aea22ab1c589329fa61701b5b09e0f34
Submitter: Zuul
Branch: master

commit 3a7f6303aea22ab1c589329fa61701b5b09e0f34
Author: Tetsuro Nakamura <email address hidden>
Date: Tue Jun 26 17:45:58 2018 +0900

    Correct the project domain option for authorization

    In blazar configuration, we have the following options:

    * os_admin_user_domain_name
    * os_admin_project_domain_name

    They are used for Keystone authentication, but
    ``os_admin_project_domain_name`` in the configuration file was not
    reflected in Blazar. This is because the Blazar service used
    ``os_admin_user_domain_name" for both *project* and *user* domain name.

    This patch fixes the bug and adds related tests.

    Change-Id: Ifbca9f622afba3aa9f41296fff2d34afce22da0a
    Closes-Bug: #1779660

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/blazar 2.0.0.0b3 development milestone.