1. OPNFV Fuel Release Notes¶
1.1. Abstract¶
This document provides the release notes for Hunter
release with the Fuel
deployment toolchain.
Starting with Gambia
release, both x86_64
and aarch64
architectures
are supported at the same time by the fuel
codebase.
1.2. License¶
All Fuel and “common” entities are protected by the Apache License 2.0.
1.3. Important Notes¶
This is the OPNFV Hunter
release that implements the deploy stage of the
OPNFV CI pipeline via Fuel.
Fuel is based on the MCP installation tool chain. More information available at Mirantis Cloud Platform Documentation.
The goal of the Hunter
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.
1.4. Summary¶
Hunter
release with the Fuel deployment toolchain will establish an OPNFV
target system on a Pharos compliant lab infrastructure. The current definition
of an OPNFV target system is OpenStack Queens combined with an SDN
controller, such as OpenDaylight. The system is deployed with OpenStack High
Availability (HA) for most OpenStack services.
Fuel also supports non-HA deployments, which deploys a single controller, one gateway node and a number of compute nodes.
Fuel supports x86_64
, aarch64
or mixed
architecture clusters.
Furthermore, Fuel is capable of deploying scenarios in a baremetal
,
virtual
or hybrid
fashion. virtual
deployments use multiple VMs on
the Jump Host and internal networking to simulate the baremetal
deployment.
For Hunter
, the typical use of Fuel as an OpenStack installer is
supplemented with OPNFV unique components such as:
- OpenDaylight
- Open Virtual Network (
OVN
) - Vector Packet Processing
As well as OPNFV-unique configurations of the Hardware and Software stack.
This Hunter
artifact provides Fuel as the deployment stage tool in the
OPNFV CI pipeline including:
- Automated (Jenkins, RTD) documentation build & publish (multiple documents);
- Automated (Jenkins) build & publish of Salt Master Docker image;
- Automated (Jenkins) deployment of
Hunter
running on baremetal or a nested hypervisor environment (KVM); - Automated (Jenkins) validation of the
Hunter
deployment
1.5. Release Data¶
Project | fuel |
Repo/tag | opnfv-8.1.0 |
Release designation | Hunter 8.1 |
Release date | June 24, 2019 |
Purpose of the delivery | OPNFV Hunter 8.1 release |
1.5.1. Version Change¶
1.5.1.1. Module Version Changes¶
This is the first tracked version of the Hunter
release with the Fuel
deployment toolchain. It is based on following upstream versions:
- MCP (
Q1`19
GA release) - OpenStack (
Rocky
release) - OpenDaylight (
Fluorine
release) - Ubuntu (
16.04
release)
1.5.1.2. Document Changes¶
This is the Hunter
8.1 release.
It comes with the following documentation:
- OPNFV Fuel Installation Instruction
- Release notes (This document)
- OPNFV Fuel Userguide
1.5.2. Reason for Version¶
1.5.2.1. Feature Additions¶
multiarch
cluster support;hybrid
cluster support;PDF
/IDF
support forvirtual
PODs;baremetal
support for noHA deployments;- containerized Salt Master;
OVN
scenarios;ODL
BGPVPN
scenario;IDF
support for configuring cluster-levelMTU
;
1.5.2.2. Bug Corrections¶
For an exhaustive list, see the OPNFV Fuel JIRA: Hunter 8.1 Bugs (fixed) filter.
1.5.2.3. Software Deliverables¶
- fuel git repository with multiarch (
x86_64
,aarch64
ormixed
) installer script files
1.5.2.4. Documentation Deliverables¶
- OPNFV Fuel Installation Instruction
- Release notes (This document)
- OPNFV Fuel Userguide
1.5.3. Scenario Matrix¶
baremetal |
virtual |
hybrid |
|
---|---|---|---|
os-nosdn-nofeature-noha | x86_64 |
||
os-nosdn-nofeature-ha | x86_64 ,
aarch64 |
||
os-nosdn-ovs-noha | x86_64 |
||
os-nosdn-ovs-ha | x86_64 ,
aarch64 |
||
os-odl-nofeature-noha | x86_64 |
||
os-odl-nofeature-ha | x86_64 ,
aarch64 |
||
os-odl-ovs-noha | x86_64 |
||
os-odl-ovs-ha | x86_64 |
||
os-odl-bgpvpn-noha | x86_64 |
||
os-odl-sfc-noha | x86_64 |
||
os-ovn-nofeature-noha | x86_64 |
||
os-ovn-nofeature-ha | aarch64 |
||
os-nosdn-fdio-noha | x86_64 ,
aarch64 |
1.6. Known Limitations, Issues and Workarounds¶
1.6.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
1.6.2. Known Issues¶
None
1.6.3. Workarounds¶
None
1.7. Test Results¶
The Hunter
8.1 release with the Fuel deployment tool has undergone QA test
runs, see separate test results.
1.8. References¶
For more information on the OPNFV Hunter
8.1 release, please see: