Description of problem:
Trying to figure where is octavia.conf located, for example, when requiring to
configure ACTIVE_STANDBY mode - user might edit the wrong octavia.conf file.
The obvious option is to "Create or update /etc/octavia/octavia.conf "
However, the current working location is:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Login to Controller (where Octavia is deployed), and run as sudo:
[root@controller-0 ~]# find / -name octavia.conf
Found octavia.conf in (at least) 3 locations:
Please set octavia.conf file in a single location (preferably /etc/octavia/octavia.conf)
Containerized services use:
That being said, why do we also place it in /etc/octavia and /var/lib/config-data/octavia/etc/octavia?
The two paths are part of how the puppet generated configuration is written and managed for all services. docker-puppet.py uses some logic to only update files in /var/lib/config-data/puppet-generated that were changed in the last "puppet apply". This will be everything on initial deploy. It then does some magic involving md5 digest calculated on /var/lib/config-data/puppet-generated, paunch and the docker container to restart if something has changed.
Closing as NOTABUG, Octavia is identical to all other services in this regard. TripleO installs the octavia/nova/cinder/whatever .rpms on the overcloud nodes which results in /etc/octavia/*, and containerization results in the other two files. We may remove the rpm packages from the overcloud in future versions, but not in 13.