From 391dcf76fefb747888a3411ae3b8df7b1ad26685 Mon Sep 17 00:00:00 2001 From: ahothan Date: Sun, 7 Oct 2018 15:55:25 -0700 Subject: 2.0 beta NFVBENCH-91 Allow multi-chaining with separate edge networks Includes complete refactoring of code Beta for NFVbench 2.0 Change-Id: I2997f0fb7722d5ac626cd11a68692ae458c7676e Signed-off-by: ahothan --- docs/development/design/design.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/development/design/design.rst') diff --git a/docs/development/design/design.rst b/docs/development/design/design.rst index d0f2f45..6de6007 100644 --- a/docs/development/design/design.rst +++ b/docs/development/design/design.rst @@ -50,7 +50,7 @@ The staging component is in charge of staging the OpenStack resources that are u 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.chain_managers.StageManager +Main class: nfvbench.chaining.ChainManager Traffic Generation ------------------ @@ -70,4 +70,4 @@ At the end of a traffic generation session, this component collects the results 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.chain_managers.StatsManager +Main class: nfvbench.stats_manager.StatsManager -- cgit 1.2.3-korg