This patch attaches already created volume to vnf using volume id. The existing volume id can be added to tosca.nodes.BlockStorage node, in this case, no new volume will be created while vnf deployment. Implementation: * Set tosca.nodes.BlockStorage.Tacker "size" required as false, this override property definition mention in tosca.nodes.Storage.BlockStorage present in tosca parser. Please refer [1] for tosca.nodes.Storage.BlockStorage details. * Add a local dictionary to store volume id present in tosca.nodes.BlockStorage.Tacker. This dictionary is use in to determine cinder volume mapping. Additionally update block_storage_usage_guide.rst with changes required to attach existing volume. Added cinderclient in test_requirement for functional test case. Add release notes for feature. [1]: http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/csprd01/TOSCA-Simple-Profile-YAML-v1.2-csprd01.html Change-Id: If5d386a64f98603de843f96287c1e296ae6a2e1f Implements: blueprint attach-existing-volume
3.4 KiB
3.4 KiB
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.
Prerequisites
To have persistent volume support to VDUs, we must enable cinder service in addition to the other services needed by Tacker.
VNFD Changes
There are two steps to have volume attached to VDU:
- Create volume or Use an existing volume.
- Attach Volume to VDU
Create Volume
To add volume, we need to add the below node to the VNFD:
VB1:
type: tosca.nodes.BlockStorage.Tacker
properties:
size: 1 GBUse 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_volAttach 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: VB1With 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