-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request to support openvswitch and ovs-db-server on separate hosts #9
Comments
@xavpaice , there is a need to selectively disable the collection of certain things, with Add a map with features to the options passed to ovn_exporter/pkg/ovn_exporter/ovn_exporter.go Lines 278 to 280 in 3882334
Add the same map in the Exporter itself. ovn_exporter/pkg/ovn_exporter/ovn_exporter.go Lines 267 to 276 in 3882334
Then, modify the below function to disable certain collections. ovn_exporter/pkg/ovn_exporter/ovn_exporter.go Lines 409 to 410 in 3882334
|
Hi, any update here? |
I guess I'll work on this now, as this is a road blocker for me. |
while implementing this I noticed that https://github.com/greenpau/ovsdb/blob/ba2fa6bc5e69ee5511f72847d060e6709036ae0f/ovn.go#L113 connects to all DBs (south- and northbound) and ovs as well and returns an error if it's not successful. This is used in turn in ovn_exporter/pkg/ovn_exporter/ovn_exporter.go Line 321 in 79cb601
to establish a new client connection. I have implemented this as far as possible in ovn-exporter but I think we need to decouple the logic in ovsdb itself as well to make it really work. |
this is only partly working because ovsdb.Client currently is tightly coupled, making connections to NB, SB and ovs everytime. Related: greenpau#9 Signed-off-by: Sven Kieske <[email protected]>
this is only partly working because ovsdb.Client currently is tightly coupled, making connections to NB, SB and ovs everytime. Related: greenpau#9 Signed-off-by: Sven Kieske <[email protected]>
this is only partly working because ovsdb.Client currently is tightly coupled, making connections to NB, SB and ovs everytime. Related: greenpau#9 Signed-off-by: Sven Kieske <[email protected]>
In the OpenStack environments deploy by Canonical's Juju charms, there is typically a cluster of 'ovn-central' hosts which run ovn-northd, ovn-ovsdb-server-nb and ovn-ovsdb-server-sb. On the compute hosts themselves, we run ovn-controller and openvswitch.
When I run ovn-exporter on the compute hosts the collector reports:
Running on the 'ovn-central' hosts:
Metrics are available on each host, but with errors in the log that may need to be cleared.
Note also that
system_id="unknown"
on both hosts. On the ovn-central there's no OpenVswitch, but on the compute host the log reportsOpen_vSwitch: system-id is not 32 characters in length, but 37 source="ovn_exporter.go:428"
FYI, some paths used differ from default (set via CLI flags):
Paths on a compute host other than the above which don't exist, are default.
The text was updated successfully, but these errors were encountered: