New Features¶

• Support multi-version of RESTfulAPI. The client can useboth VNF LCM API “1.3.0” and “2.0.0” defined by ETSI NFV.

• Add new RESTful APIs of List VNF LCM API versionsand Show VNF LCM API versions based on ETSI NFV specifications.They enable the client to retrieve supported versions of VNF LCM API.

• Add the following new version of RESTful APIsbased on ETSI NFV specifications.Version “2.0.0” API of Create VNF, Delete VNF,Instantiate VNF, Terminate VNF, List VNF, Show VNF,List VNF LCM operation occurrence, Show VNF LCM operation occurrence,Create subscription, List subscription, and Show subscription are added.

• VNF LCM API “2.0.0” provides a new type of userdata scriptand utility functions to describe it.They enable the user to freely operate HEAT to meet the uniquerequirements of VNF.

• 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.

• Functions to enable the use of Docker private registry images in aKubernetes Cluster environment. We provide the sample of MgmtDriverwhich can deploy Docker private registry VNF for Kubernetes clusterbefore deploying Kubernetes cluster VNF, and deploy Kubernetes clusterVNF that can support both the Docker private registry created aboveand any others created outside of Tacker.

  Instantiate operation for Kubernetes cluster with MgmtDriver:MgmtDriver configures connections with Docker private registries onnewly created all Master/Worker VMs.

  Scale-out operation for Kubernetes cluster Worker-nodes with MgmtDriver:MgmtDriver configures connections with Docker private registries onnewly created Worker VMs.

  Heal operation for the entire Kubernetes cluster with MgmtDriver:MgmtDriver configures connections with Docker private registries onthe created all Master/Worker VMs.

  Heal operation for a single node in Kubernetes cluster with MgmtDriver:MgmtDriver configures connections with Docker private registries onthe created Master/Worker VM.

• Add new interface for Kubernetes VIM to handle Helm chart. It enables Usersto include Helm chart files as MCIOP in their VNF Packages, to instantiateand to terminate CNF with them.And update sample of MgmtDriver to install and configure Helm package forusing Helm cli command in the deployed Kubernetes cluster VNF, and torestore the registered helm repositories and charts after the master node ishealed.

• 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 deploy a Kubernetes cluster. It can usekubespray as Ansible playbooks to install Kubernetes cluster VNF,and also install and configure HAproxy load balancer for the Kubernetescluster. We also provide a user guide to help users understand how touse this feature.

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

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

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

• Support deploying Kubernetes cluster VNF which has a storage server withCinder volume. This feature enables users to deploy CNF which hasPersistentVolume on it. The following changes are added for MgmtDriver.

  • Create a storage server VM with Cinder volume.

  • Expose Cinder volume as NFS shared directories in the storage server.

  • Register NFS shared directories as Kubernetes PersistentVolumes.

  • Install NFS client on newly created Master/Worker VMs in all LCMoperations.

Upgrade Notes¶

• Update cirros image from 0.4.0 to 0.5.2.

• Change default network backend driver to OVN intacker/devstack forinstallation and.zuul.yaml for functional tests.

Deprecation Notes¶

• Drop sqlalchemy-filters from tacker. We’ve been depending onsqlalchemy-filters a little, but it can be replaced with original code intacker as alternative. We can catch up with a change in SQLAlchemy withoutwaiting for a update sqlalchemy-filters after then, update our codeinstead quickly.

Bug Fixes¶

• Fixesbug 1923360, add missing endpoint URL in each response of vnflcmoperation.

• Fixesbug 1923425, add interface into vim connection info.

• Fixesbug 1923478, correct incomplete URL in notification of vnflcm opocc.

• Fixesbug 1923528, dropWorkerService class which spawns childservice proceses with given numberapi_worker as a config value.Without this fix, it results in that the worker processes, the number ofthem isapi_worker, spawn each child processes unintendedly.api_worker is designed just for the number of workers, and not fortheir children.

• Fixesbug 1923540, fix permission of uploaded files withvnfpackageupload command are changed to644 unexpectedly whileit should be755. It’s corrected while extracting.

• Fixesbug 1924214, fix a resourceOS::Heat::AutoScalingGroup markedas unhealthy unexpectedly. Marking only forOS::Nova::Server iscorrect.

• Fixesbug 1930571, add missing propertyvnfConfigurablePropertiesin the result of CLI commands, such asopenstackvnflcmshow.

Other Notes¶

• RevisedInstallation Guide.

  • Added a table that shows hardware requirements toETSI Install viaDevstack.

• RevisedUser Guide.

  • Classified Legacy Tacker documents and ETSI NFV-SOL Tacker documents.

  • Added diagrams and overviews of theETSI NFV-SOL Tacker Use Cases.

  • AddedGetting Started with ETSI NFV-SOL Tacker.

  • Removed documents that seem to be no longer necessary.