blob: 3027a7ea8b78017ad2d566325c55d52647982cc2 (
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
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
|
.. OPNFV - Open Platform for Network Function Virtualization
.. This work is licensed under a Creative Commons Attribution 4.0
.. International License.
.. http://creativecommons.org/licenses/by/4.0
Scenario: "OpenStack - ovs-nfv"
=============================
Scenario: apex-os-nosdn-ovs-noha
"apex-os-ovs-noha" is a scenario developed as part of the OVS for NFV
OPNFV project. The main components of the "apex-os-nosdn-ovs-noha" scenario
are:
- APEX (TripleO) installer (please also see APEX installer documentation)
- Openstack (in non-HA configuration)
- OVS/DPDK Open vSwitch with DPDK data plane virtual forwarder for tenant networking
Introduction
============
NFV and virtualized high performance applications, such as video processing,
require Open vSwitch to be accelerated with a fast data plane solution that provides both
carrier grade forwarding performance, scalability and open extensibility.
A key component of any NFV solution is the virtual forwarder, which should consist of
soft switch that includes an accelerated data plane component. For this, any virtual
switch should make use of
hardware accelerators and optimized cache operation to be run in user space.
The "Openstack - Open vSwitch/DPDK" scenario provides
use-cases for deployment of NFV nodes instantiated by
an Openstack orchestration system on OVS/DPDK enabled compute nodes.
A deployment of the "apex-os-nosdn-ovs-noha" scenario consists of 3 or more
servers:
* 1 Jumphost hosting the APEX installer - running the Undercloud
* 1 Controlhost, which runs the Overcloud and Openstack services
* 1 or more Computehosts
.. image:: ovs4nfv.png
Tenant networking leverages Open vSwitch accelerated with a fast user space data path such
as DPDK.
Open VSwitch (OVS) with the Linux kernel module data path is used for all other
connectivity, such as connectivity to public networking "the
Internet" (i.e. br-ext) is performed via non-accelerated OVS.
Features of the scenario
------------------------
Main features of the "apex-os-ovs-nosdn-noha" scenario:
* Automated installation using the APEX installer
* Accelerated tenant networking using OVS/DPDK as the forwarder
Networking in this scenario using OVS with accelerated User space IO.
---------------------------------------------------------------------
The apex-os-nosdn-ovs-noha scenario combines components from three open
source projects: OpenStack, Open vSwitch and DPDK. To make accelerated networking
available for this scenario Open vSwitch is bound via its netdev interface
with DPDK user space accelerated capability.
Scenario Configuration
======================
To enable the "apex-os-nosdn-ovs-noha" scenario check the appropriate settings
in the APEX configuration files. Those are typically found in /etc/opnfv-apex.
File "deploy_settings.yaml" choose false for sdn controller::
global_params:
ha_enabled: false
deploy_options:
sdn_controller: false
sdn_l3: false
tacker: false
congress: false
sfc: false
vpn: false
Validated deployment environments
=================================
The "os-odl_l2-ovs-noha" scenario has been deployed and tested
on the following sets of hardware:
* TBD
Limitations, Issues and Workarounds
===================================
There are no known issues.
References
==========
* OVS for NFV OPNFV project wiki: https://wiki.opnfv.org/display/ovsnfv
* Open vSwitch: http://openvswitch.org/
* DPDK: http://dpdk.org
* OPNFV Colorado release - more information: http://www.opnfv.org/colorado
|
