diff options
| author |   ahothan <ahothan@cisco.com> | 2018-11-13 10:16:15 -0800 |
|---|---|---|
| committer | ahothan <ahothan@cisco.com> | 2018-11-13 10:16:15 -0800 |
| commit | 7a90e74a1390794b72fc5c3629e141f2def908d7 (patch) | |
| tree | def2805186b2a2f65ac7db183b3ce576734bc05a /docs/development/design/traffic_desc.rst | |
| parent | 3dfb5268ebfada08c1a2316708564e627f86da42 (diff) | |
Update 2.0 doc
Change-Id: I223bd40e798c772d7cf7423d88f62bccb164a46b
Signed-off-by: ahothan <ahothan@cisco.com>
Diffstat (limited to 'docs/development/design/traffic_desc.rst')
| -rw-r--r-- | docs/development/design/traffic_desc.rst | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/development/design/traffic_desc.rst b/docs/development/design/traffic_desc.rst index 2a40b6a..6442013 100644 --- a/docs/development/design/traffic_desc.rst +++ b/docs/development/design/traffic_desc.rst @@ -10,11 +10,10 @@ The general packet path model followed by NFVbench requires injecting traffic in number of service chains, where each service chain is identified by 2 edge networks (left and right). In the current multi-chaining model: -- all service chains share the same left and right edge networks -- each port associated to the traffic generator is dedicated to send traffic to one edge network +- all service chains can either share the same left and right edge networks or can have their own edge networks +- each port associated to the traffic generator is dedicated to send traffic to one side of the edge networks -In an OpenStack deployment, this corresponds to all chains sharing the same 2 neutron networks. -If VLAN encapsulation is used, all traffic sent to a port will have the same VLAN id. +If VLAN encapsulation is used, all traffic sent to a port will either have the same VLAN id (shared networks) or distinct VLAN ids (dedicated egde networks) Basic Packet Description ------------------------ |