OPNFV Apex Release Notes¶

Contents:

1. OPNFV Release Notes for the Colorado release of OPNFV Apex deployment tool¶

Table of Contents

1.1. Abstract¶

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

1.2. License¶

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

1.3. Version history¶

Date	Ver.	Authors	Comment
2016-08-11	2.0.0	Dan Radez	Updates for Colorado
2015-09-17	1.0.0	Dan Radez	Rewritten for RDO Manager update

1.4. Important notes¶

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

1.5. Summary¶

Colorado 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 and OpenStack Liberty combined with OpenDaylight Beryllium. The system is deployed with OpenStack High Availability (HA) for most OpenStack services. OpenDaylight is deployed in non-HA form as HA support is not availble for OpenDaylight at the time of the Colorado release. Ceph storage is used as Cinder backend, and is the only supported storage for Colorado. Ceph is setup as 3 OSDs and 3 Monitors, one OSD+Mon per Controller node.

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

1.6. Release Data¶

Project	apex
Repo/tag	apex/colorado.1.0
Release designation	colorado.1.0
Release date	2016-09-14
Purpose of the delivery	OPNFV Colorado release

1.6.1. Version change¶

1.6.1.1. Module version changes¶

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

OpenStack (Mitaka release)
OpenDaylight (Beryllium release)
CentOS 7

1.6.1.2. Document version changes¶

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

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

1.6.1.3. Feature additions¶

JIRA REFERENCE	SLOGAN
JIRA: APEX-32	Build.sh integration of RDO Manager
JIRA: APEX-6	Deploy.sh integration of RDO Manager
JIRA: APEX-34	Migrate and update Release Documentation for Colorado

1.6.1.4. Bug corrections¶

JIRA TICKETS:

JIRA REFERENCE	SLOGAN

1.6.2. Deliverables¶

1.6.2.1. Software deliverables¶

Apex .iso file Apex overcloud .rpm (opnfv-apex) Apex undercloud .rpm (opnfv-apex-undercloud) Apex common .rpm (opnfv-apex-common) build.sh - Builds the above artifacts opnfv-deploy - Automatically deploys Target OPNFV System opnfv-clean - Automatically resets a Target OPNFV Deployment

1.6.2.2. Documentation deliverables¶

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

1.7. Known Limitations, Issues and Workarounds¶

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

1.7.2. Known issues¶