3) Use of /var/log/amphora-agent.log feels non-standard but I'm not finding proof to back that argument up. Packages generally put log files in /var/log/<package>/, ie. /var/log/octavia/amphora-agent.log. I did a quick search of debian standards and filesystem hierarchy standards but didn't find anything. I'm wondering if this should get changed upstream or if we could carry a patch in ubuntu to patch the code to use /var/log/octavia/amphora-agent.log (unless a patch upstream makes sense).
Hi Frode,
1) This should be a simple change in the package for the amphora-agent init to use /etc/octavia/ amphora- agent.conf.
2) These permissions have changed since this bug was reported. /etc/octavia now gets:
root@g1:~# ls -al /etc/octavia
total 36
drwxr-x--- 2 root octavia 4 Jul 17 17:51 .
drwxr-xr-x 100 root root 191 Jul 17 17:51 ..
-rw-r----- 1 root octavia 61659 Jul 17 17:51 octavia.conf
-rw-r----- 1 root octavia 7184 Jul 17 17:51 policy.json
So perhaps that is now solved?
3) Use of /var/log/ amphora- agent.log feels non-standard but I'm not finding proof to back that argument up. Packages generally put log files in /var/log/ <package> /, ie. /var/log/ octavia/ amphora- agent.log. I did a quick search of debian standards and filesystem hierarchy standards but didn't find anything. I'm wondering if this should get changed upstream or if we could carry a patch in ubuntu to patch the code to use /var/log/ octavia/ amphora- agent.log (unless a patch upstream makes sense).
Thanks,
Corey