summaryrefslogtreecommitdiffstats
path: root/docs/release/installation.introduction.rst
diff options
context:
space:
mode:
authorSofia Wallin <sofia.wallin@est.tech>2020-11-17 10:30:33 +0100
committerSofia Wallin <sofia.wallin@est.tech>2020-12-16 15:19:16 +0100
commit61a23a6e23a227abc0ec3069742b45db6cc85610 (patch)
tree33173f639f71d321a795aa7acb1c38f92d906e42 /docs/release/installation.introduction.rst
parent01dc193a89f93aca55d2ac2c6d06c9856ac25234 (diff)
Jerma updates
Updated participating projects Updated according to Al's feedback. List of participating project still needs to be updated. Updates made to the installation, user and config guide, removed all scenario references. Change-Id: Ifc8fe984ff488131870806267124c5460a688c3f Signed-off-by: Sofia Wallin <sofia.wallin@est.tech>
Diffstat (limited to 'docs/release/installation.introduction.rst')
-rw-r--r--docs/release/installation.introduction.rst49
1 files changed, 4 insertions, 45 deletions
diff --git a/docs/release/installation.introduction.rst b/docs/release/installation.introduction.rst
index 7a5132dcf..b109a3fcd 100644
--- a/docs/release/installation.introduction.rst
+++ b/docs/release/installation.introduction.rst
@@ -11,57 +11,16 @@ Installation
Abstract
========
-This an overview document for the installation of the Iruya release of OPNFV.
-
-The Iruya release can be installed making use of one of the installer projects in OPNFV:
-Airship or Fuel. 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
-============
-
-The OPNFV platform is comprised of a variety of upstream components that may be deployed on your
-infrastructure. A composition of components, tools and configurations is identified in OPNFV as a
-deployment scenario.
-
-The various OPNFV scenarios provide unique features and capabilities that you may want to leverage, and
-it is important to understand your required target platform capabilities before installing and
-configuring your scenarios.
-
-An OPNFV installation requires either a physical infrastructure environment as defined
-in the `Pharos specification <https://wiki.opnfv.org/display/pharos/Pharos+Specification>`_, or a virtual one.
-When configuring a physical infrastructure it is strongly advised to follow the Pharos configuration guidelines.
-
-
-Scenarios
-=========
-
-OPNFV scenarios are designed to host virtualised network functions (VNF’s) in a variety of deployment
-architectures and locations. Each scenario provides specific capabilities and/or components aimed at
-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 Iruya release refer to the scenario
-description documents provided:
-
-- :ref:`os-nosdn-ovs-noha <os-nosdn-ovs-noha>`
-- :ref:`os-nosdn-fdio-noha <os-nosdn-fdio-noha>`
+This is the installation document for the OPNFV Jerma release, please use this document for further reference.
Installation Procedure
======================
-Detailed step by step instructions for working with an installation toolchain and installing
-the required scenario is provided by the installation projects. The projects providing installation
-support for the OPNFV Iruya release are: Airship and Fuel.
+Each of the test Frameworks and other projects will have separate installations procedures: see the individual project documentation.
-The instructions for each toolchain can be found in these links:
+- :ref:`Airship Installation Guide <airship-installation>`
+- :ref:`Kuberef Installation Guide <kuberef-installation>`
-- :ref:`Airship installation instruction <airship-installation>`
-- :ref:`Fuel installation instruction <fuel-installation>`
OPNFV Test Frameworks
=====================