We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
OVN exporter has no access to the local databases OVSDB, OVN-NB-NB, OVN-SB-DB only over the socket remote and with the ovn parameters:
-database.northbound.socket.remote 192.168.0.x:6641 -database.southbound.socket.remote 192.168.0.x:6642 -database.vswitch.socket.remote 127.0.0.1:6640
there some parameters/files missing aspecial chassis-id PID Switchname, system-id or logs
how is the correct way to connect remote the Databases ?
the initial reason for this is that i try to integrate it in kolla-ansible, reference is the is the #10 the Docker Container is prepared here https://review.opendev.org/c/openstack/kolla/+/762986/ and the kolla-ansible integration is here https://review.opendev.org/c/openstack/kolla-ansible/+/855498
thanks a lot to take a look to this issue
The text was updated successfully, but these errors were encountered:
@berendt , @pawelmarkowski , @rnurgaliyev , would you be able to help with this issue?
Sorry, something went wrong.
No branches or pull requests
OVN exporter has no access to the local databases OVSDB, OVN-NB-NB, OVN-SB-DB
only over the socket remote and with the ovn parameters:
there some parameters/files missing aspecial
chassis-id
PID
Switchname,
system-id
or logs
how is the correct way to connect remote the Databases ?
the initial reason for this is that i try to integrate it in kolla-ansible, reference is the is the #10
the Docker Container is prepared here https://review.opendev.org/c/openstack/kolla/+/762986/
and the kolla-ansible integration is here https://review.opendev.org/c/openstack/kolla-ansible/+/855498
thanks a lot to take a look to this issue
The text was updated successfully, but these errors were encountered: