Bug 1111918

Summary: Docs: suggest a repository for installing hosts with an external network provider
Product: [oVirt] ovirt-engine Reporter: Moti Asayag <masayag>
Component: DocumentationAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: bugs <bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: adahms, bugs, gklein, rbalakri, srevivo, ylavi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-27 06:41:26 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 Moti Asayag 2014-06-22 06:26:57 UTC
Description of problem:
Compute nodes which are being added to ovirt-engine and set to be installed with an external network provider (OpenStack neutron), should contain a repository for
installing the openstack-neutron package and other required dependencies.

In ovirt-3.5, the neutron appliance is suggested, which is relied on OpenStack IceHouse neutron service. Therefore, the recommended packages for host installation with the neutron appliance as an external network providerare OpenStack IceHouse based [1]

[1] http://repos.fedorapeople.org/repos/openstack/openstack-icehouse/

The 'add/install host' guide should include this information, for the sake of users which intends to use the ovirt-neutron integration.

Comment 1 Moti Asayag 2014-06-23 12:28:57 UTC
Installing the rdo-release-icehouse-3.noarch.rpm will set the right repository for the destined OS:

yum install -y http://repos.fedorapeople.org/repos/openstack/openstack-icehouse/rdo-release-icehouse-3.noarch.rpm

Comment 2 Sandro Bonazzola 2014-10-17 12:14:39 UTC
Moving pending bugs not fixed in 3.5.0 to 3.5.1.

Comment 3 Sandro Bonazzola 2015-01-21 16:08:41 UTC
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority

Comment 4 Red Hat Bugzilla Rules Engine 2015-10-19 10:51:42 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Yaniv Lavi 2016-04-27 06:41:26 UTC
The integration changed and we no longer provide a appliance. Therefore this change is not needed.