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

Bug 1457031

Summary: [Docs][RFE][Admin] Set up OVN provider in engine-setup
Product: Red Hat Enterprise Virtualization Manager Reporter: Tahlia Richardson <trichard>
Component: DocumentationAssignee: Tahlia Richardson <trichard>
Status: CLOSED CURRENTRELEASE QA Contact: Byron Gravenorst <bgraveno>
Severity: unspecified Docs Contact:
Priority: high    
Version: 4.2.0CC: bgraveno, dholler, lbopf, lsurette, mburman, mmirecki, rbalakri, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.2.0Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: docs-accepted
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-07 23:42:32 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:

Description Tahlia Richardson 2017-05-31 01:45:22 UTC 
In 4.2 we will be able to set up ovirt-provider-ovn in engine-setup.

Eng bug: https://bugzilla.redhat.com/show_bug.cgi?id=1436154

Current details (may change?): https://www.ovirt.org/blog/2016/11/ovirt-provider-ovn/#provider-setup-using-the-engine-setup-script

This will require not only an update to the Manager installation section, but also adding details in the OVN network provider section.

I worked on the original OVN network provider content here: https://bugzilla.redhat.com/show_bug.cgi?id=1420169

I'd also like to use this bug for other changes to the OVN provider functionality in 4.2, so I'm opening it now to capture any 4.2 feedback from the current round of tech review.
Comment 2 Lucy Bopf 2017-11-21 07:10:17 UTC 
Accepting into Beta program, and assigning to Tahlia for review.
Comment 6 Marcin Mirecki 2017-11-30 13:03:21 UTC 
Answers:
1.

The cluster default provider will be installed if no action is taken.
To install any other provider the user would have to uncheck the checkbox:
	"Use cluster's default network provider"
this will activate the:
	"External Network Provider"
dropdown and allow the user to choose another one 

2. 
Yes
If not selected, you will just create a regular ovirt network.
If the checkbox is not checked, the drop-down has no effect, even if it actually show anything (it's grayed out to indicate it's not relevant)

3.
You can use the one you already have
If you have installed it prior to 4.2, you will need to make a manual update to its "networking plugin" value (set it to "oVirt Network Provider for OVN").

It is likely for customers which have installed for trial in 4.1
Comment 12 Marcin Mirecki 2017-12-08 09:20:17 UTC 
Do you need any input for BZ#1522620?

The epoch issue is described in:
https://bugzilla.redhat.com/1505398
Comment 15 Byron Gravenorst 2017-12-12 03:50:50 UTC 
Reviewed and merged.
Comment 17 Tahlia Richardson 2018-01-07 23:42:32 UTC 
Now published at https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2-beta/html/administration_guide/chap-external_providers#Adding_OVN_as_an_External_Network_Provider