Bug 1560870
| Summary: | [Docs][Admin]Document how to configure a network for OVN tunnel | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Avital Pinnick <apinnick> |
| Component: | Documentation | Assignee: | rhev-docs <rhev-docs> |
| Status: | CLOSED DUPLICATE | QA Contact: | rhev-docs <rhev-docs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.0 | CC: | apinnick, lbopf, lsurette, rbalakri, srevivo, ykaul |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-13 12:34:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Avital, I'm just looking at bug 1565963, and it appears that Marcin raised a bug to track the same thing you've noted here. Can you take a look and confirm? If they are the same request, let's close one as a duplicate. (In reply to Lucy Bopf from comment #1) > Avital, I'm just looking at bug 1565963, and it appears that Marcin raised a > bug to track the same thing you've noted here. Can you take a look and > confirm? If they are the same request, let's close one as a duplicate. Yes, they are the same. I would close this one and leave 1565963 open. It has more information. *** This bug has been marked as a duplicate of bug 1565963 *** |
From mmirecki: Out of the box, when a host is installed, it uses the "ovirtmgmt" network to set up OVN tunnels (connecting the OVN hosts). But, the user might want to use another network for this purpose. This can be done in mutliple ways: 1. Centrally from engine, using ansible: cd /use/share/ovirt-engine/playbooks Create a new playbook (for example change-ovn-tunnelling-network.yml): """ - name: Change OVN tunneling network hosts: ovirt_cluster_<cluster name> ### for example: hosts: ovirt_cluster_test-cluster ### vars: ovn_central: <IP of ovn central on the network> ovn_tunneling_interface: <name of ovirt network to be used for tunneling> roles: - ovirt-provider-ovn-driver """ Run the playbook: ansible-playbook --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa -i /usr/share/ovirt-engine-metrics/bin/ovirt-engine-hosts-ansible-inventory change-ovn-tunnelling-network.yml 2. On each host separately: Run the following vdsm-tool command: vdsm-tool ovn-config <ovn central ip> <tunneling ip or network name>