oslo-config-generator does not work with new oslo namespaces

[Jay Bryant]

We have discovered in Cinder that the config generator does not work with oslo_concurrency instead of oslo.concurrency:

jsbryant@ubuntu-14-04:~$ oslo-config-generator --namespace oslo_concurrency
[DEFAULT]
jsbryant@ubuntu-14-04:~$ oslo-config-generator --namespace oslo.concurrency
[DEFAULT]

[oslo_concurrency]

#
# From oslo.concurrency
#

# Enables or disables inter-process locks. (boolean value)
# Deprecated group/name - [DEFAULT]/disable_process_locking
#disable_process_locking = false

# Directory to use for lock files. For security, the specified
# directory should only be writable by the user running the processes
# that need locking. Defaults to environment variable OSLO_LOCK_PATH.
# If external locks are used, a lock path must be set. (string value)
# Deprecated group/name - [DEFAULT]/lock_path
#lock_path = <None>
jsbryant@ubuntu-14-04:~$

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/177957

[Doug Hellmann (doug-hellmann)]

The entry point namespace if the name of the library, not the name of the python package. So using "oslo.concurrency" is the correct form.

[Doug Hellmann (doug-hellmann)]

s/if the name/is the name/

[Jay Bryant (jsbryant)]

That seems kind-of inconsistent, but I won't worry about trying to fix oslo-config-generator if that is the way it is supposed to work.

[Doug Hellmann (doug-hellmann)]

The code isn't using that value to do a direct import, it's looking for an entry point name. We opted to name the entry points after the library so they would be consistently named.

[Sean McGinnis (sean-mcginnis)]

Jay, I believe this is fixed. Can you confirm?

[Jay Bryant (jsbryant)]

Yes, this looks like it is fixed. We are getting options from oslo_concurrency in the generated config file.