2 name: insert a name for the scenario
3 description: insert a description for the scenario
6 vnf1: # vnf/net name in the scenario
7 type: VNF # VNF, network, external_network (if it is a datacenter network)
8 VNF model: vnf_model1 # VNF name as introduced in OPENMANO DB
9 # vnf_id: 519f03ee-8ab6-11e4-ab4c-52540056c317 # Optionally, instead of the VNF name, the VNF id in Openmano DB can be used
13 # Optional information for display in the openmano-gui: graphical position of the node and its interfaces
14 graph: {"y":399,"x":632,"ifaces":{"left":[["xe0","d"],["xe1","d"]],"bottom":[["eth0","v"],["eth1","m"]]}}
15 bridge1: # Bridge networks must be declared in this section if we want to interconnect VNFs using a Linux bridge
17 model: bridge_net # 'bridge_net' or 'dataplane_net' for 'network' type
18 default: # External networks (datacenter nets) must be declared in this section if we want to interconnect VNFs to them
19 type: external_network
20 model: default # datacenter net name, as introduced in OPENMANO DB
21 connections: # In this section, connections between VNFs and networks are explicited
23 # Data plane connections do not need to include a bridge since they are built through the Openflow Controller
24 nodes: # nodes that will be connected: one or several vnfs, and optionally one additional network declared in nodes section
25 - vnf1: xe0 # First node and its interface to be connected (interfaces must match to one in the VNF descriptor)
26 - vnf2: xe0 # Second node and its interface
28 # Control plane connections must include a bridge network in the list of nodes
30 - bridge1: null # Bridge networks must be included if we want to interconnect the nodes to that network
34 # Connections based on external networks (datacenter nets) must include the external network in the list of nodes
36 - default: null # Datacenter networks (external networks) must be included if we want to interconnect the nodes to that network