Bug 1560870 - [Docs][Admin]Document how to configure a network for OVN tunnel
Summary: [Docs][Admin]Document how to configure a network for OVN tunnel
Keywords:
Status: CLOSED DUPLICATE of bug 1565963
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: rhev-docs@redhat.com
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-27 07:39 UTC by Avital Pinnick
Modified: 2019-05-07 12:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-13 12:34:07 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Avital Pinnick 2018-03-27 07:39:10 UTC
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>

Comment 1 Lucy Bopf 2018-04-13 05:32:51 UTC
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.

Comment 2 Avital Pinnick 2018-04-13 12:34:07 UTC
(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 ***


Note You need to log in before you can comment on or make changes to this bug.