leannetworking / ovs-exporter Goto Github PK

The current ovs-exporter implementation only supports reading statistics from an OVS bridge via passive OpenFlow ports, which means that the OVS bridge has to listen to OpenFlow commands on an opened TCP port. That can cause security issues since by knowing the given port number, everyone can send OpenFlow commands to the bridges that can corrupt the forwarding behavior.

I suggest to add a different model where next to every OVS switch runs an ovs-exporter. That way the exporter can read the statistics from the OVS Unix Socket file, provided that it has read permission (the default file is at /var/run/openvswitch/db.sock). This would also help scenarios where multiple OVS bridges are defined on the same host (e.g. in OpenStack where bridges br-int, br-tun and br-ext might exist on the same host).

My suggestion is the following:

• Have a --local flag, which in case it's set read use the same param(target) from the URL but do not include the 'tcp:' before the bridge name, therefore it will read data via the Unix Socket file rather than a remote bridge.

Hi!

do you plan to release your exporter on dockerhub?

Cheers,
Jan