blob: 75b90f8561dd4c168fc1828a4a7742963b08e292 (
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
|
.. contents::
:depth: 3
:local:
.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) Cisco Systems, Inc
Introduction
------------
NFVbench can be decomposed in the following components:
- Configuration
- Orchestration:
- Staging
- Traffic generation
- Results analysis
Configuration
-------------
This component is in charge of getting the configuration options from the user and consolidate them with
the default configuration into a running configuration.
default configuration + user configuration options = running configuration
User configuration can come from:
- CLI configuration shortcut arguments (e.g --frame-size)
- CLI configuration file (--config [file])
- CLI configuration string (--config [string])
- REST request body
- custom platform pluging
The precedence order for configuration is (from highest precedence to lowest precedence)
- CLI configuration or REST configuration
- custom platform plugin
- default configuration
The custom platform plugin is an optional python class that can be used to override default configuration options
with default platform options which can be either hardcoded or calculated at runtime from platform specific sources
(such as platform deployment configuration files).
A custom platform plugin class is a child of the parent class nfvbench.config_plugin.ConfigPlugin.
Orchestration
-------------
Once the configuration is settled, benchmark orchestration is managed by the ChainRunner class (nfvbench.chain_runner.ChainRunner).
The chain runner will take care of orchestrating the staging, traffic generation and results analysis.
Staging
-------
The staging component is in charge of staging the OpenStack resources that are used for the requested packet path.
For example, for a PVP packet path, this module will create 2 Neutron networks and one VM instance connected to these 2 networks.
Multi-chaining and VM placement is also handled by this module.
Main class: nfvbench.chaining.ChainManager
Traffic Generation
------------------
The traffic generation component is in charge of contrilling the TRex traffic generator using its python API.
It includes tasks such as:
- traffic check end to end to make sure the packet path is clear in both directions before starting a benchmark
- programming the TRex traffic flows based on requested parameters
- fixed rate control
- NDR/PDR binary search
Main class: nfvbench.traffic_client.TrafficClient
Traffic Generator Results Analysis
----------------------------------
At the end of a traffic generation session, this component collects the results from TRex and packages them in a format that
is suitable for the various output formats (JSON, REST, file, fluentd).
In the case of multi-chaining, it handles aggregation of results across chains.
Main class: nfvbench.stats_manager.StatsManager
|
