4.1 KiB
ETSI NFV-SOL CNF Update
This document describes how to update CNF in Tacker. Please refer to
the /user/v2/cnf/update_with_mgmt_driver/index
for how to
update CNF with Mgmt Driver in Tacker.
Prerequisites
The following packages should be installed:
- tacker
- python-tackerclient
Execute up to "Create VNF" of "Instantiate VNF" in the procedure of
/user/v2/cnf/deployment/index
.
CNF Update Procedures
As mentioned in Prerequisites, the CNF must be created before performing update.
Details of CLI commands are described in /cli/cli-etsi-vnflcm
.
For update VNF instance, you need to prepare a JSON-formatted definition file.
{
"vnfInstanceName": "sample"
}
Note
sample_param_file.json contains the VNF name as an example. The Update operation can update the following.
- vnfInstanceName
- vnfInstanceDescription
- vnfId
- vnfConfigurableProperties
- metadata
- extensions
- vnfcInfoModifications
- vimConnectionInfo
Note
The update operation can change the vimConnectionInfo
associated with an existing VNF instance. Even if update operation
specify multiple vimConnectionInfo
associated with one VNF
instance, only one of them will be used for life cycle management
operations. It is not possible to delete the key of registered
vimConnectionInfo
.
How to Update CNF
Execute Update CLI command and check the name of VNF instance before and after update. This is to confirm that the name of VNF instance has changed after update.
VNF instance name before update:
$ openstack vnflcm show VNF_INSTANCE_ID -c 'VNF Instance Name' \
--os-tacker-api-version 2
Result:
+-------------------+-------+
| Field | Value |
+-------------------+-------+
| VNF Instance Name | |
+-------------------+-------+
Update VNF can be executed by the following CLI command.
$ openstack vnflcm update VNF_INSTANCE_ID --I sample_param_file.json \
--os-tacker-api-version 2
Result:
Update vnf:431b94b5-d7ba-4d1c-aa26-ecec65d7ee53
Note
Create a parameter file that describes the resource information to be changed in advance.
VNF instance name after operation:
$ openstack vnflcm show VNF_INSTANCE_ID -c 'VNF Instance Name' \
--os-tacker-api-version 2
Result:
+-------------------+--------+
| Field | Value |
+-------------------+--------+
| VNF Instance Name | sample |
+-------------------+--------+
You can confirm that the VNF Instance Name has been changed by the update operation.
If the vnfdId
is not changed by update operation, the
current value shall be updated using the request parameter. The
following attributes are updated by performing JSON Merge Patch with the
values set in the request parameter to the current values.
- vnfConfigurableProperties
- metadata
- extensions
If the vnfdId
is requested to be changed by update
operation, the following attributes of VNF instance shall be updated in
addition to those set in the request parameters. These are updated with
the values obtained from the VNFD associated with the new vnfdId.
- vnfProvider
- vnfProductName
- vnfSoftwareVersion
- vnfdVersion
Note
In the update operation for CNF, if "Scale" or "Heal" is performed
after updating vnfdId
, the VNF package associated with the
vnfdId before the update
shall be used. Therefore, in order
to maintain the update of vnfdId
, it is necessary to
execute "Terminate VNF" once and then "Instantiate VNF".
History of Checks
The content of this document has been confirmed to work using the following VNF Package.