> You should not run ovn-config manually, if the host bond0 has ovirtmgmt on
> top of it. That is all done by host deploy. The step might be needed if you
> want to have a tunnel on a different interface than ovirtmgmt is using.
Thanks for that. We performed a normal oVirt install and as a part of it the controller was installed in the manager. I can see the pre-req rpms and services are also installed in the hypervisors. So If I understood correctly you're saying that the tunnels and bridge would've been already created when we added the host?
If we just bring up the openvswitch and ovn-controller services we should be able to see the tunnels and bridge.
So there are a couple of things to keep in mind. During engine-setup you need to say yes for the OVN provider option.
The cluster with the hostat needs to have default network provider, which for "Default" cluster is configured automatically when the
OVN option is yes. With those conditions you don't need to start any service, everything should be running and the hosts installed
in the cluster will have tunnels ready on ovirtmgmt.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XOBGD7VYYBAW4MK2F3SSWHFHWAHGLUYW/
