forked from sonata-nfv/tng-sdk-benchmark
-
Notifications
You must be signed in to change notification settings - Fork 6
NSD YAML File Structure
Bhuvan Sharma edited this page Dec 3, 2019
·
1 revision
nsd:nsd-catalog:
nsd:
- constituent-vnfd:
- member-vnf-index: 1
vnfd-id-ref: {{vnfd_id: a vnfd with this vnfd id must exist}}
description: {{Your description of this NSD}}
id: {{nsd_id}}
name: {{nsd_name}}
short-name: {{nsd_short_name: it will be displayed in OSM NSD list}}
vendor: ''
version: '1.0'
vld:
- id: {{mgmt_vld_id}}
mgmt-network: 'true'
name: {{mgmt_vld_name}}
short-name: {{mgmt_vld_id}}
type: ELAN
vim-network-name: mgmt
vnfd-connection-point-ref:
- member-vnf-index-ref: 1
vnfd-connection-point-ref: eth1-mgmt
vnfd-id-ref: {{vnfd_id}}
- id: {{data_vld_id}}
name: {{data_vld_name}}
short-name: {{data_vld_short_name}}
type: ELAN
vnfd-connection-point-ref:
- member-vnf-index-ref: 1
vnfd-connection-point-ref: eth0-data
vnfd-id-ref: {{vnd_id}}
- The variables which can be renamed are specified as {{___}}.
- You can add more VNFDs in "constituent-vnfd" with different "member-vnf-index" and same/different "vnfd-id-ref".
- For every VNFD, you need to join them with both "data" and "mgmt" VLD
You can take a look at an example NSD here
tng-bench --generator osm