When deploying the UGP VNF using a stand-alone AutoVNF instance, AutoVNF deploys the VNF based on parameters defined in a VNF configuration file.
The VNF configuration file includes parameters pertaining to the Cinder volumes required by the VNF components (VNFCs) including the Control Functions (CFs).
With this release, the CFs can be deployed using Cinder volumes previously configured in OpenStack.
To configure the CFs to use pre-existing Cinder volumes, modify the following parameters in the VNF configuration file:
infra-element-groups <element_group_name> instances <num_instances> vdus <cf_vdu_name><---SNIP--->\
<---SNIP---> instance-volume <instance_num> volume <pre_created_vol_name> type LUKS bus ide bootable false ! volume <pre_created_vol_name> type LUKS bus ide bootable true !
Each CF requires a single volume instance with two volumes identified, one bootable, the other for call detail record storage (CDR). pre_created_vol_name is the name of the volume configured in Cinder and displayed using the cinder list command in OpenStack. The details provided in this configuration are passed to the VNFM to identify the appropriate volume.