1. Feature Overview: Support for the Amazon S3 API in Swift a) Name of feature: INTEL OSP 10 FEAT OPENDAYLIGHT OVS_DPDK NETVIRT-OVSDB SUPPORT b) Feature Description: Provide support for OpenDaylight, OVS-DPDK and OpenStack in the NetVirt/OVSDB scenario. This feature allows users to use OpenDaylight to set up virtualized networks for their tenants using OpenDaylight (& OVS_DPDK). 2. Feature Details: a) Architectures: 64-bit Intel E Power System/390 b) Bugzilla Dependencies: c) Drivers or hardware dependencies: d) Upstream acceptance information: e) External links: f) Severity (H,M,L): H High (required for Hardware Enablement) Medium Low g) Feature Needed by: 3. Business Justification: (Some partners prefer to include this information in Comment #1, so it can be made private if the bug is opened to other partners.) a) Why is this feature needed? b) What hardware does this enable? c) Is this hardware on-board in a system (eg, LOM) or an add-on card? d) Business impact? e) Other business drivers: 4. Primary contact at Red Hat, email, phone (chat) Phone Number 5. Primary contact at Partner, email, phone (chat) Rob Armstrong Robert.h.armstrong Phone Number 503-887-3687
There is some work going on in upstream to enable support for this feature in both ODL and networking-odl, but this is not a priority for us in Boron/RHOSP 10 as we are focusing on the switch towards the new NetVirt implementation. We prefer to get things working and stable with base OVS before we tackle the DPDK one. Once we get there we should really have a discussion with Intel on what is actually required here in terms of topologies/deployment options, encapsulation types, and other supportive features such security groups, IPAM, routing, etc.
The new target is to support OVS-DPDK with ODL in RHOSP 12 (Pike). Note also BZ 1414325 which tracks the required TripleO (OSP director) changes.
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:3462
Lukas, where do I see the doctext?