FastDataStacks Release Notes¶
1. License¶
OPNFV Euphrates release notes for FastDataStacks
OPNFV Euphrates release notes for FastDataStacks are licensed under a Creative Commons Attribution 4.0 International License. You should have received a copy of the license along with this. If not, see <http://creativecommons.org/licenses/by/4.0/>.
2. OPNFV Euphrates release notes for FastDataStacks¶
2.1. Abstract¶
This document describes the release notes of FastDataStacks project.
2.2. OPNFV Euphrates Release¶
Any NFV solution stack is only as good as its foundation: The networking infrastructure. Key foundational assets for a NFV infrastructure are:
- The virtual forwarder: The virtual forwarder needs to be a feature-rich, high performance, highly scale virtual switch-router. It needs to leverage hardware accelerators when available and run in user space. In addition, it should be modular and easily extensible.
- Forwarder diversity: A solution stack should support a variety of forwarders, hardware forwarders (physical switches and routers) as well as software forwarders. This way virtual and physical forwarding domains can be seamlessly glued together.
- Policy driven connectivity: Business policies should determine the network level connectivity, rather than the other way around. Historically this has often been the other way around which quite often resulted in operational challenges.
In order to meet these desired qualities of an NFV infrastructure, the OPNFV FastDataStacks project was started in spring 2016, shortly after the FD.io Linux Foundation collaborative project was launched. FastDataStacks set out to compose a variety of scenarios using FD.io as a foundation to create an NFV solution that is both fast and flexible. OPNFV runs NFV for real – which also means that a virtual forwarder has to supply multi-million packet per second forwarding capability – even, and especially when integrated into a full stack solution. Simple software switches which are often found in cloud deployments with forwarding rates in the tens of thousands packets per second don’t offer appropriate performance for NFV deployments.
FastDataStacks scenarios are created with components from a set of open source projects. While performing the integration, FastDataStacks had to integrate and significantly evolve the functionality of different upstream components used, and evolve the automated installation and testing tools in OPNFV. FastDataStacks is a great example of OPNFV’s modus operandi: create, compose, deploy, test, iterate.
The key ingredient for all these scenarios is the data-plane forwarding and control infrastructure supplied by FD.io, i.e. VPP and Honeycomb along with OpenStack as the VM manager. In addition, OpenDaylight as a network controller plays a key role in many of the scenarios built by FastDataStacks.
2.3. Release Data¶
| Project | FastDataStacks |
| Repo/tag | fds/euphrates.1.0 |
| Release designation | 5.0.0 |
| Release date | 2017-10-20 |
| Purpose of the delivery | OPNFV Euphrates release |
2.4. FastDataStacks Scenarios in Euphrates¶
In release Euphrates, FastDataStacks releases the following scenarios:
OpenStack (with Neutron networking-vpp mechanism driver), VPPOpenStack (in a high-availability setup, with Neutron networking-vpp mechanism driver), VPPOpenStack, OpenDaylight (for Layer 2 and Layer 3 networking control), HoneyComb, VPPOpenStack (in a high-availability setup), OpenDaylight (for Layer 2 and Layer 3 networking control in clustered mode), HoneyComb, VPPOpenStack, OpenDaylight (for Layer 3 networking control; there is no Layer 2 configuration), HoneyComb, VPP
All of the scenarios are installed using the APEX installer.
2.5. Known Issues/Restrictions¶
2.5.1. Scenario os-nosdn-fdio-noha known issues in Euphrates¶
2.5.2. Scenario os-nosdn-fdio-ha known issues in Euphrates¶
- FDS-156: Race conditions for network-vif-plugged notification
- FDS-160: Vlan fix on controller
- FDS-371: Tempest_full_parallel failures due to DBDeadlock error
- FDS-399: Neutron ports are not marked ACTIVE
- FDS-400: Race condition between VPP ML2 agent and tempest code
- FDS-401: SimpleHealthCheck fails in snaps_smoke
- FDS-483: Live migration not supported
- APEX-468: Mariadb/mysqld fails to start post a reboot
- APEX-469: Undercloud iptables rules are messed up post a power outage
- FUNCTEST-841: Cloudify_ims testcase keeps timing out
- ORCEHSTRA-13: Internal Server Error/java.lang.OutOfMemoryError: Java heap space
2.5.3. Scenario os-odl-fdio-noha known issues in Euphrates¶
- FDS-476: Race conditions in GBP
- FDS-481: VPP hangs on blocking read from vhost user interface
- FDS-482: Live migration not supported
- FDS-484: snaps_smoke failures
- APEX-468: Mariadb/mysqld fails to start post a reboot
- APEX-469: Undercloud iptables rules are messed up post a power outage
- APEX-532: Add nat undercloud configuration for fdio scenarios
2.5.4. Scenario os-odl-fdio-ha known issues in Euphrates¶
- FDS-476: Race conditions in GBP
- FDS-481: VPP hangs on blocking read from vhost user interface
- FDS-482: Live migration not supported
- FDS-484: snaps_smoke failures
- APEX-468: Mariadb/mysqld fails to start post a reboot
- APEX-469: Undercloud iptables rules are messed up post a power outage
- APEX-532: Add nat undercloud configuration for fdio scenarios
2.5.5. Scenario os-odl-fdio_dvr-noha known issues in Euphrates¶
- FDS-481: VPP hangs on blocking read from vhost user interface
- FDS-482: Live migration not supported
- FDS-484: snaps_smoke failures
- FDS-485: LISP errors, improvements and cleanup in GBP
- APEX-468: Mariadb/mysqld fails to start post a reboot
- APEX-469: Undercloud iptables rules are messed up post a power outage
- APEX-532: Add nat undercloud configuration for fdio scenarios
- HC2VPP-249: Route can be created even if output interface does not exist
- HC2VPP-250: Cannot add EID if it’s already present in operational DS
Revision:
| Author: | Frank Brockners (fbrockne@cisco.com) |
|---|
Build date: October 19, 2017
