Current Series Release Notes

6.0.0.0rc1-31

New Features

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

  • Add new RESTful APIs of List VNF LCM API versions and 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 APIs based 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 script and utility functions to describe it. They enable the user to freely operate HEAT to meet the unique requirements of VNF.

  • Functions to enable the use of Docker private registry images in a Kubernetes Cluster environment. We provide the sample of MgmtDriver which can deploy Docker private registry VNF for Kubernetes cluster before deploying Kubernetes cluster VNF, and deploy Kubernetes cluster VNF that can support both the Docker private registry created above and any others created outside of Tacker.

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

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

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

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

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

  • MgmtDriver function configures applications provided by VNF vendors. VNF vendors can customize configuration methods for applications via MgmtDriver. These customizations are specified by “interface” definition in ETSI NFV-SOL001 v2.6.1. We provide the sample of MgmtDriver and scripts which can deploy a Kubernetes cluster. It can use kubespray as Ansible playbooks to install Kubernetes cluster VNF, and also install and configure HAproxy load balancer for the Kubernetes cluster. We also provide a user guide to help users understand how to use this feature.

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

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

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

  • Support deploying Kubernetes cluster VNF which has a storage server with Cinder volume. This feature enables users to deploy CNF which has PersistentVolume 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 LCM operations.