diff options
Diffstat (limited to 'docs')
18 files changed, 633 insertions, 210 deletions
diff --git a/docs/release/installation/architecture.rst b/docs/release/installation/architecture.rst index ae634cc4..eff5d35d 100644 --- a/docs/release/installation/architecture.rst +++ b/docs/release/installation/architecture.rst @@ -30,7 +30,7 @@ Undercloud ---------- The undercloud is not Highly Available. End users do not depend on the -underloud. It is only for management purposes. +undercloud. It is only for management purposes. Overcloud --------- @@ -47,7 +47,7 @@ will run the following services: - Ceph Monitors and OSDs Stateless OpenStack services - All running statesless OpenStack services are load balanced by HA Proxy. + All running stateless OpenStack services are load balanced by HA Proxy. Pacemaker monitors the services and ensures that they are running. Stateful OpenStack services @@ -65,9 +65,13 @@ RabbitMQ establishment of clustering across cluster members. OpenDaylight - OpenDaylight is currently installed on all three control nodes but only - started on the first control node. OpenDaylight's HA capabilities are not yet - mature enough to be enabled. + OpenDaylight is currently installed on all three control nodes and started as + an HA cluster unless otherwise noted for that scenario. OpenDaylight's + database, known as MD-SAL, breaks up pieces of the database into "shards". + Each shard will have its own election take place, which will determine + which OpenDaylight node is the leader for that shard. The other + OpenDaylight nodes in the cluster will be in standby. Every Open vSwitch + node connects to every OpenDaylight to enable HA. HA Proxy HA Proxy is monitored by Pacemaker to ensure it is running across all nodes @@ -127,9 +131,9 @@ issues per scenario. The following scenarios correspond to a supported +-------------------------+-------------+---------------+ | os-nosdn-ovs-noha | OVS for NFV | Yes | +-------------------------+-------------+---------------+ -| os-nosdn-fdio-ha | FDS | Yes | +| os-nosdn-fdio-ha | FDS | No | +-------------------------+-------------+---------------+ -| os-nosdn-fdio-noha | FDS | Yes | +| os-nosdn-fdio-noha | FDS | No | +-------------------------+-------------+---------------+ | os-nosdn-kvm-ha | KVM for NFV | Yes | +-------------------------+-------------+---------------+ diff --git a/docs/release/installation/baremetal.rst b/docs/release/installation/baremetal.rst index f06de9f2..c7b4740e 100644 --- a/docs/release/installation/baremetal.rst +++ b/docs/release/installation/baremetal.rst @@ -50,7 +50,7 @@ images provided by the undercloud. These disk images include all the necessary packages and configuration for an OPNFV deployment to execute. Once the disk images have been written to node's disks the nodes will boot locally and execute cloud-init which will execute the final node configuration. This -configuration is largly completed by executing a puppet apply on each node. +configuration is largely completed by executing a puppet apply on each node. Installation High-Level Overview - VM Deployment ================================================ @@ -62,7 +62,7 @@ VM a collection of VMs (3 control nodes + 2 compute for an HA deployment or 1 control node and 1 or more compute nodes for a Non-HA Deployment) will be defined for the target OPNFV deployment. The part of the toolchain that executes IPMI power instructions calls into libvirt instead of the IPMI -interfaces on baremetal servers to operate the power managment. These VMs are +interfaces on baremetal servers to operate the power management. These VMs are then provisioned with the same disk images and configuration that baremetal would be. @@ -235,7 +235,7 @@ help you customize them. (``/etc/opnfv-apex/``). These files are named with the naming convention os-sdn_controller-enabled_feature-[no]ha.yaml. These files can be used in place of the (``/etc/opnfv-apex/deploy_settings.yaml``) file if one suites - your deployment needs. If a pre-built deploy_settings file is choosen there + your deployment needs. If a pre-built deploy_settings file is chosen there is no need to customize (``/etc/opnfv-apex/deploy_settings.yaml``). The pre-built file can be used in place of the (``/etc/opnfv-apex/deploy_settings.yaml``) file. diff --git a/docs/release/installation/virtualinstall.rst b/docs/release/installation/virtualinstall.rst index 5da2ee3c..61fc4be6 100644 --- a/docs/release/installation/virtualinstall.rst +++ b/docs/release/installation/virtualinstall.rst @@ -8,7 +8,7 @@ undercloud VM. In addition to the undercloud VM a collection of VMs or more compute nodes for a non-HA Deployment) will be defined for the target OPNFV deployment. The part of the toolchain that executes IPMI power instructions calls into libvirt instead of the IPMI interfaces on baremetal -servers to operate the power managment. These VMs are then provisioned with +servers to operate the power management. These VMs are then provisioned with the same disk images and configuration that baremetal would be. To Triple-O these nodes look like they have just built and registered the same way as bare metal nodes, the main difference is the use of a libvirt driver for the power @@ -22,6 +22,25 @@ Installation Guide - Virtual Deployment This section goes step-by-step on how to correctly install and provision the OPNFV target system to VM nodes. +Special Requirements for Virtual Deployments +-------------------------------------------- + +In scenarios where advanced performance options or features are used, such +as using huge pages with nova instances, DPDK, or iommu; it is required to +enabled nested KVM support. This allows hardware extensions to be passed to +the overcloud VMs, which will allow the overcloud compute nodes to bring up +KVM guest nova instances, rather than QEMU. This also provides a great +performance increase even in non-required scenarios and is recommended to be +enabled. + +During deployment the Apex installer will detect if nested KVM is enabled, +and if not, it will attempt to enable it; while printing a warning message +if it cannot. Check to make sure before deployment that Nested +Virtualization is enabled in BIOS, and that the output of ``cat +/sys/module/kvm_intel/parameters/nested`` returns "Y". Also verify using +``lsmod`` that the kvm_intel module is loaded for x86_64 machines, and +kvm_amd is loaded for AMD64 machines. + Install Jumphost ---------------- @@ -32,7 +51,7 @@ Running ``opnfv-deploy`` You are now ready to deploy OPNFV! ``opnfv-deploy`` has virtual deployment capability that includes all of -the configuration nessesary to deploy OPNFV with no modifications. +the configuration necessary to deploy OPNFV with no modifications. If no modifications are made to the included configurations the target environment will deploy with the following architecture: diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst index da5aac92..5a292e3c 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-150 | Allow for multiple external networks | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-111 | Allow RAM to be specified for | -| | Control/Compute in Virtual | -| | Deployments | +| JIRA: APEX-301 | Support Networking ODL v2 Driver | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-119 | Enable OVS DPDK as a deployment | -| | Scenario in Apex | +| JIRA: APEX-300 | Support OpenDaylight new netvirt | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-126 | Tacker Service deployed by Apex | +| JIRA: APEX-302 | Upstream Tacker and Congress | +| | support | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-135 | Congress Service deployed by Apex | +| JIRA: APEX-106 | Enable CPU pinning for Overcloud | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-127 | Nova Instance CPU Pinning | +| JIRA: APEX-390 | OpenDaylight HA as default for HA | +| | scenarios | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-130 | IPv6 Underlay Deployment | +| JIRA: APEX-357 | Include Quagga in SDNVPN scenario | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-133 | FDIO with Honeycomb Agent | +| JIRA: APEX-262 | Migrate to new network settings | +| | format | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-141 | Integrate VSPERF into Apex | -+--------------------------------------+--------------------------------------+ -| JIRA: APEX-172 | Enable ONOS SFC | +| JIRA: APEX-128 | Adds Real Time KVM support | +--------------------------------------+--------------------------------------+ Bug Corrections @@ -165,55 +162,73 @@ 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-180 | Baremetal deployment error: Failed to| -| | mount root partition /dev/sda on | -| | /mnt/rootfs | +| 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-161 | Heat autoscaling stack creation fails| -| | for non-admin users | +| JIRA: APEX-276 | ODL HA is unstable and crashes | +| | frequently | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-198 | Missing NAT iptables rule for public | -| | network in instack VM | +| JIRA: APEX-287 | Name mismatch for package openstack- | +| | congress during overcloud build | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-147 | Installer doesn't generate/distribute| -| | SSH keys between compute nodes | +| JIRA: APEX-339 | Enable pinning for OVS DPDK | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-109 | ONOS routes local subnet traffic to | -| | GW | +| JIRA: APEX-345 | Horizon and cloud failures due to | +| | running out of file descriptors for | +| | MariaDB in noha deployments | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-146 | Swift service present in available | -| | endpoints | +| JIRA: APEX-370 | ISO builds fail in Danube | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-160 | Enable force_metadata to support | -| | subnets with VM as the router | +| JIRA: APEX-372 | Specifying same NIC for storage and | +| | private network but different VLANs | +| | results in duplicate NIC error | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-114 | OpenDaylight GUI is not available | +| JIRA: APEX-373 | Running smoke tests should install | +| | Ansible onto jump host | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-100 | DNS1 and DNS2 should be handled in | -| | nic bridging | +| 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-382 | yum update on undercloud breaks | +| | deployments | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-155 | NIC Metric value not used when | -| | bridging NICs | +| JIRA: APEX-386 | Fix os-net-config to match upstream | +| | stable/newton | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-136 | 2 network deployment fails | +| JIRA: APEX-398 | Tacker uses "RegionOne" instead of | +| | "regionOne" | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-89 | Deploy Ceph OSDs on compute nodes | +| JIRA: APEX-399 | hugepages are not enabled when | +| | configured in deploy settings | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-137 | added arping ass dependency for | -| | ONOS deployments | +| JIRA: APEX-403 | Remove Quagga from build process and | +| | cache to artifacts | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-121 | VM Storage deletion intermittently | -| | fails | +| JIRA: APEX-406 | ODL FDIO neutron patches to all | +| | scenarios | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-182 | Nova services not correctly deployed | +| JIRA: APEX-407 | VPP service does not start upon | +| | reboot | +--------------------------------------+--------------------------------------+ -| JIRA: APEX-153 | brbm bridge not created in jumphost | +| JIRA: APEX-408 | Quagga's bgpd cannot start due to | +| | permissions | ++--------------------------------------+--------------------------------------+ +| JIRA: APEX-421 | Update odl/hc/vpp versions for odl_l3| +| | noha | ++--------------------------------------+--------------------------------------+ +| 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 +239,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 +248,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 +278,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 + |