SFC Release Notes¶
1. Abstract¶
This document compiles the release notes for the Euphrates release of OPNFV SFC
2. Important notes¶
These notes provide release information for the use of SFC with the Apex installer and xci tools for the Euphrates release of OPNFV.
3. Summary¶
The goal of the SFC Euphrates release is to integrate the OpenDaylight SFC project into an OPNFV environment, with either the Apex installer or xci tools. In subsequent releases, we expect Compass4NFV to integrate the SFC scenarios too.
More information about OpenDaylight and SFC can be found here.
- OpenDaylight version “Nitrogen SR1”
- Service function chaining
- Documentation built by Jenkins
- Overall OPNFV documentation
- Design document
- User Guide
- Installation Instructions
- Release Notes (this document)
4. Release Data¶
| Project | sfc |
| Repo/tag | euphrates 1.0 |
| Release designation | Euphrates base release |
| Release date | 6th October 2017 |
| Purpose of the delivery | Integrate neutron networking-sfc and use the latest tacker code. Move to OpenStack ocata and ODL Nitrogen |
4.1. Version change¶
4.1.1. Module version changes¶
This release of OPNFV sfc is based on following upstream versions:
- OpenStack Ocata release
- OpenDaylight Nitrogen SR1 release
- Open vSwitch 2.6.1 with Yi Yang NSH patch
4.1.2. Document changes¶
This is the first tracked version of OPNFV SFC Euphrates. It comes with the following documentation:
- Design document
- User Guide
- Installation Instructions
- Release notes (This document)
4.2. Reason for version¶
4.2.1. Feature additions¶
- Integration with neutron networking-sfc
- Moved to latest tacker code
- Started using forwarding graphs as a way to configure SFC
- Created compatibility with latest functest (based on Alpine containers)
4.3. Deliverables¶
4.3.1. Software deliverables¶
No specific deliverables are created, as SFC is included with Apex.
4.3.2. Documentation deliverables¶
- Design document
- User Guide
- Installation Instructions
- Release notes (This document)
5. Known Limitations, Issues and Workarounds¶
5.1. System Limitations¶
The Euphrates 3.0 release has a few limitations:
1 - The testcase sfc_two_chains_SSH_and_HTTP is disabled in this release due to bugs in ODL, Tacker and networking-sfc:
https://bugs.opendaylight.org/show_bug.cgi?id=9221 https://bugs.launchpad.net/tacker/+bug/1719839 https://bugs.launchpad.net/tacker/+bug/1719876 https://bugs.launchpad.net/networking-sfc/+bug/1719835 https://bugs.launchpad.net/networking-sfc/+bug/1719883
2 - The topology CLIENT_SERVER_SAME_HOST does not work due to a bug in the vxlan_tool. This tool is part of the ODL-SFC repo and provides support for non-NSH-aware SFs:
https://bugs.opendaylight.org/show_bug.cgi?id=9219
3 - The topologies CLIENT_SERVER_DIFFERENT_HOST_SPLIT_VNF and CLIENT_SERVER_SAME_HOST_SPLIT_VNF do not work because of a ODL bug:
5.2. Known issues¶
1 - OpenDaylight SFC relies on a version of Open vSwitch (OVS) with Network Service Headers (NSH). A version of OVS with NSH currently exists, but it is in a branched version of OVS. Extensive upstream work has been done to merge the NSH patches into mainstream OVS, but the work is still not complete. More information about this can be found in the OPNFV SFC design document (link provided above).
2 - Due to a bug in tacker:
https://bugs.launchpad.net/tacker/+bug/1719841
it is not possible to run the SFC scenarios in openstack environments which require SSL connections to public endpoints and use self-signed certificates
5.3. Workarounds¶
There is a way to avoid the known issue number 2 when using xci. Once the deployment is successfully done, go to tacker server and modify line 242 of the file:
/openstack/venvs/tacker-15.1.7/lib/python2.7/site-packages/keystoneauth1/session.py
So that instead of having:
self.verify = verify
It has:
self.verify = False
Forcing tacker to not check the certificates
6. Test results¶
The Euphrates release of SFC has undergone QA test runs with Functest tests on the Apex installer and xci utility
