Naming
======
The naming scheme used for config merging in some of the services needs to be improved / made more consistent. We're coming across confusion from operators such as the following (paraphrased)
"I've added an ini file in /etc/kolla/config/cinder-api/cinder.conf on the system running kolla-ansible, and none of the parameters are showing up on my target system."
Answer here is to put it in either /etc/kolla/config/cinder.conf or /etc/kolla/config/cinder/cinder-api.conf. This is confusing, either both situations should be supported or documentation needs to be better.
Flexibility
===========
"I want to make changes to nova.conf on *api nodes only*. I put changes in /etc/kolla/config/nova/nova-api.conf but they're ending up on compute nodes"
There's currently no way of doing the above.
should only support one situation. The choice is bad.
> "I want to make changes to nova.conf on *api nodes only*. I put changes in /etc/kolla/ config/ nova/nova- api.conf but they're ending up on compute nodes"
the configure should be only copied to the node who need it, this is a bug[0].
the custom config file also support ansible template and this should be documented. like
cat <<EOF > /etc/kolla/ config/ nova.conf name='nova- api' %}
{% if service_
[DEFAULT]
debug=True
{% endif %}
[0] https:/ /bugs.launchpad .net/kolla/ +bug/1559122