As a follow up on this question: How do I configure Keystone with Juju? Other questions on this topic like this ask what they need to be able to use Juju in their openstack installation. I need it just the other way around. I want to configure keystone for authentication against Active Directory, but the first thing in the keystone config file is:
# [ WARNING ]
# Configuration file maintained by Juju. Local changes may be overwritten.
This warning should be heeded, as the config changes are reset after a reboot of the container.
I searched the whole filesystem of the container for files related to keystone and juju, but the only file I could find (/var/lib/juju/agents/unit-keystone-0/charm/.juju-persistent-config
) that seems related is also reset after the reboot.
So, where can I configure juju to create a keystone config file with my additions for Active Directory?
juju set keystone "key=value"
and rebooting the container the values showed up in the keystone.conf as intended. Sadly, this only lead to the next problem, with Keystone being unable to start and reportingImportError: No module named ldap.filter
in the error log. – Gerald Schneider May 30 '16 at 08:22