You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem with this ovn_exporter is ".pid" and ".sock" files when they are inside of the container. For ".sock" it is easy to bind them to host I think but about ".pid" I don't have a solution because PID of inside Container is different from the host.
The text was updated successfully, but these errors were encountered:
AFAICT the pid files are only used to track the pid of the running processes, which IMO doesn't need to happen within this exporter and so possibly could be dropped. If you want to bindmount those instead, that should also work, the only information you could gather from this anyway is when a process was restarted. Oras a workaround, you could simply create a dummy file containing "0" and point to that as PID file.
Request for support Containerized OVN Services
When Openstack is deployed with Kolla-Ansible it uses Containers to deploy OVN and OVS binaries in different containers:
The problem with this ovn_exporter is ".pid" and ".sock" files when they are inside of the container. For ".sock" it is easy to bind them to host I think but about ".pid" I don't have a solution because PID of inside Container is different from the host.
The text was updated successfully, but these errors were encountered: