4.1. OPNFV Release Notes for the Hunter release of OPNFV Apex deployment tool

4.1.1. Abstract

This document provides the release notes for Hunter release with the Apex deployment toolchain.

4.1.2. License

All Apex and “common” entities are protected by the Apache 2.0 License ( http://www.apache.org/licenses/ )

4.1.3. Important Notes

This is the OPNFV Hunter 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.

4.1.4. Summary

Hunter 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 Hunter. 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.

  • Documentation is built by Jenkins
  • .iso image is built by Jenkins
  • .rpm packages are built by Jenkins
  • Jenkins deploys a Hunter release with the Apex deployment toolchain bare metal, which includes 3 control+network nodes, and 2 compute nodes.

4.1.5. Release Data

Project apex
Repo/tag opnfv-7.1.0
Release designation 7.1.0
Release date 2018-12-14
Purpose of the delivery OPNFV Hunter release

4.1.5.1. Version change

4.1.5.1.1. Module version changes

This is the first tracked version of the Hunter release with the Apex deployment toolchain. It is based on following upstream versions:

  • OpenStack (Queens release)
  • OpenDaylight (Oxygen releases)
  • CentOS 7

4.1.5.1.2. Document Version Changes

This is the first tracked version of Hunter release with the Apex deployment toolchain. The following documentation is provided with this release:

  • OPNFV Installation instructions for the Hunter release with the Apex deployment toolchain - ver. 1.0.0
  • OPNFV Release Notes for the Hunter release with the Apex deployment toolchain - ver. 1.0.0 (this document)

4.1.5.2. Deliverables

4.1.5.2.1. Software Deliverables

  • Apex .rpm (python34-opnfv-apex)
  • build.py - Builds the above artifact
  • opnfv-deploy - Automatically deploys Target OPNFV System
  • opnfv-clean - Automatically resets a Target OPNFV Deployment
  • opnfv-util - Utility to connect to or debug Overcloud nodes + OpenDaylight

4.1.5.2.2. Documentation Deliverables

  • OPNFV Installation instructions for the Hunter release with the Apex deployment toolchain - ver. 7.1
  • OPNFV Release Notes for the Hunter release with the Apex deployment toolchain - ver. 7.1 (this document)

4.1.6. Known Limitations, Issues and Workarounds

4.1.6.1. System Limitations

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).

4.1.6.2. Known Issues

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

4.1.6.3. Workarounds

-

4.1.7. Test Result

Please reference Functest project documentation for test results with the Apex installer.

4.1.8. References

For more information on the OPNFV Hunter release, please see:

http://wiki.opnfv.org/releases/Hunter

Authors:Tim Rozet (trozet@redhat.com)
Authors:Dan Radez (dradez@redhat.com)
Version:7.1