Skip to content

VNFD YAML File Structure

Bhuvan Sharma edited this page Dec 3, 2019 · 1 revision

VNFD YAML File Structure:

vnfd:vnfd-catalog:
    vnfd:
    -   connection-point:
        -   name: eth0-data
            type: VPORT
        -   name: eth1-mgmt
            type: VPORT
        description: {{Your description of the VNF}}
        id: {{vnfd_id}}
        mgmt-interface:
            cp: eth1-mgmt
        name: {{vnf_name}}
        short-name: {{vnf_short_name: it is displayed in OSM GUI VNFD List}}
        vdu:
        -   cloud-init-file: cloud-config.txt
            count: 1
            description: {{Your VDU description}}
            id: {{vdu_id}}
            image: {{image_name_from_VIM}}
            interface:
            -   external-connection-point-ref: eth0-data
                name: eth0-data
                position: 2
                type: EXTERNAL
                virtual-interface:
                    type: PARAVIRT
            -   external-connection-point-ref: eth1-mgmt
                name: eth1-mgmt
                position: 1
                type: EXTERNAL
                virtual-interface:
                    type: PARAVIRT
            name: {{vdu_name}}
            vm-flavor:
                memory-mb: {{memory in MB}}
                storage-gb: {{storage in GB}}
                vcpu-count: 1
        vendor: OSM
        version: '1.0'
        vnf-configuration:
            initial-config-primitive:
            -   name: config
                parameter:
                -   name: ssh-hostname
                    value: <rw_mgmt_ip>
                -   name: ssh-username
                    value: ubuntu
                -   name: ssh-password
                    value: osm4u
                seq: '1'

Notes

  • The variables which can be renamed are specified as {{____}}.

Important

The connection points (interfaces) will be renamed according to the position, so make sure you give "management interface" "position: 1" and "data interface" "position: 2". So the management interface will have the name "ens3" and data interface will have the name "ens4", which can further be used in development.

Reference

You can take a look at an example VNFD here