diff options
Diffstat (limited to 'docs')
23 files changed, 663 insertions, 247 deletions
diff --git a/docs/release/installation/abstract.rst b/docs/release/installation/abstract.rst index 70814cea..b2d92a23 100644 --- a/docs/release/installation/abstract.rst +++ b/docs/release/installation/abstract.rst @@ -1,16 +1,16 @@ Abstract ======== -This document describes how to install the Colorado release of OPNFV when +This document describes how to install the Danube release of OPNFV when using Apex as a deployment tool covering it's limitations, dependencies and required system resources. License ======= -Colorado release of OPNFV when using Apex as a deployment tool Docs +Danube release of OPNFV when using Apex as a deployment tool Docs (c) by Tim Rozet (Red Hat) and Dan Radez (Red Hat) -Colorado release of OPNFV when using Apex as a deployment tool Docs +Danube release of OPNFV when using Apex as a deployment tool Docs are licensed under a Creative Commons Attribution 4.0 International License. You should have received a copy of the license along with this. If not, see <http://creativecommons.org/licenses/by/4.0/>. diff --git a/docs/release/installation/architecture.rst b/docs/release/installation/architecture.rst index 38806391..ae634cc4 100644 --- a/docs/release/installation/architecture.rst +++ b/docs/release/installation/architecture.rst @@ -116,28 +116,56 @@ description. Also, please refer to release-notes for information about known issues per scenario. The following scenarios correspond to a supported <Scenario>.yaml deploy settings file: -+-------------------------+------------+-----------------+ -| **Scenario** | **Owner** | **Supported** | -+-------------------------+------------+-----------------+ -| os-nosdn-nofeature-ha | Apex | Yes | -+-------------------------+------------+-----------------+ -| os-nosdn-nofeature-noha | Apex | Yes | -+-------------------------+------------+-----------------+ -| os-nosdn-ovs-noha | OVS for NFV| Yes | -+-------------------------+------------+-----------------+ -| os-nosdn-fdio-noha | FDS | Yes | -+-------------------------+------------+-----------------+ -| os-odl_l2-nofeature-ha | Apex | Yes | -+-------------------------+------------+-----------------+ -| os-odl_l3-nofeature-ha | Apex | Yes | -+-------------------------+------------+-----------------+ -| os-odl_l2-sfc-noha | SFC | Yes | -+-------------------------+------------+-----------------+ -| os-odl-bgpvpn-ha | SDNVPN | No | -+-------------------------+------------+-----------------+ -| os-odl_l2-fdio-noha | FDS | Yes | -+-------------------------+------------+-----------------+ -| os-onos-nofeature-ha | ONOSFW | Yes | -+-------------------------+------------+-----------------+ -| os-onos-sfc-ha | ONOSFW | Yes | -+-------------------------+------------+-----------------+ ++-------------------------+-------------+---------------+ +| **Scenario** | **Owner** | **Supported** | ++-------------------------+-------------+---------------+ +| os-nosdn-nofeature-ha | Apex | Yes | ++-------------------------+-------------+---------------+ +| os-nosdn-nofeature-noha | Apex | Yes | ++-------------------------+-------------+---------------+ +| os-nosdn-ovs-ha | OVS for NFV | Yes | ++-------------------------+-------------+---------------+ +| os-nosdn-ovs-noha | OVS for NFV | Yes | ++-------------------------+-------------+---------------+ +| os-nosdn-fdio-ha | FDS | Yes | ++-------------------------+-------------+---------------+ +| os-nosdn-fdio-noha | FDS | Yes | ++-------------------------+-------------+---------------+ +| os-nosdn-kvm-ha | KVM for NFV | Yes | ++-------------------------+-------------+---------------+ +| os-nosdn-kvm-noha | KVM for NFV | Yes | ++-------------------------+-------------+---------------+ +| os-nosdn-performance-ha | Apex | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l3-nofeature-ha | Apex | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l3-nofeature-noha| Apex | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l3-ovs-ha | OVS for NFV | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l3-ovs-noha | OVS for NFV | Yes | ++-------------------------+-------------+---------------+ +| os-odl-bgpvpn-ha | SDNVPN | Yes | ++-------------------------+-------------+---------------+ +| os-odl-bgpvpn-noha | SDNVPN | Yes | ++-------------------------+-------------+---------------+ +| os-odl-gluon-noha | GluOn | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l3-csit-noha | Apex | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l3-fdio-ha | FDS | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l3-fdio-noha | FDS | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l2-fdio-ha | FDS | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l2-fdio-noha | FDS | Yes | ++-------------------------+-------------+---------------+ +| os-odl_l2-sfc-noha | SFC | No | ++-------------------------+-------------+---------------+ +| os-onos-nofeature-ha | ONOSFW | No | ++-------------------------+-------------+---------------+ +| os-onos-sfc-ha | ONOSFW | No | ++-------------------------+-------------+---------------+ +| os-ovn-nofeature-noha | Apex | Yes | ++-------------------------+-------------+---------------+ diff --git a/docs/release/installation/index.rst b/docs/release/installation/index.rst index c251fd5a..615aa7e5 100644 --- a/docs/release/installation/index.rst +++ b/docs/release/installation/index.rst @@ -22,7 +22,7 @@ Contents: :Authors: Tim Rozet (trozet@redhat.com) :Authors: Dan Radez (dradez@redhat.com) -:Version: 3.0 +:Version: 4.0 Indices and tables ================== diff --git a/docs/release/installation/introduction.rst b/docs/release/installation/introduction.rst index cc489917..18267848 100644 --- a/docs/release/installation/introduction.rst +++ b/docs/release/installation/introduction.rst @@ -1,7 +1,7 @@ Introduction ============ -This document describes the steps to install an OPNFV Colorado reference +This document describes the steps to install an OPNFV Danube reference platform, as defined by the Genesis Project using the Apex installer. The audience is assumed to have a good background in networking @@ -19,7 +19,7 @@ deployment tool chain. The Apex deployment artifacts contain the necessary tools to deploy and configure an OPNFV target system using the Apex deployment toolchain. These artifacts offer the choice of using the Apex bootable ISO -(``opnfv-apex-colorado.iso``) to both install CentOS 7 and the +(``opnfv-apex-danube.iso``) to both install CentOS 7 and the necessary materials to deploy or the Apex RPMs (``opnfv-apex*.rpm``), and their associated dependencies, which expects installation to a CentOS 7 libvirt enabled host. The RPM contains a collection of diff --git a/docs/release/installation/references.rst b/docs/release/installation/references.rst index a63a8421..b777bac5 100644 --- a/docs/release/installation/references.rst +++ b/docs/release/installation/references.rst @@ -14,16 +14,14 @@ OPNFV `OPNFV Home Page <www.opnfv.org>`_ -`OPNFV Genesis project page <https://wiki.opnfv.org/get_started>`_ - `OPNFV Apex project page <https://wiki.opnfv.org/apex>`_ -`OPNFV Apex release notes <http://artifacts.opnfv.org/apex/colorado/docs/releasenotes/release-notes.html#references>`_ +:ref:`OPNFV Apex Release Notes <apex-releasenotes>` OpenStack --------- -`OpenStack Mitaka Release artifacts <http://www.openstack.org/software/mitaka>`_ +`OpenStack Newton Release artifacts <http://www.openstack.org/software/newton>`_ `OpenStack documentation <http://docs.openstack.org>`_ diff --git a/docs/release/installation/requirements.rst b/docs/release/installation/requirements.rst index 507b671e..62c9963e 100644 --- a/docs/release/installation/requirements.rst +++ b/docs/release/installation/requirements.rst @@ -15,7 +15,7 @@ The Jumphost requirements are outlined below: 4. minimum 1 networks and maximum 5 networks, multiple NIC and/or VLAN combinations are supported. This is virtualized for a VM deployment. -5. The Colorado Apex RPMs and their dependencies. +5. The Danube Apex RPMs and their dependencies. 6. 16 GB of RAM for a bare metal deployment, 64 GB of RAM for a VM deployment. diff --git a/docs/release/installation/troubleshooting.rst b/docs/release/installation/troubleshooting.rst index ed0d1ff6..efff9796 100644 --- a/docs/release/installation/troubleshooting.rst +++ b/docs/release/installation/troubleshooting.rst @@ -85,18 +85,11 @@ executed. However, some other cases it could be worth it to try to debug it. OpenDaylight Integration ------------------------ -When a user deploys any of the following scenarios: - - - os-odl-bgpvpn-ha.yaml - - os-odl_l2-fdio-ha.yaml - - os-odl_l2-fdio-noha.yaml - - os-odl_l2-nofeature-ha.yaml - - os-odl_l2-sfc-noha.yaml - - os-odl_l3-nofeature-ha.yaml - -OpenDaylight (ODL) SDN controller will be deployed too and completely -integrated with OpenStack. ODL is running as a systemd service, so you can -manage it as a regular service: +When a user deploys a scenario that starts with os-odl*: + +OpenDaylight (ODL) SDN controller will be deployed and integrated with +OpenStack. ODL will run as a systemd service, and can be managed as +as a regular service: ``systemctl start/restart/stop opendaylight.service`` diff --git a/docs/release/installation/verification.rst b/docs/release/installation/verification.rst index 81e4c8e4..5156effc 100644 --- a/docs/release/installation/verification.rst +++ b/docs/release/installation/verification.rst @@ -51,7 +51,7 @@ working correctly: 1. In the left pane, click Compute -> Images, click Create Image. 2. Insert a name "cirros", Insert an Image Location - ``http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img``. + ``http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img``. 3. Select format "QCOW2", select Public, then click Create Image. diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst index da5aac92..9bb51551 100644 --- a/docs/release/release-notes/release-notes.rst +++ b/docs/release/release-notes/release-notes.rst @@ -1,6 +1,6 @@ -========================================================================== -OPNFV Release Notes for the Colorado release of OPNFV Apex deployment tool -========================================================================== +======================================================================== +OPNFV Release Notes for the Danube release of OPNFV Apex deployment tool +======================================================================== .. contents:: Table of Contents @@ -10,7 +10,7 @@ OPNFV Release Notes for the Colorado release of OPNFV Apex deployment tool Abstract ======== -This document provides the release notes for Colorado release with the Apex +This document provides the release notes for Danube release with the Apex deployment toolchain. License @@ -28,6 +28,8 @@ Version History | **Date** | **Ver.** | **Authors** | **Comment** | | | | | | +-------------+-----------+-----------------+----------------------+ +| 2017-03-30 | 4.0 | Tim Rozet | Updates for Danube | ++-------------+-----------+-----------------+----------------------+ | 2016-09-20 | 2.1.0 | Tim Rozet | More updates for | | | | | Colorado | +-------------+-----------+-----------------+----------------------+ @@ -40,7 +42,7 @@ Version History Important Notes =============== -This is the OPNFV Colorado release that implements the deploy stage of the +This is the OPNFV Danube release that implements the deploy stage of the OPNFV CI pipeline via Apex. Apex is based on RDO's Triple-O installation tool chain. @@ -52,14 +54,14 @@ deploy OPNFV using Apex installer. Summary ======= -Colorado release with the Apex deployment toolchain will establish an OPNFV +Danube 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 +of an OPNFV target system is OpenStack Newton 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 +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 -Colorado. Ceph is setup as 3 OSDs and 3 Monitors, one OSD+Mon per Controller +Danube. 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 @@ -69,7 +71,7 @@ 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 Colorado release with the Apex deployment toolchain +- Jenkins deploys a Danube release with the Apex deployment toolchain bare metal, which includes 3 control+network nodes, and 2 compute nodes. Release Data @@ -79,16 +81,16 @@ Release Data | **Project** | apex | | | | +--------------------------------------+--------------------------------------+ -| **Repo/tag** | apex/colorado.1.0 | +| **Repo/tag** | apex/danube.1.0 | | | | +--------------------------------------+--------------------------------------+ -| **Release designation** | colorado.1.0 | +| **Release designation** | danube.1.0 | | | | +--------------------------------------+--------------------------------------+ -| **Release date** | 2016-09-22 | +| **Release date** | 2017-03-31 | | | | +--------------------------------------+--------------------------------------+ -| **Purpose of the delivery** | OPNFV Colorado release | +| **Purpose of the delivery** | OPNFV Danube release | | | | +--------------------------------------+--------------------------------------+ @@ -97,25 +99,25 @@ Version change Module version changes ~~~~~~~~~~~~~~~~~~~~~~ -This is the first tracked version of the Colorado release with the Apex +This is the first tracked version of the Danube release with the Apex deployment toolchain. It is based on following upstream versions: -- OpenStack (Mitaka release) +- OpenStack (Newton release) -- OpenDaylight (Beryllium/Boron releases) +- OpenDaylight (Boron/Carbon releases) - CentOS 7 Document Version Changes ~~~~~~~~~~~~~~~~~~~~~~~~ -This is the first tracked version of Colorado release with the Apex +This is the first tracked version of Danube release with the Apex deployment toolchain. The following documentation is provided with this release: -- OPNFV Installation instructions for the Colorado release with the Apex +- OPNFV Installation instructions for the Danube release with the Apex deployment toolchain - ver. 1.0.0 -- OPNFV Release Notes for the Colorado release with the Apex deployment +- OPNFV Release Notes for the Danube release with the Apex deployment toolchain - ver. 1.0.0 (this document) Feature Additions @@ -125,35 +127,30 @@ Feature Additions | **JIRA REFERENCE** | **SLOGAN** | | | | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-107 | OpenDaylight HA - OVSDB Clustering | -+--------------------------------------+--------------------------------------+ -| JIRA: APEX-108 | Migrate to OpenStack Mitaka | +| JIRA: APEX-129 | Adds OVN SDN Controller support | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-30 | Support VLAN tagged deployments | +| JIRA: APEX-299 | Migrate to OpenStack Newton | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-105 | Enable Huge Page Configuration | -| | Options | -+--------------------------------------+--------------------------------------+ -| JIRA: APEX-111 | Allow RAM to be specified for | -| | Control/Compute in Virtual | -| | Deployments | +| JIRA: APEX-150 | Allow for multiple external networks | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-119 | Enable OVS DPDK as a deployment | -| | Scenario in Apex | +| JIRA: APEX-301 | Support Networking ODL v2 Driver | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-126 | Tacker Service deployed by Apex | +| JIRA: APEX-300 | Support OpenDaylight new netvirt | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-135 | Congress Service deployed by Apex | +| JIRA: APEX-302 | Upstream Tacker and Congress | +| | support | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-127 | Nova Instance CPU Pinning | +| JIRA: APEX-106 | Enable CPU pinning for Overcloud | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-130 | IPv6 Underlay Deployment | +| JIRA: APEX-390 | OpenDaylight HA as default for HA | +| | scenarios | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-133 | FDIO with Honeycomb Agent | +| JIRA: APEX-357 | Include Quagga in SDNVPN scenario | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-141 | Integrate VSPERF into Apex | +| JIRA: APEX-262 | Migrate to new network settings | +| | format | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-172 | Enable ONOS SFC | +| JIRA: APEX-128 | Adds Real Time KVM support | +--------------------------------------+--------------------------------------+ Bug Corrections @@ -165,55 +162,70 @@ Bug Corrections | **JIRA REFERENCE** | **SLOGAN** | | | | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-86 | Need ability to specify number of | -| | compute nodes | +| JIRA: APEX-208 | Need ability to specify which nic | +| | to place vlan on | ++--------------------------------------+--------------------------------------+ +| JIRA: APEX-215 | Keystone services not configured and | +| | error is silently ignored on VLAN | +| | Deployments | ++--------------------------------------+--------------------------------------+ +| JIRA: APEX-221 | NoHA virtual deployments should use 1| +| | compute | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-180 | Baremetal deployment error: Failed to| -| | mount root partition /dev/sda on | -| | /mnt/rootfs | +| JIRA: APEX-276 | ODL HA is unstable and crashes | +| | frequently | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-161 | Heat autoscaling stack creation fails| -| | for non-admin users | +| JIRA: APEX-287 | Name mismatch for package openstack- | +| | congress during overcloud build | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-198 | Missing NAT iptables rule for public | -| | network in instack VM | +| JIRA: APEX-339 | Enable pinning for OVS DPDK | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-147 | Installer doesn't generate/distribute| -| | SSH keys between compute nodes | +| JIRA: APEX-345 | Horizon and cloud failures due to | +| | running out of file descriptors for | +| | MariaDB in noha deployments | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-109 | ONOS routes local subnet traffic to | -| | GW | +| JIRA: APEX-370 | ISO builds fail in Danube | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-146 | Swift service present in available | -| | endpoints | +| JIRA: APEX-372 | Specifying same NIC for storage and | +| | private network but different VLANs | +| | results in duplicate NIC error | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-160 | Enable force_metadata to support | -| | subnets with VM as the router | +| JIRA: APEX-373 | Running smoke tests should install | +| | Ansible onto jump host | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-114 | OpenDaylight GUI is not available | +| JIRA: APEX-374 | Ceph accidentally disabled by default| +--------------------------------------+--------------------------------------+ -| JIRA: APEX-100 | DNS1 and DNS2 should be handled in | -| | nic bridging | +| JIRA: APEX-378 | OVS 2.5.90 NSH build fails | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-100 | DNS1 and DNS2 should be handled in | -| | nic bridging | +| JIRA: APEX-382 | yum update on undercloud breaks | +| | deployments | ++--------------------------------------+--------------------------------------+ +| JIRA: APEX-386 | Fix os-net-config to match upstream | +| | stable/newton | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-155 | NIC Metric value not used when | -| | bridging NICs | +| JIRA: APEX-398 | Tacker uses "RegionOne" instead of | +| | "regionOne" | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-136 | 2 network deployment fails | +| JIRA: APEX-399 | hugepages are not enabled when | +| | configured in deploy settings | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-89 | Deploy Ceph OSDs on compute nodes | +| JIRA: APEX-403 | Remove Quagga from build process and | +| | cache to artifacts | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-137 | added arping ass dependency for | -| | ONOS deployments | +| JIRA: APEX-406 | ODL FDIO neutron patches to all | +| | scenarios | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-121 | VM Storage deletion intermittently | -| | fails | +| JIRA: APEX-408 | Quagga's bgpd cannot start due to | +| | permissions | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-182 | Nova services not correctly deployed | +| JIRA: APEX-421 | Update odl/hc/vpp versions for odl_l3| +| | noha | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-153 | brbm bridge not created in jumphost | +| JIRA: APEX-426 | Missing virtual-computes arg in help | +| | output for deploy | ++--------------------------------------+--------------------------------------+ +| JIRA: APEX-427 | Neutron openvswitch agent starts when| +| | openvswitch is restarted | +--------------------------------------+--------------------------------------+ Deliverables @@ -224,7 +236,6 @@ Software Deliverables - Apex .iso file - Apex release .rpm (opnfv-apex-release) - Apex overcloud .rpm (opnfv-apex) - For nosdn and OpenDaylight Scenarios -- Apex overcloud onos .rpm (opnfv-apex-onos) - ONOS Scenarios - Apex undercloud .rpm (opnfv-apex-undercloud) - Apex common .rpm (opnfv-apex-common) - build.sh - Builds the above artifacts @@ -234,10 +245,10 @@ Software Deliverables 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) +- OPNFV Installation instructions for the Danube release with the Apex + deployment toolchain - ver. 4.0 +- OPNFV Release Notes for the Danube release with the Apex deployment + toolchain - ver. 4.0 (this document) Known Limitations, Issues and Workarounds ========================================= @@ -264,151 +275,65 @@ Known Issues | **JIRA REFERENCE** | **SLOGAN** | | | | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-203 | Swift proxy enabled and fails in noha| -| | deployments | +| JIRA: APEX-138 | Unclear error message when interface | +| | set to dhcp | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-215 | Keystone services not configured and | -| | the error is silently ignored (VLAN | -| | Deployments) | +| JIRA: APEX-280 | Deleted network not cleaned up | +| | on controller | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-208 | Need ability to specify which NIC to | -| | place VLAN on | +| JIRA: APEX-295 | Missing support for VLAN tenant | +| | networks | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-254 | Add dynamic hugepages configuration | +| JIRA: APEX-352 | Package "openstack-utils" is | +| | missing from overcloud | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-138 | Unclear error message when interface | -| | set to dhcp | +| 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-389 (Danube) | Compute kernel parameters are used | +| 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-410 | Need to limit number of workers per | +| | OpenStack service for baremetal | +| | deployments | ++--------------------------------------+--------------------------------------+ +| JIRA: APEX-412 | Install failures with UEFI | ++--------------------------------------+--------------------------------------+ +| JIRA: APEX-417 | Missing OVS 2.6 + NSH support | ++--------------------------------------+--------------------------------------+ +| JIRA: APEX-419 | opnfv-clean sometimes leaves admin | +| | and public network down | ++--------------------------------------+--------------------------------------+ +| JIRA: APEX-425 | Need to tweak performance settings | +| | virtual DPDK scenarios | ++--------------------------------------+--------------------------------------+ Workarounds ----------- **-** -Scenario specific release notes -=============================== - -Scenario os-odl_l3-nofeature known issues ------------------------------------------ - -* `APEX-112 <https://jira.opnfv.org/browse/APEX-112>`_: - ODL routes local subnet traffic to GW - -Scenario os-odl_l2-nofeature known issues ------------------------------------------ - -* `APEX-149 <https://jira.opnfv.org/browse/APEX-149>`_: - Openflow rules are populated very slowly - -Scenario os-odl-bgpvpn known issues --------------------------------------- - -* `APEX-278 <https://jira.opnfv.org/browse/APEX-278>`_: - Duplicate neutron config class declaration for SDNVPN - -Scenario os-onos-nofeatures/os-onos-sfc known issues ----------------------------------------------------- - -* `APEX-281 <https://jira.opnfv.org/browse/APEX-281>`_: - ONOS sometimes fails to provide addresses to instances - -Scenario os-odl_l2-sfc-noha known issues ----------------------------------------- - -* `APEX-275 <https://jira.opnfv.org/browse/APEX-275>`_: - Metadata fails in Boron - -Scenario os-nosdn-ovs known issues ----------------------------------- - -* `APEX-274 <https://jira.opnfv.org/browse/APEX-274>`_: - OVS DPDK scenario does not create vhost user ports - -Scenario os-odl_l2-fdio-noha known issues ------------------------------------------ - -* `FDS-16 <https://jira.opnfv.org/browse/FDS-16>`_: - Security group configuration through nova leads - to vhostuser port connection issues -* `FDS-62 <https://jira.opnfv.org/browse/FDS-62>`_: - APEX - Increase number of files MariaDB can open -* `FDS-79 <https://jira.opnfv.org/browse/FDS-79>`_: - Sometimes (especially in bulk crete/delete operations - when multiple networks/ports are created within short time) - OpenDaylight doesn't accept creation requests -* `FDS-80 <https://jira.opnfv.org/browse/FDS-80>`_: - After launching a VM it stayed forever in BUILD status. - Also further operation related to this VM (volume attachment etc.) - caused problems -* `FDS-81 <https://jira.opnfv.org/browse/FDS-81>`_: - After functest finishes there are two bds on computes and - none on controller -* `FDS-82 <https://jira.opnfv.org/browse/FDS-82>`_: - Nova list shows no vms but there are some on computes in paused state -* `APEX-217 <https://jira.opnfv.org/browse/APEX-217>`_: - qemu not configured with correct group:user - -Scenario os-nosdn-fdio-noha known issues ----------------------------------------- - -Note that a set of manual configration steps need to be performed -post an automated deployment for the scenario to be fully functional. -Please refer to `FDS-159 <https://jira.opnfv.org/browse/FDS-159>`_ and -`FDS-160 <https://jira.opnfv.org/browse/FDS-160>`_ for details. - -* `FDS-155 <https://jira.opnfv.org/browse/FDS-155>`_: - os-nosdn-fdio-noha scenario: tempest_smoke_serial causes - mariadb/mysqld process to hang -* `FDS-156 <https://jira.opnfv.org/browse/FDS-156>`_: - os-nosdn-fdio-noha scenario: Race conditions for - network-vif-plugged notification -* `FDS-157 <https://jira.opnfv.org/browse/FDS-157>`_: - os-nosdn-fdio-noha scenario: Intermittently VMs - would get assigned 2 IPs instead of 1 -* `FDS-158 <https://jira.opnfv.org/browse/FDS-158>`_: - os-nosdn-fdio-noha scenario: VM start/launch fails with - "no more IP addresses" in neutron logs -* `FDS-159 <https://jira.opnfv.org/browse/FDS-159>`_: - os-nosdn-fdio-noha scenario: Security groups not yet supported -* `FDS-160 <https://jira.opnfv.org/browse/FDS-160>`_: - os-nosdn-fdio-noha scenario: Vlan fix on controller -* `FDS-161 <https://jira.opnfv.org/browse/FDS-161>`_: - os-nosdn-fdio-noha scenario: VPP fails with certain UCS B-series blades - -.. _HAIssues: - -General HA scenario known issues --------------------------------- - -* `COPPER-22 <https://jira.opnfv.org/browse/COPPER-22>`_: - Congress service HA deployment is not yet supported/verified. -* `APEX-276 <https://jira.opnfv.org/browse/APEX-276>`_: - ODL HA unstable and crashes frequently Test Result =========== -The Colorado release with the Apex deployment toolchain has undergone QA -test runs with the following results: - -+--------------------------------------+--------------------------------------+ -| **TEST-SUITE** | **Results:** | -| | | -+--------------------------------------+--------------------------------------+ -| **-** | **-** | -+--------------------------------------+--------------------------------------+ +Please reference Functest project documentation for test results with the +Apex installer. References ========== -For more information on the OPNFV Colorado release, please see: +For more information on the OPNFV Danube release, please see: -http://wiki.opnfv.org/releases/Colorado +http://wiki.opnfv.org/releases/Danube :Authors: Tim Rozet (trozet@redhat.com) :Authors: Dan Radez (dradez@redhat.com) -:Version: 2.1.0 +:Version: 4.0 diff --git a/docs/release/scenarios/os-nosdn-nofeature-ha/index.rst b/docs/release/scenarios/os-nosdn-nofeature-ha/index.rst new file mode 100644 index 00000000..1902f8d9 --- /dev/null +++ b/docs/release/scenarios/os-nosdn-nofeature-ha/index.rst @@ -0,0 +1,15 @@ +.. _os-nosdn-nofeature-ha: + +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +============================================== +os-nosdn-nofeature-ha overview and description +============================================== + +.. toctree:: + :numbered: + :maxdepth: 4 + + os-nosdn-nofeature-ha.rst diff --git a/docs/release/scenarios/os-nosdn-nofeature-ha/os-nosdn-nofeature-ha.rst b/docs/release/scenarios/os-nosdn-nofeature-ha/os-nosdn-nofeature-ha.rst new file mode 100644 index 00000000..9956f290 --- /dev/null +++ b/docs/release/scenarios/os-nosdn-nofeature-ha/os-nosdn-nofeature-ha.rst @@ -0,0 +1,47 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +This document provides scenario level details for Danube 1.0 of +deployment with no SDN controller and no extra features enabled. + +.. contents:: + :depth: 3 + :local: + +============ +Introduction +============ + +This scenario is used primarily to validate and deploy a Newton OpenStack +deployment without any NFV features or SDN controller enabled. + +Scenario components and composition +=================================== + +This scenario is composed of common OpenStack services enabled by default, +including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and +by default, Tacker and Congress services are also enabled. Ceph is used as +the backend storage to Cinder on all deployed nodes. + +All services are in HA, meaning that there are multiple cloned instances of +each service, and they are balanced by HA Proxy using a Virtual IP Address +per service. + +Scenario usage overview +======================= + +Simply deploy this scenario by using the os-nosdn-nofeature-ha.yaml deploy +settings file. + +Limitations, Issues and Workarounds +=================================== + +None + +References +========== + +For more information on the OPNFV Danube release, please visit +http://www.opnfv.org/danube + diff --git a/docs/release/scenarios/os-nosdn-nofeature-noha/index.rst b/docs/release/scenarios/os-nosdn-nofeature-noha/index.rst new file mode 100644 index 00000000..8c0e65ed --- /dev/null +++ b/docs/release/scenarios/os-nosdn-nofeature-noha/index.rst @@ -0,0 +1,15 @@ +.. _os-nosdn-nofeature-noha: + +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +================================================ +os-nosdn-nofeature-noha overview and description +================================================ + +.. toctree:: + :numbered: + :maxdepth: 4 + + os-nosdn-nofeature-noha.rst diff --git a/docs/release/scenarios/os-nosdn-nofeature-noha/os-nosdn-nofeature-noha.rst b/docs/release/scenarios/os-nosdn-nofeature-noha/os-nosdn-nofeature-noha.rst new file mode 100644 index 00000000..6c5c0535 --- /dev/null +++ b/docs/release/scenarios/os-nosdn-nofeature-noha/os-nosdn-nofeature-noha.rst @@ -0,0 +1,44 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +This document provides scenario level details for Danube 1.0 of +deployment with no SDN controller and no extra features enabled. + +.. contents:: + :depth: 3 + :local: + +============ +Introduction +============ + +This scenario is used primarily to validate and deploy a Newton OpenStack +deployment without any NFV features or SDN controller enabled. + +Scenario components and composition +=================================== + +This scenario is composed of common OpenStack services enabled by default, +including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and +by default, Tacker and Congress services are also enabled. Ceph is used as +the backend storage to Cinder on all deployed nodes. + + +Scenario usage overview +======================= + +Simply deploy this scenario by using the os-nosdn-nofeature-noha.yaml deploy +settings file. + +Limitations, Issues and Workarounds +=================================== + +None + +References +========== + +For more information on the OPNFV Danube release, please visit +http://www.opnfv.org/danube + diff --git a/docs/release/scenarios/os-nosdn-performance-ha/index.rst b/docs/release/scenarios/os-nosdn-performance-ha/index.rst new file mode 100644 index 00000000..e0dbca7f --- /dev/null +++ b/docs/release/scenarios/os-nosdn-performance-ha/index.rst @@ -0,0 +1,15 @@ +.. _os-nosdn-performance-ha: + +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +================================================ +os-nosdn-performance-ha overview and description +================================================ + +.. toctree:: + :numbered: + :maxdepth: 4 + + os-nosdn-performance-ha.rst diff --git a/docs/release/scenarios/os-nosdn-performance-ha/os-nosdn-performance-ha.rst b/docs/release/scenarios/os-nosdn-performance-ha/os-nosdn-performance-ha.rst new file mode 100644 index 00000000..8f941286 --- /dev/null +++ b/docs/release/scenarios/os-nosdn-performance-ha/os-nosdn-performance-ha.rst @@ -0,0 +1,58 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +This document provides scenario level details for Danube 1.0 of +deployment with no SDN controller and performance options enabled. + +.. contents:: + :depth: 3 + :local: + +============ +Introduction +============ + +This scenario is used primarily to demonstrate the performance settings and +capabilities in Apex. This scenario will deploy a Newton OpenStack +deployment without any NFV features or SDN controller enabled. + +Scenario components and composition +=================================== + +This scenario is composed of common OpenStack services enabled by default, +including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and +by default, Tacker and Congress services are also enabled. Ceph is used as +the backend storage to Cinder on all deployed nodes. + +All services are in HA, meaning that there are multiple cloned instances of +each service, and they are balanced by HA Proxy using a Virtual IP Address +per service. + +The main purpose of this scenario is to serve as an example to show how to +set optional performance settings in an Apex deploy settings file. + +Scenario usage overview +======================= + +The performance options listed in os-nosdn-performance-ha.yaml give an example +of the different options a user can set in any deploy settings file. Some +of these performance options are actually required for other scenarios which +rely on DPDK. Options under the nova section like 'libvirtpin' allow a +user to choose which core to pin nova instances to on the overcloud compute +node. Options under 'kernel' allow a user to set kernel specific arguments +at boot, which include options like hugepages, isolcpus, enabling iommu, etc. + + +Limitations, Issues and Workarounds +=================================== + +* `APEX-389 <https://jira.opnfv.org/browse/APEX-389>`_: + Compute kernel parameters are applied to all nodes + +References +========== + +For more information on the OPNFV Danube release, please visit +http://www.opnfv.org/danube + diff --git a/docs/release/scenarios/os-odl_l3-csit-noha/index.rst b/docs/release/scenarios/os-odl_l3-csit-noha/index.rst new file mode 100644 index 00000000..29483b0f --- /dev/null +++ b/docs/release/scenarios/os-odl_l3-csit-noha/index.rst @@ -0,0 +1,15 @@ +.. _os-odl_l3-csit-noha: + +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +============================================ +os-odl_l3-csit-noha overview and description +============================================ + +.. toctree:: + :numbered: + :maxdepth: 4 + + os-odl_l3-csit-noha.rst diff --git a/docs/release/scenarios/os-odl_l3-csit-noha/os-odl_l3-csit-noha.rst b/docs/release/scenarios/os-odl_l3-csit-noha/os-odl_l3-csit-noha.rst new file mode 100644 index 00000000..7511a558 --- /dev/null +++ b/docs/release/scenarios/os-odl_l3-csit-noha/os-odl_l3-csit-noha.rst @@ -0,0 +1,58 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +This document provides scenario level details for Danube 1.0 of +deployment with the OpenDaylight SDN controller and only CSIT relevant +features enabled. + +.. contents:: + :depth: 3 + :local: + +============ +Introduction +============ + +This scenario is used primarily to validate and deploy a minimum Newton +OpenStack + OpenDaylight deployment with only required OpenStack services. + +Scenario components and composition +=================================== + +This scenario is composed of only required OpenStack services enabled by +default, including Nova, Neutron, Glance, and Keystone. OpenDaylight is also +enabled. File storage is used as the backend to Glance. + +The purpose of this file is to deploy a minimum OpenStack setup that will +still be able to exercise OpenDaylight. The use case for this scenario is +to be able to test OpenDaylight quickly in an environment with low +CPU/Memory requirements. + + +Scenario usage overview +======================= + +Simply deploy this scenario by using the os-odl_l3-csit-noha.yaml deploy +settings file. + +Limitations, Issues and Workarounds +=================================== + +* `APEX-112 <https://jira.opnfv.org/browse/APEX-112>`_: + ODL routes local subnet traffic to GW +* `APEX-149 <https://jira.opnfv.org/browse/APEX-149>`_: + OpenFlow rules are populated very slowly +* `APEX-268 <https://jira.opnfv.org/browse/APEX-268>`_: + VMs with multiple floating IPs can only access via first NIC +* `APEX-384 <https://jira.opnfv.org/browse/APEX-384>`_: + Not including odl_version in deploy settings causes error +* `APEX-422 <https://jira.opnfv.org/browse/APEX-422>`_: + First nova instance DHCP request fails + +References +========== + +For more information on the OPNFV Danube release, please visit +http://www.opnfv.org/danube + diff --git a/docs/release/scenarios/os-odl_l3-nofeature-ha/index.rst b/docs/release/scenarios/os-odl_l3-nofeature-ha/index.rst new file mode 100644 index 00000000..7d02fff4 --- /dev/null +++ b/docs/release/scenarios/os-odl_l3-nofeature-ha/index.rst @@ -0,0 +1,15 @@ +.. _os-odl_l3-nofeature-ha: + +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +=============================================== +os-odl_l3-nofeature-ha overview and description +=============================================== + +.. toctree:: + :numbered: + :maxdepth: 4 + + os-odl_l3-nofeature-ha.rst diff --git a/docs/release/scenarios/os-odl_l3-nofeature-ha/os-odl_l3-nofeature-ha.rst b/docs/release/scenarios/os-odl_l3-nofeature-ha/os-odl_l3-nofeature-ha.rst new file mode 100644 index 00000000..69df973c --- /dev/null +++ b/docs/release/scenarios/os-odl_l3-nofeature-ha/os-odl_l3-nofeature-ha.rst @@ -0,0 +1,61 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +This document provides scenario level details for Danube 1.0 of +deployment with the OpenDaylight SDN controller and no extra features enabled. + +.. contents:: + :depth: 3 + :local: + +============ +Introduction +============ + +This scenario is used primarily to validate and deploy a Newton OpenStack +deployment with OpenDaylight, and without any NFV features enabled. + +Scenario components and composition +=================================== + +This scenario is composed of common OpenStack services enabled by default, +including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and +by default, Tacker and Congress services are also enabled. Ceph is used as +the backend storage to Cinder on all deployed nodes. + +All services are in HA, meaning that there are multiple cloned instances of +each service, and they are balanced by HA Proxy using a Virtual IP Address +per service. + +OpenDaylight is also enabled in HA, and forms a cluster. Neutron +communicates with a Virtual IP Address for OpenDaylight which is load +balanced acrosss the OpenDaylight cluster. Every Open vSwitch node is +connected to every OpenDaylight for High Availability. + +Scenario usage overview +======================= + +Simply deploy this scenario by using the os-odl_l3-nofeature-ha.yaml deploy +settings file. + +Limitations, Issues and Workarounds +=================================== + +* `APEX-112 <https://jira.opnfv.org/browse/APEX-112>`_: + ODL routes local subnet traffic to GW +* `APEX-149 <https://jira.opnfv.org/browse/APEX-149>`_: + OpenFlow rules are populated very slowly +* `APEX-268 <https://jira.opnfv.org/browse/APEX-268>`_: + VMs with multiple floating IPs can only access via first NIC +* `APEX-384 <https://jira.opnfv.org/browse/APEX-384>`_: + Not including odl_version in deploy settings causes error +* `APEX-422 <https://jira.opnfv.org/browse/APEX-422>`_: + First nova instance DHCP request fails + +References +========== + +For more information on the OPNFV Danube release, please visit +http://www.opnfv.org/danube + diff --git a/docs/release/scenarios/os-odl_l3-nofeature-noha/index.rst b/docs/release/scenarios/os-odl_l3-nofeature-noha/index.rst new file mode 100644 index 00000000..182174e3 --- /dev/null +++ b/docs/release/scenarios/os-odl_l3-nofeature-noha/index.rst @@ -0,0 +1,15 @@ +.. _os-odl_l3-nofeature-noha: + +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +================================================= +os-odl_l3-nofeature-noha overview and description +================================================= + +.. toctree:: + :numbered: + :maxdepth: 4 + + os-odl_l3-nofeature-noha.rst diff --git a/docs/release/scenarios/os-odl_l3-nofeature-noha/os-odl_l3-nofeature-noha.rst b/docs/release/scenarios/os-odl_l3-nofeature-noha/os-odl_l3-nofeature-noha.rst new file mode 100644 index 00000000..7b4ebbee --- /dev/null +++ b/docs/release/scenarios/os-odl_l3-nofeature-noha/os-odl_l3-nofeature-noha.rst @@ -0,0 +1,55 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +This document provides scenario level details for Danube 1.0 of +deployment with the OpenDaylight SDN controller and no extra features enabled. + +.. contents:: + :depth: 3 + :local: + +============ +Introduction +============ + +This scenario is used primarily to validate and deploy a Newton OpenStack +deployment with OpenDaylight, and without any NFV features enabled. + +Scenario components and composition +=================================== + +This scenario is composed of common OpenStack services enabled by default, +including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and +by default, Tacker and Congress services are also enabled. Ceph is used as +the backend storage to Cinder on all deployed nodes. + +Only a single controller is deployed in this scenario, which also includes +the OpenDaylight service on it. + +Scenario usage overview +======================= + +Simply deploy this scenario by using the os-odl_l3-nofeature-noha.yaml deploy +settings file. + +Limitations, Issues and Workarounds +=================================== + +* `APEX-112 <https://jira.opnfv.org/browse/APEX-112>`_: + ODL routes local subnet traffic to GW +* `APEX-149 <https://jira.opnfv.org/browse/APEX-149>`_: + OpenFlow rules are populated very slowly +* `APEX-268 <https://jira.opnfv.org/browse/APEX-268>`_: + VMs with multiple floating IPs can only access via first NIC +* `APEX-384 <https://jira.opnfv.org/browse/APEX-384>`_: + Not including odl_version in deploy settings causes error +* `APEX-422 <https://jira.opnfv.org/browse/APEX-422>`_: + First nova instance DHCP request fails + +References +========== + +For more information on the OPNFV Danube release, please visit +http://www.opnfv.org/danube + diff --git a/docs/release/scenarios/os-ovn-nofeature-noha/index.rst b/docs/release/scenarios/os-ovn-nofeature-noha/index.rst new file mode 100644 index 00000000..74545044 --- /dev/null +++ b/docs/release/scenarios/os-ovn-nofeature-noha/index.rst @@ -0,0 +1,15 @@ +.. _os-ovn-nofeature-noha: + +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +============================================== +os-ovn-nofeature-noha overview and description +============================================== + +.. toctree:: + :numbered: + :maxdepth: 4 + + os-ovn-nofeature-noha.rst diff --git a/docs/release/scenarios/os-ovn-nofeature-noha/os-ovn-nofeature-noha.rst b/docs/release/scenarios/os-ovn-nofeature-noha/os-ovn-nofeature-noha.rst new file mode 100644 index 00000000..24de23bb --- /dev/null +++ b/docs/release/scenarios/os-ovn-nofeature-noha/os-ovn-nofeature-noha.rst @@ -0,0 +1,44 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + +This document provides scenario level details for Danube 1.0 of +deployment with the OVN SDN controller and no extra features enabled. + +.. contents:: + :depth: 3 + :local: + +============ +Introduction +============ + +This scenario is used primarily to validate and deploy a Newton OpenStack +deployment with the OVN SDN controller, and without any NFV features enabled. + +Scenario components and composition +=================================== + +This scenario is composed of common OpenStack services enabled by default, +including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and +by default, Tacker and Congress services are also enabled. Ceph is used as +the backend storage to Cinder on all deployed nodes. + +Scenario usage overview +======================= + +Simply deploy this scenario by using the os-ovn-nofeature-noha.yaml deploy +settings file. + +Limitations, Issues and Workarounds +=================================== + +* `APEX-430 <https://jira.opnfv.org/browse/APEX-430>`_: + OVN HA functionality is not available. + +References +========== + +For more information on the OPNFV Danube release, please visit +http://www.opnfv.org/danube + |