Release notes for Fuel@OPNFV¶
1. Abstract¶
This document compiles the release notes for the Euphrates release of OPNFV when using Fuel as a deployment tool. This is an unified documentation for both x86_64 and aarch64 architectures. All information is common for both architectures except when explicitly stated.
2. Important Notes¶
These notes provides release information for the use of Fuel as deployment tool for the Euphrates release of OPNFV.
The goal of the Euphrates release and this Fuel-based deployment process is to establish a lab ready platform accelerating further development of the OPNFV infrastructure.
Carefully follow the installation-instructions.
3. Summary¶
For Euphrates, the typical use of Fuel as an OpenStack installer is supplemented with OPNFV unique components such as:
As well as OPNFV-unique configurations of the Hardware and Software stack.
This Euphrates artifact provides Fuel as the deployment stage tool in the OPNFV CI pipeline including:
- Documentation built by Jenkins
- overall OPNFV documentation
- this document (release notes)
- installation instructions
- Automated deployment of Euphrates with running on bare metal or a nested hypervisor environment (KVM)
- Automated validation of the Euphrates deployment
4. Release Data¶
| Project | fuel/armband |
| Repo/tag | opnfv-5.0.2 |
| Release designation | Euphrates 5.0 |
| Release date | October 20 2017 |
| Purpose of the delivery | Euphrates alignment to Released MCP 1.0 baseline + features and bug-fixes for the following feaures:
|
4.1. Version Change¶
4.1.1. Module Version Changes¶
This is the Euphrates 5.0 release. It is based on following upstream versions:
- MCP 1.0 Base Release
- OpenStack Ocata Release
- OpenDaylight
4.1.2. Document Changes¶
This is the Euphrates 5.0 release. It comes with the following documentation:
- Installation instructions
- Release notes (This document)
4.2. Reason for Version¶
4.2.1. Feature Additions¶
JIRA TICKETS: Euphrates 5.0 new features
4.2.2. Bug Corrections¶
JIRA TICKETS:
(Also See respective Integrated feature project’s bug tracking)
5. Known Limitations, Issues and Workarounds¶
5.1. System Limitations¶
- Max number of blades: 1 Jumpserver, 3 Controllers, 20 Compute blades
- Min number of blades: 1 Jumpserver
- Storage: Cinder is the only supported storage configuration
- Max number of networks: 65k
6. Test Results¶
The Euphrates 5.0 release with the Fuel deployment tool has undergone QA test runs, see separate test results.
