Table of Contents
This document provides the release notes for Colorado 2.0 release with the Apex deployment toolchain.
All Apex and "common" entities are protected by the Apache License ( http://www.apache.org/licenses/ )
Date | Ver. | Authors | Comment |
2016-10-26 | 2.2.0 | Tim Rozet | More updates for Colorado 2.0 |
2016-09-20 | 2.1.0 | Tim Rozet | More updates for Colorado |
2016-08-11 | 2.0.0 | Dan Radez | Updates for Colorado |
2015-09-17 | 1.0.0 | Dan Radez | Rewritten for RDO Manager update |
This is the OPNFV Colorado 2.0 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.
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 OpenStack Mitaka 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 only on the first controller (see HAIssues for known HA SDN issues). 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 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 | apex/colorado.2.0 |
Release designation | colorado.2.0 |
Release date | 2016-10-27 |
Purpose of the delivery | OPNFV Colorado 2.0 release |
This is the second tracked version of the Colorado release with the Apex deployment toolchain. It is based on following upstream versions:
The following documentation is provided with this release:
JIRA REFERENCE | SLOGAN |
JIRA: APEX-107 | OpenDaylight HA - OVSDB Clustering |
JIRA: APEX-108 | Migrate to OpenStack Mitaka |
JIRA: APEX-30 | Support VLAN tagged deployments |
JIRA: APEX-105 | Enable Huge Page Configuration Options |
JIRA: APEX-111 | Allow RAM to be specified for Control/Compute in Virtual Deployments |
JIRA: APEX-119 | Enable OVS DPDK as a deployment Scenario in Apex |
JIRA: APEX-126 | Tacker Service deployed by Apex |
JIRA: APEX-135 | Congress Service deployed by Apex |
JIRA: APEX-127 | Nova Instance CPU Pinning |
JIRA: APEX-130 | IPv6 Underlay Deployment |
JIRA: APEX-133 | FDIO with Honeycomb Agent |
JIRA: APEX-141 | Integrate VSPERF into Apex |
JIRA: APEX-172 | Enable ONOS SFC |
JIRA TICKETS:
JIRA REFERENCE | SLOGAN |
JIRA: APEX-86 | Need ability to specify number of compute nodes |
JIRA: APEX-180 | Baremetal deployment error: Failed to mount root partition /dev/sda on /mnt/rootfs |
JIRA: APEX-161 | Heat autoscaling stack creation fails for non-admin users |
JIRA: APEX-198 | Missing NAT iptables rule for public network in instack VM |
JIRA: APEX-147 | Installer doesn't generate/distribute SSH keys between compute nodes |
JIRA: APEX-109 | ONOS routes local subnet traffic to GW |
JIRA: APEX-146 | Swift service present in available endpoints |
JIRA: APEX-160 | Enable force_metadata to support subnets with VM as the router |
JIRA: APEX-114 | OpenDaylight GUI is not available |
JIRA: APEX-100 | DNS1 and DNS2 should be handled in nic bridging |
JIRA: APEX-100 | DNS1 and DNS2 should be handled in nic bridging |
JIRA: APEX-155 | NIC Metric value not used when bridging NICs |
JIRA: APEX-136 | 2 network deployment fails |
JIRA: APEX-89 | Deploy Ceph OSDs on compute nodes |
JIRA: APEX-137 | added arping ass dependency for ONOS deployments |
JIRA: APEX-121 | VM Storage deletion intermittently fails |
JIRA: APEX-182 | Nova services not correctly deployed |
JIRA: APEX-153 | brbm bridge not created in jumphost |
JIRA: APEX-274 | OVS DPDK scenario does not create vhost user ports |
JIRA: APEX-277 | ONOS fails to launch due to OVS and Kernel version mismatch |
JIRA: APEX-179 | DNS settings not working properly for baremetal deployments |
JIRA: APEX-203 | Swift proxy enabled and fails in noha deployment |
JIRA: APEX-230 | Tacker heat_uri setting is wrong |
JIRA: APEX-241 | Glance services are not running after reboot |
JIRA: APEX-265 | Metadata problems with os-odl_l2-sfc scenario |
JIRA: APEX-271 | L3 agent interface_driver set incorrectly for nosdn fdio noha |
JIRA: APEX-275 | Metadata fails in ODL Boron |
JIRA: APEX-278 | Duplicate neutron config class declaration for SDNVPN |
JIRA: APEX-281 | ONOS sometimes fails to provide addresses to instances |
JIRA: APEX-283 | Change networking-vpp ML2 driver to etcd |
JIRA: APEX-284 | vpp and hc versions for os-odl_l2 -fdio-noha scenario |
JIRA: APEX-285 | Remove vlan-strip-offload off config from os-odl_l2-fdio-noha scenario |
JIRA: APEX-286 | Make fdio repo an option in puppet- fdio |
JIRA: APEX-289 | Set undercloud VM to autostart for reboot |
JIRA: APEX-291 | link to apex installer missing on OPNFV download site |
JIRA: APEX-293 | tenant_nic is assumed to be a virtual name for nosdn fdio scenario |
JIRA: APEX-294 | dns server settings is ignored from network_settings.yaml |
JIRA: APEX-297 | Add details in "11.2 Creating a Node Inventory File" |
JIRA: APEX-326 | Consolidate SFC rpm into regular Apex rpm |
JIRA: APEX-331 | Conditionally install OVS NSH in ONOS Deployment |
JIRA: APEX-332 | IPv6 Scenario fails to deploy |
JIRA: APEX-333 | OVS DPDK does not work with UCS |
JIRA: APEX-334 | ONOS SFC not using SFC version of OVS |
JIRA: APEX-335 | Performance settings missing in os-odl_l2-fdio-ha.yaml |
JIRA: APEX-163 | Prefix to mask calculation doesn't work |
JIRA: APEX-266 | ntp server shoudl be in network settings |
JIRA: APEX-292 | unclear that ip ranges in network settings may not overlap |
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 jumphost, 24GB for virtual deployments (noHA).
JIRA TICKETS:
JIRA REFERENCE | SLOGAN |
JIRA: APEX-203 | Swift proxy enabled and fails in noha deployments |
JIRA: APEX-215 | Keystone services not configured and the error is silently ignored (VLAN Deployments) |
JIRA: APEX-208 | Need ability to specify which NIC to place VLAN on |
JIRA: APEX-254 | Add dynamic hugepages configuration |
JIRA: APEX-138 | Unclear error message when interface set to dhcp |
-
ODL routes local subnet traffic to GW
Openflow rules are populated very slowly
None
None
ONOS sometimes fails to provide addresses to instances
None
None
qemu doesn't receive connection on socket, vhost-user reconnect problem
APEX - Increase number of files MariaDB can open
Sometimes (especially in bulk crete/delete operations when multiple networks/ports are created within short time) OpenDaylight doesn't accept creation requests
After functest finishes there are two bds on computes and none on controller
qemu not configured with correct group:user
enable isolcpu on kernel and pin vpp to unused cpu for fdio scenarios
The Colorado release with the Apex deployment toolchain has undergone QA test runs with the OPNFV FuncTest project. The latest results per scenario can be found here for Colorado release.
For more information on the OPNFV Colorado release, please see:
http://wiki.opnfv.org/releases/Colorado
Authors: | Tim Rozet (trozet@redhat.com) |
---|---|
Authors: | Dan Radez (dradez@redhat.com) |
Version: | 2.2.0 |