Bug 1717485

Summary:	Missing SRIOV-OVN ymal file that enabling ovn with Neutron dhcp agent
Product:	Red Hat OpenStack	Reporter:	Kamil Sambor <ksambor>
Component:	openstack-tripleo-heat-templates	Assignee:	Kamil Sambor <ksambor>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	mburns, mschuppe, slinaber
Target Milestone:	z8	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.3.1-40.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-10 13:05:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kamil Sambor 2019-06-05 14:51:56 UTC

This bug was initially created as a copy of Bug #1699953

I am copying this bug because: 



Description of problem:
When we want to deploy OVN with SRIOV we need to install Neutron Dhcp Agent- OS::TripleO::Services::NeutronDhcpAgent 
so we need to add new THT file with all relevant parameter of OVN and enabling NeutronDHCP agent.

/usr/share/openstack-tripleo-heat-templates/docker/services/neutron-dhcp.yaml


We need to document it in out official docs. 

Today I am enabling it manully by adding   OS::TripleO::Services::NeutronDhcpAgent: /usr/share/openstack-tripleo-heat-templates/docker/services/neutron-dhcp.yaml  in network-environment.yaml

Version-Release number of selected component (if applicable):

OpenStack/14.0-RHEL-7/2019-04-12.1
(undercloud) [stack@undercloud-0 ~]$ rpm -qa | grep tripleo-heat-templates
openstack-tripleo-heat-templates-9.3.1-0.20190314162756.d0a6cb1.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 10 errata-xmlrpc 2019-07-10 13:05:31 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1738