Orchestrating VNFs with attached Volumes¶
To support persistent volumes to VNF, the TOSCA NFV profile supports a new type of nodes. Tacker has now the feature of parsing of those new nodes and creation of cinder volumes which are attached to the VDUs.
To have persistent volume support to VDUs, we must enable cinder service in addition to the other services needed by Tacker.
There are two steps to have volume attached to VDU:
Create volume or Use an existing volume.
Attach Volume to VDU
To add volume, we need to add the below node to the VNFD:
VB1: type: tosca.nodes.BlockStorage.Tacker properties: size: 1 GB
Use Existing Volume¶
We can also attach an already created/existing volume with VNF by providing
volume_id in input.
topology_template: inputs: my_vol: description: volume id type: string VB1: type: tosca.nodes.BlockStorage.Tacker properties: volume_id: my_vol
Attach volume to VDU¶
Next attach the created volume to VDU as below:
CB1: type: tosca.nodes.BlockStorageAttachment properties: location: /dev/vdb requirements: - virtualBinding: node: VDU1 - virtualAttachment: node: VB1
With these additions, the new VNFD looks like below:
tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0 description: Demo example metadata: template_name: sample-tosca-vnfd 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: cirros-0.4.0-x86_64-disk availability_zone: nova mgmt_driver: noop config: | param0: key1 param1: key2 CP1: type: tosca.nodes.nfv.CP.Tacker properties: management: true order: 0 anti_spoofing_protection: false requirements: - virtualLink: node: VL1 - virtualBinding: node: VDU1 VB1: type: tosca.nodes.BlockStorage.Tacker properties: size: 1 GB CB1: type: tosca.nodes.BlockStorageAttachment properties: location: /dev/vdb requirements: - virtualBinding: node: VDU1 - virtualAttachment: node: VB1 VL1: type: tosca.nodes.nfv.VL properties: network_name: net_mgmt vendor: Tacker