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
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
==============
Scenariomatrix
==============
Scenarios are implemented as deployable compositions through integration with an installation tool.
OPNFV supports multiple installation tools and for any given release not all tools will support all
scenarios. While our target is to establish parity across the installation tools to ensure they
can provide all scenarios, the practical challenge of achieving that goal for any given feature and
release results in some disparity.
Danube scenario overeview
^^^^^^^^^^^^^^^^^^^^^^^^^
The following table provides an overview of the installation tools and available scenario's
in the Danube release of OPNFV.
Scenario status is indicated by a weather pattern icon. All scenarios listed with
a weather pattern are possible to deploy and run in your environment or a Pharos lab,
however they may have known limitations or issues as indicated by the icon.
Weather pattern icon legend:
+---------------------------------------------+----------------------------------------------------------+
| Weather Icon | Scenario Status |
+=============================================+==========================================================+
| .. image:: images/weather-clear.jpg | Stable, no known issues |
+---------------------------------------------+----------------------------------------------------------+
| .. image:: images/weather-few-clouds.jpg | Stable, documented limitations |
+---------------------------------------------+----------------------------------------------------------+
| .. image:: images/weather-overcast.jpg | Deployable, stability or feature limitations |
+---------------------------------------------+----------------------------------------------------------+
| .. image:: images/weather-dash.jpg | Not deployed with this installer |
+---------------------------------------------+----------------------------------------------------------+
Scenarios that are not yet in a state of "Stable, no known issues" will continue to be stabilised
and updates will be made on the stable/danube branch. While we intend that all Danube
scenarios should be stable it is worth checking regularly to see the current status. Due to
our dependency on upstream communities and code some issues may not be resolved prior to the D release.
Scenario Naming
^^^^^^^^^^^^^^^
In OPNFV scenarios are identified by short scenario names, these names follow a scheme that
identifies the key components and behaviours of the scenario. The rules for scenario naming are as follows:
.. code:: bash
os-[controller]-[feature]-[mode]-[option]
Details of the fields are
* **[os]:** mandatory
* Refers to the platform type used
* possible value: os (OpenStack)
* **[controller]:** mandatory
* Refers to the SDN controller integrated in the platform
* example values: nosdn, ocl, odl, onos
* **[feature]:** mandatory
* Refers to the feature projects supported by the scenario
* example values: nofeature, kvm, ovs, sfc
* **[mode]:** mandatory
* Refers to the deployment type, which may include for instance high availability
* possible values: ha, noha
* **[option]:** optional
* Used for the scenarios those do not fit into naming scheme.
* The optional field in the short scenario name should not be included if there is no optional scenario.
Some examples of supported scenario names are:
* **os-nosdn-kvm-noha**
* This is an OpenStack based deployment using neutron including the OPNFV enhanced KVM hypervisor
* **os-onos-nofeature-ha**
* This is an OpenStack deployment in high availability mode including ONOS as the SDN controller
* **os-odl_l2-sfc**
* This is an OpenStack deployment using OpenDaylight and OVS enabled with SFC features
* **os-nosdn-kvm_nfv_ovs_dpdk-ha**
* This is an Openstack deployment with high availability using OVS, DPDK including the OPNFV enhanced KVM hypervisor
* This deployment has ``3-Contoller and 2-Compute nodes``
* **os-nosdn-kvm_nfv_ovs_dpdk-noha**
* This is an Openstack deployment without high availability using OVS, DPDK including the OPNFV enhanced KVM hypervisor
* This deployment has ``1-Contoller and 3-Compute nodes``
* **os-nosdn-kvm_nfv_ovs_dpdk_bar-ha**
* This is an Openstack deployment with high availability using OVS, DPDK including the OPNFV enhanced KVM hypervisor
and Barometer
* This deployment has ``3-Contoller and 2-Compute nodes``
* **os-nosdn-kvm_nfv_ovs_dpdk_bar-noha**
* This is an Openstack deployment without high availability using OVS, DPDK including the OPNFV enhanced KVM hypervisor
and Barometer
* This deployment has ``1-Contoller and 3-Compute nodes``
Installing your scenario
^^^^^^^^^^^^^^^^^^^^^^^^
There are two main methods of deploying your target scenario, one method is to follow this guide which will
walk you through the process of deploying to your hardware using scripts or ISO images, the other method is
to set up a Jenkins slave and connect your infrastructure to the OPNFV Jenkins master.
For the purposes of evaluation and development a number of Danube scenarios are able to be deployed
virtually to mitigate the requirements on physical infrastructure. Details and instructions on performing
virtual deployments can be found in the installer specific installation instructions.
To set up a Jenkins slave for automated deployment to your lab, refer to the `Jenkins slave connect guide.
<http://artifacts.opnfv.org/brahmaputra.1.0/docs/opnfv-jenkins-slave-connection.brahmaputra.1.0.html>`_
|
