VNF Components in Tacker

Agenda

Introduction

Why VNFC ??

Different drivers to implement VNFC in Tacker.

Quick Demo

Open Discussion

Introduction

● VNF Provider models the VNF into various software components called as VNF Components.

● In the current state, Tacker depends on pre-built images in which Network function is embedded to build the VDUs.

● VNFs can be built from one or more VNFCs

Why VNFC ??

● To use vendor specific installation procedures to build network function.

● Loose coupling between image and network function which avoid dependency on the underlying image.

● Easy to upgrade the VNF.

Different drivers to implement VNFC.

1.Cloud Init

2.Heat Software Deployment

3.SSH Driver

Cloud Init

Tacker can leverage the Heat Software Config feature to achieve VNF components support in Tacker.

Pros :

Most of the cloud images have cloud-init installed.

Cons :

Hard to upgrade the VNFs on the fly.

Heat Software Deployment

Tacker can leverage the Heat Software Deployment feature to achieve VNF components support in Tacker.

Pros :

Facilitates the upgrade functionality of the VNF.

Cons :

Heat agents needs to be installed as a prerequisite.

SSH Driver

Introducing SSH driver in Tacker is nice to have feature where in tacker will have complete control on what needs to be installed as software component to bring up a VNFC.

Pros :

Facilitates the easy upgrade of the VNFs

Cons :

Credentials storage and security of VDU is pain area.

Demo

1.Instantiate a VNF using Heat Software Deployment.

2.Instantiate a VNF using SSH Driver.

Open Discussion

- Improvements & suggestions.

- Thoughts about other drivers.

- Future scope of VNFC.