Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1623865

Summary: [Docs][RFE][Admin] Document new script to support long names when editing tunneling network for ovn controllers
Product: Red Hat Enterprise Virtualization Manager Reporter: Emma Heftman <eheftman>
Component: DocumentationAssignee: rhev-docs <rhev-docs>
Status: CLOSED CURRENTRELEASE QA Contact: Marcin Mirecki <mmirecki>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.2.6CC: danken, lsurette, mmirecki, pkovar, rdlugyhe, srevivo, tburke
Target Milestone: ovirt-4.3.4Keywords: Documentation, FutureFeature
Target Release: 4.3.0   
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: 2019-06-10 16:29:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Emma Heftman 2018-08-30 10:55:10 UTC 
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/#Adding_OVN_as_an_External_Network_Provider

This feature adds support for long network names
when modifying the tunneling network for ovn
controllers. 

The usage of the script: 

'ansible-playbook --key-file <pubkey> -i <inventory> --extra-vars " cluster_name=<cluster name> ovn_central=<ovn central ip> ovirt_network=<ovirt network name> ovn_tunneling_interface=<vdsm_network_name>"' 

Paramters:
  cluster_name - name of cluster on which to do the change
  ovirt_network - the ovirt network name (can be long name)
  ovn_tunneling_interface - specifies the vdsm network name (same as bridge name on vdsm)

Either 'ovirt_network' or 'ovn_tunneling_interface'
can be defined. The playbook will fail if both are
defined.

The 'inventory' paramter is the vm inventory for ovirt.
The following script can be used to retrieve this:
  /usr/share/ovirt-engine-metrics/bin/ovirt-engine-hosts-ansible-inventory

The user has to provider a key to long into the hosts.
The default key used by ovirt-engine is usually located in:
  /etc/pki/ovirt-engine/keys/engine_id_rsa



Example of usage:

using ovirt_network parameter for ovirt network "Long Network Name with ascii char ☺":

ansible-playbook --key-file /etc/pki/ovirt-engine/keys/engine_id_rsa -i /usr/share/ovirt-engine-metrics/bin/ovirt-engine-hosts-ansible-inventory --extra-vars " cluster_name=test-cluster ovn_central=192.168.200.2 ovirt_network=\"Long\ Network\ Name\ with\ \ascii\ char\ \☺\"" ovirt-provider-ovn-driver.yml

using ovn_tunneling_interface parameter for vdsm network "on703ea21ddbc34":

ansible-playbook --key-file /etc/pki/ovirt-engine/keys/engine_id_rsa -i /usr/share/ovirt-engine-metrics/bin/ovirt-engine-hosts-ansible-inventory --extra-vars " cluster_name=test-cluster ovn_central=192.168.200.2 ovn_tunneling_interface=on703ea21ddbc34" ovirt-provider-ovn-driver.yml







How rep
Comment 4 Sandro Bonazzola 2019-01-28 09:40:41 UTC 
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Comment 7 Marcin Mirecki 2019-04-03 12:51:55 UTC 
The doc says:
"You can use the `ovirt-provider-ovn-driver` Ansible playbook to create long network names when modifying the tunnel 
network for OVN controllers."

This is not true. The playbook can USE long names to modify the tunnel network, but the script is not meant to create long network names. The script does not modify the network name.
Comment 12 Petr Kovar 2019-06-10 16:29:32 UTC 
4.3 docs published.