add network info to topology 45/36745/17
authorRoss Brattain <ross.b.brattain@intel.com>
Mon, 22 May 2017 04:07:50 +0000 (21:07 -0700)
committerEdward MacGillivray <edward.s.macgillivray@intel.com>
Thu, 13 Jul 2017 23:34:24 +0000 (16:34 -0700)
commit7a32c18b2fb3f220f099218871ba29115ef31ee9
tree3e87b12bdbd030a43bbd849aee4f231b699768a5
parent49d358550209ab39bf618d8b226f655a0b54d13f
add network info to topology

we need to know which network each port is connected to
so we can find VLAN or VXLAN ID.

To do this we implement a new method for Contexts,
Context.get_network().  This method is similar to
Context.get_server(), it searches for a given
network name in all the contexts.

From this we generate a context_cfg["networks"]
dict that stores all the network info for the nodes
in the scenario.

Then when we generate the topology for VNFD, we can
lookup a given network by the vld_id and get the
network_type, segmentation_id, etc.

Then if we need to for example generated
traffic on a given VLAN or VXLAN, we have this
info available.

Define default nd_route_tbl for ACL VNF
we need default empty nd_route_tbl for IPv6 route.

Change-Id: I9f9cfbd6acabeb4ae4675ca7354390efa57b29e7
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
Signed-off-by: Edward MacGillivray <edward.s.macgillivray@intel.com>
15 files changed:
tests/unit/benchmark/contexts/test_heat.py
tests/unit/benchmark/contexts/test_node.py
tests/unit/benchmark/contexts/test_standalone.py
tests/unit/benchmark/core/test_task.py
tests/unit/benchmark/scenarios/networking/test_vnf_generic.py
tests/unit/orchestrator/test_heat.py
yardstick/benchmark/contexts/base.py
yardstick/benchmark/contexts/dummy.py
yardstick/benchmark/contexts/heat.py
yardstick/benchmark/contexts/model.py
yardstick/benchmark/contexts/node.py
yardstick/benchmark/contexts/standalone.py
yardstick/benchmark/core/task.py
yardstick/benchmark/scenarios/networking/vnf_generic.py
yardstick/orchestrator/heat.py