blob: 2f1dbabab0d8575cecc1898f900f2d7f382f48b5 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
.. _opnfv-installation:
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. SPDX-License-Identifier: CC-BY-4.0
.. (c) Sofia Wallin Ericsson AB and other contributors
============
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-ovs-ha <os-nosdn-ovs-ha>`
- :ref:`os-nosdn-fdio-noha <os-nosdn-fdio-noha>`
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.
The instructions for each toolchain can be found in these links:
- :ref:`Airship installation instruction <airship-installation>`
- :ref:`Fuel installation instruction <fuel-installation>`
OPNFV Test Frameworks
=====================
If you have elected to install the OPNFV platform using the deployment toolchain provided by OPNFV,
your system will have been validated once the installation is completed.
The basic deployment validation only addresses a small part of capabilities in
the platform and you may want to execute more exhaustive tests. Some investigation will be required to
select the right test suites to run on your platform.
Many of the OPNFV test project provide user-guide documentation and installation instructions in :ref:`this document <testing-userguide>`
|
