From 1db1bd89db4cffe08845f3042af6fc0989a71d5f Mon Sep 17 00:00:00 2001 From: ChristopherPrice Date: Wed, 29 Mar 2017 14:51:26 +0200 Subject: Updating composite docs with links, information and versions. Comments welcome. Change-Id: I1c6bca795d0d638e0867a59fa6b1fd0a17e5333c Signed-off-by: ChristopherPrice --- docs/release/installation.introduction.rst | 43 +++++++++--------------------- 1 file changed, 13 insertions(+), 30 deletions(-) (limited to 'docs/release/installation.introduction.rst') diff --git a/docs/release/installation.introduction.rst b/docs/release/installation.introduction.rst index bacedb76d..e31c5b1ee 100644 --- a/docs/release/installation.introduction.rst +++ b/docs/release/installation.introduction.rst @@ -10,12 +10,12 @@ Abstract ======== The following document provides an overview of the instructions required for the installation -of the Colorado release of OPNFV. +of the Danube release of OPNFV. -The Colorado release can be installed using a tool from the following -integration projects participating in OPNFV: Apex, Compass4Nfv, Fuel and JOID. -Each installer provides the ability to install a common OPNFV platform as well as integrating -additional features delivered through a variety of scenarios by the OPNFV community. +The Danube release can be installed using a tool from the following integration projects in OPNFV: +Apex, Compass4Nfv, Fuel and JOID. Each installer provides the ability to install a common OPNFV +platform as well as integrating additional features delivered through a variety of scenarios by +the OPNFV community. Introduction @@ -30,7 +30,7 @@ it is important to understand your required target platform capabilities before configuring your scenarios. An OPNFV installation requires either a physical, or virtual, infrastructure environment as defined -in the `Pharos specification `. +in the `Pharos specification `. When configuring a physical infrastructure it is strongly advised to follow the Pharos configuration guidelines. @@ -44,25 +44,17 @@ solving specific problems for the deployment of VNF’s. A scenario may, for instance, include components such as OpenStack, OpenDaylight, OVS, KVM etc., where each scenario will include different source components or configurations. -To learn more about the scenarios supported in the Colorado release refer to the scenario +To learn more about the scenarios supported in the Danube release refer to the scenario description documents provided: -- Accelerated OVS `os-nosdn-ovs `_ -- Layer 3 overlay using opendaylight `os-odl-l2-bgpvpn `_ -- FD.io based forwarding using opendaylight SDN `os-odl-12-fdio-noha `_ -- High availability service function chaining `os-odl-l2-sfc-ha `_ -- Service function chaining `os-odl-l2-sfc-noha `_ -- Accelerated KVM hypervisor `os-nosdn-kvm-ha `_ -- LXD container hypervisor `os-nosdn-lxd-noha `_ -- High Availability LXD container hypervisor `os-nosdn-lxd-ha `_ - +- Links to scenario description documents need to be added here. (todo) Installation Procedure ====================== Detailed step by step instructions for working with an installation toolchain and installing the required scenario are provided by each installation project. The four projects providing installation -support for the OPNFV Colorado release are; Apex, Compass4nfv, Fuel and Joid. +support for the OPNFV Danube release are; Apex, Compass4nfv, Fuel and Joid. The instructions for each toolchain can be found in these links: @@ -94,16 +86,7 @@ Many of the OPNFV test project provide user-guide documentation and installation Security Notes ============== -The following patches were applied to fix security issues discovered in opnfv -projects, during the Colorado release cycle. - -- `Removal of private keys `_ -- `Fix security issues of eval-s in testapi `_ -- `Implements use of yaml.safe_load `_ -- `Fix security issues reported by the security audit `_ -- `Fix issues found in security review `_ -- `Removing OpenSteak Project `_ -- `Remove unsed files in open-contrail role `_ -- `Get rid of private key in repo `_ -- `Handling file loads and tmp dirs differently `_ -- `Remove 'Debug = True' when run Flask and add logger `_ +The following patches were applied to fix security issues discovered in OPNFV +projects, during the Danube release cycle. + +- Links to security patches need to be added here. (todo) -- cgit 1.2.3-korg