tacker/samples/tosca-templates/vnfd/tosca-vnfd-openwrt.yaml
Sridhar Ramaswamy cf7f677fc7 Introduce TOSCA 'order' property for connection points
This is a follow-on to [1] which uses dictionary for VNFD
template and no longer relies on OrderedDict to preserve
the order of the node_types in the VNFD template. Instead
we are going to insist the templates to explicit mention
the order of the CP.

[1] https://review.openstack.org/#/c/360809

Change-Id: Iaf7389305cfea90f158da0eaaa19afe86869541b
Closes-Bug: #1591361
2016-09-13 06:12:49 +00:00

85 lines
1.7 KiB
YAML

tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0
description: OpenWRT with services
metadata:
template_name: OpenWRT
topology_template:
node_templates:
VDU1:
type: tosca.nodes.nfv.VDU.Tacker
capabilities:
nfv_compute:
properties:
num_cpus: 1
mem_size: 512 MB
disk_size: 1 GB
properties:
image: OpenWRT
config: |
param0: key1
param1: key2
mgmt_driver: openwrt
monitoring_policy:
name: ping
parameters:
count: 3
interval: 10
actions:
failure: respawn
CP1:
type: tosca.nodes.nfv.CP.Tacker
properties:
management: true
order: 0
anti_spoofing_protection: false
requirements:
- virtualLink:
node: VL1
- virtualBinding:
node: VDU1
CP2:
type: tosca.nodes.nfv.CP.Tacker
properties:
order: 1
anti_spoofing_protection: false
requirements:
- virtualLink:
node: VL2
- virtualBinding:
node: VDU1
CP3:
type: tosca.nodes.nfv.CP.Tacker
properties:
order: 2
anti_spoofing_protection: false
requirements:
- virtualLink:
node: VL3
- virtualBinding:
node: VDU1
VL1:
type: tosca.nodes.nfv.VL
properties:
network_name: net_mgmt
vendor: Tacker
VL2:
type: tosca.nodes.nfv.VL
properties:
network_name: net0
vendor: Tacker
VL3:
type: tosca.nodes.nfv.VL
properties:
network_name: net1
vendor: Tacker