This document provides the release notes for Fraser release with the Apex deployment toolchain.
All Apex and "common" entities are protected by the Apache 2.0 License ( http://www.apache.org/licenses/ )
This is the OPNFV Fraser release that implements the deploy stage of the OPNFV CI pipeline via Apex.
Apex is based on RDO's Triple-O installation tool chain. More information at http://rdoproject.org
Carefully follow the installation-instructions which guide a user on how to deploy OPNFV using Apex installer.
Fraser release with the Apex deployment toolchain will establish an OPNFV target system on a Pharos compliant lab infrastructure. The current definition of an OPNFV target system is OpenStack Pike combined with an SDN controller, such as OpenDaylight. The system is deployed with OpenStack High Availability (HA) for most OpenStack services. SDN controllers are deployed on every controller unless deploying with one the HA FD.IO scenarios. Ceph storage is used as Cinder backend, and is the only supported storage for Fraser. Ceph is setup as 3 OSDs and 3 Monitors, one OSD+Mon per Controller node in an HA setup. Apex also supports non-HA deployments, which deploys a single controller and n number of compute nodes. Furthermore, Apex is capable of deploying scenarios in a bare metal or virtual fashion. Virtual deployments use multiple VMs on the Jump Host and internal networking to simulate the a bare metal deployment.
Project | apex |
Repo/tag | opnfv-6.0.0 |
Release designation | 6.0.0 |
Release date | 2018-04-30 |
Purpose of the delivery | OPNFV Fraser release |
This is the first tracked version of the Fraser release with the Apex deployment toolchain. It is based on following upstream versions:
This is the first tracked version of Fraser release with the Apex deployment toolchain. The following documentation is provided with this release:
Max number of blades: 1 Apex undercloud, 3 Controllers, 20 Compute blades
Min number of blades: 1 Apex undercloud, 1 Controller, 1 Compute blade
Storage: Ceph is the only supported storage configuration.
Min master requirements: At least 16GB of RAM for baremetal Jump Host, 24GB for virtual deployments (noHA).
JIRA TICKETS:
JIRA REFERENCE | SLOGAN |
JIRA: APEX-280 | Deleted network not cleaned up on controller |
JIRA: APEX-295 | Missing support for VLAN tenant networks |
JIRA: APEX-368 | Ceilometer stores samples and events forever |
JIRA: APEX-371 | Ceph partitions need to be prepared on deployment when using 2nd disk |
JIRA: APEX-375 | Default glance storage points to http,swift when ceph disabled |
JIRA: APEX-389 | Compute kernel parameters are used for all nodes |
JIRA: APEX-412 | Install failures with UEFI |
JIRA: APEX-425 | Need to tweak performance settings virtual DPDK scenarios |
-
Please reference Functest project documentation for test results with the Apex installer.
For more information on the OPNFV Fraser release, please see:
http://wiki.opnfv.org/releases/Fraser
Authors: | Tim Rozet (trozet@redhat.com) |
---|---|
Authors: | Dan Radez (dradez@redhat.com) |
Version: | 6.0 |