Prelude¶

This release contains a new feature to attach an already created or existing volume with VNF. Enhancement to an existing feature that supports attachment of persistent volumes to VNF.

Features based on ETSI NFV specifications, REST API and data models:

• ETSI NFV-SOL003 v2.6.1: VNF Lifecycle Management(Scale VNF, Update VNFand Rollback VNF)

• ETSI NFV-SOL005 v2.6.1: Fetch VNF Package Artifacts

Kubernetes VIM is extended to use ETSI NFV-SOL based operations.The major version of resources such as Deployment, DaemonSet, StatefulSet,and ReplicaSet can be deployed as VNF with Instantiate VNF operation.

The 5.0.0 release includes new features based on ETSI NFV-SOLRelease2 specifications. The major changes are:

• Day2 operations for Cloud-native Network Function (CNF).Scale operation for CNF andHeal operation for CNF withETSI NFV-SOL003 v2.6.1 are supported.

• New MgmtDriver as preamble and postamble of VNF Lifecycle Management.<base_operation_name>_start and<base_operation_name>_end areexecuted before and after its operation according to the VNFD.

• Sample MgmtDriver for Kubernetes cluster VNF is provided to manageon-premise Kubernetes. HA Master nodes, Scaling Worker nodes, andHealing Master/Worker nodes are possible with Kube-adm.

• Error handling of VNF instance is enhanced to support Retry,Rollback, and Fail operations.

New Features¶

• This feature allows users to attach an already created or existingvolume with VNF by providing volume_id in the TOSCA template.In this case, no new volume is created while vnf deployment.

• Add placement constraints support so that the VNFM may interoperate with 3rd party NFVO, it enables to deploy each VM in the VNF after setting the zone information based on the grant response from NFVO.

• Add new RESTful APIs forScale VNF,Update VNF, andRollback VNFoperation based on ETSI NFV specifications.

• Add new RESTful APIs for subscriptions and notifications based on ETSINFV specifications. The client can use these resource to subscribe tonotifications related to VNF lifecycle management, and to query itssubscriptions.

• SetvnfPkgId to related APIs in order to expand a wide range of NFVrelated equipments. See thespec for more details.

• Add following ETSI NFV SOL003 specification compliant operationsto cooperate with 3rd-Party NFVOs as VNFM.

  • VNF package management interface to obtain VNF package information

  • Granting interface to allow the VNFM to request a grant forauthorization of a VNF lifecycle operation.

• Add new RESTful APIs for Fail VNF, Retry VNF as part of error handling operation based on ETSI NFV specifications.

• Adds Container based VNF support with ESTI NFV-SOL003 v2.6.1 VNF LifecycleManagement. Users can create, instantiate, terminate, and delete VNF onKubernetes VIM. The Kubernetes resource files are available as VNFD anduploaded as a part of VNF Package.

• MgmtDriver function configures applications provided by VNF vendors.VNF vendors can customize configuration methods for applications viaMgmtDriver. These customizations are specified by “interface” definitionin ETSI NFV-SOL001 v2.6.1. We provide the sample of MgmtDriver andscripts which can be used to deploy a Kubernetes cluster. The samplescript for deploying Kubernetes cluster can be used in two cases.One is to deploy one master node with worker nodes. Under this case,it supports to scale worker node and heal worker node. The other is todeploy a high availability cluster, there are three(or more) masternodes with worker nodes. Under this case, it supports to scale workernode and to heal worker node and master node. In all the above cases,kubeadm is used for deploying Kubernetes in the sample script. We alsoprovide a user guide to help users understand how to use this feature.

  Instantiate single master node kubernetes cluster:The Kubernetes cluster can be instantiated with VNF LifecycleManagement Interface in ETSI NFV-SOL 003 v2.6.1.

  Instantiate multi-master nodes kubernetes cluster:A Kubenrnetes cluster with a high availability (HA) configurationcan be deployed.

  Scale kubernetes worker node:Scaling operations on the Worker-nodes for the VNF includingKubernetes cluster is supported with MgmtDriver.

  Heal kubernetes master and worker nodes:Healing operations on the Master-nodes and Worker-nodes for theVNF including Kubernetes cluster is supported with MgmtDriver.

• Enable VNF vendors to customize configuration methodsfor applications via MgmtDriver. These customizationsare specified by “interface” definition in ETSINFV-SOL001 v2.6.1. With MgmtDriver, users can executepreamble and postamble of the base LCM operation.Customization of LCM itself is not supported byMgmtDriver.

• Add Container based VNF heal operation support with ETSI NFV-SOL002 andSOL003 v2.6.1 VNF Lifecycle Management. For “Heal VNFC with SOL002”, userscan heal Pod (mapped as VNFC) that is singleton or created using controllerresources such as Kubernetes Deployment, DaemonSet, StatefulSet, andReplicaSet. For “Heal VNF instance with SOL003”, users can heal entire VNFinstance by termination and instantiation of the VNF. And the VNFC resourceinformation are stored and updated for the heal operation of the Pod.

• Add Container based VNF scale operation support with ETSI NFV-SOL003v2.6.1 VNF Lifecycle Management. Users can scale the number of pod replicasmanaged by controller resources such as Kubernetes Deployment, StatefulSet,and ReplicaSet.

Upgrade Notes¶

• The default value of[oslo_policy]policy_file config option hasbeen changed frompolicy.json topolicy.yaml.Operators who are utilizing customized or previously generatedstatic policy JSON files (which are not needed by default), shouldgenerate new policy files or convert them in YAML format. Use theoslopolicy-convert-json-to-yamltool to convert a JSON to YAML formatted policy file inbackward compatible way.

Deprecation Notes¶

• Use of JSON policy files was deprecated by theoslo.policy libraryduring the Victoria development cycle. As a result, this deprecation isbeing noted in the Wallaby cycle with an anticipated future removal of supportbyoslo.policy. As such operators will need to convert to YAML policyfiles. Please see the upgrade notes for details on migration of anycustom policy files.

Bug Fixes¶

• Fixesbug 1879436. Users who build VNF packages can specify softwareimage properties likemin_disk,min_ram andsize in different unitsas mentioned in section 3.2.6.4 ofTOSCA Simple Profile in YAML Version 1.2 template.These property values are converted from various units tobyte unit andreturned inGET /vnfpkgm/v1/vnf_packages/{vnf_package_id} API response.

  Note

  For old vnf packages, the software image properties are not convertedintobyte unit.