Bug 1384861

Summary: Add 3 composable roles for NFV: OVS (default), OVS-DPDK, and SR-IOV
Product: Red Hat OpenStack Reporter: Franck Baudin <fbaudin>
Component: openstack-tripleo-heat-templatesAssignee: Yariv <yrachman>
Status: CLOSED ERRATA QA Contact: Yariv <yrachman>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: atelang, dcadzow, fbaudin, lbopf, mburns, nlevinki, oblaut, rhel-osp-director-maint, sclewis, vchundur, yrachman, zgreenbe
Target Milestone: Upstream M2Keywords: FutureFeature, TestOnly, Triaged, ZStream
Target Release: 11.0 (Ocata)Flags: vchundur: automate_bug+
vchundur: needinfo+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
This effort to establish these roles packing the respective services and test connectivity. As an exit criteria we would give clear steps (perhaps, update templates as required) and pass this information to the documentation team.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-17 19:34:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1424611    

Description Franck Baudin 2016-10-14 09:49:48 UTC
Description of problem:

NFV deployment requires various compute node roles:
 1/ default, as for RHOSP9, based on regular OVS
 2/ SR-IOV, enabling SR-IOV and regular OVS
 3/ OVS-DPDK, enabling exclusively OVS-DPDK and not the regular OVS neither SR-IOV

Comment 1 Franck Baudin 2016-11-14 15:00:38 UTC
This is a documentation and QE BZ only, no enhancement are required.

Comment 10 Derek 2017-04-12 12:58:26 UTC
Removing [Docs] from the summary so that we can distinguish between the bugs raised by the tech team and those raised by the doc team to track the doc work. (doc bug for this one is BZ1424611)

Comment 14 errata-xmlrpc 2017-05-17 19:34:54 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/RHEA-2017:1245