newton docs not consistent about [assignment] driver option

[Proskurin Kirill]

It's not clear what I should put into the:

[assignment]
driver = ???

in newton.

If I leave it undefined, I have deprecation warning, but docs tell me to leave it be:
http://docs.openstack.org/newton/config-reference/identity/samples/keystone.conf.html

and this one tells me to define it, since auto detection is deprecated.
http://docs.openstack.org/newton/config-reference/identity/config-options.html

[Lance Bragstad (lbragstad)]

As of Ocata, keystone only provides one driver for the assignment API [0]. I assume this is the deprecation warning you're seeing [1]. We've removed the logic to auto-detect the assignment driver when Ocata opened for development [2].

A work around for the deprecation warning and would be to set `keystone.conf [assignment] driver=sql` which is the default as of Ocata anyway.

Let us know if that helps and if you have any issues feel free to reopen the bug.

[0] https://github.com/openstack/keystone/blob/stable/newton/keystone/conf/assignment.py#L18-L28
[1] https://github.com/openstack/keystone/blob/stable/newton/keystone/assignment/core.py#L75-L81
[2] https://review.openstack.org/#/c/382428/4

[Steve Martinelli (stevemar)]

We post a sample configuration file with a lot of content over here: http://docs.openstack.org/developer/keystone/sample_config.html

Specifically, this paragraph will be helpful:

# Entry point for the assignment backend driver (where role assignments are
# stored) in the `keystone.assignment` namespace. Only a SQL driver is supplied
# by keystone itself. Unless you are writing proprietary drivers for keystone,
# you do not need to set this option. (string value)

Lance's comment is also correct.