Choose which initial/terminate primitives are to be executed within an NSD

Proposers

• Pedro Escaleira (IT)

Description

This feature is based on the idea of reusing the same VNFD among similar VNFs, which only differ on some of the initial/terminate primitives they have. For example, imagine I want to deploy a Kubernetes cluster through an NS, whose VNFs are the control plane and workers. However, I want to have one worker with Docker and another with containerd, i.e., a distinct container runtime among different nodes. Their software installation process is very similar, but on one I have to have some commands to install Docker while on the other different ones to install containerd. At the moment, if I want something like this, I probably need to create two distinct VNFDs, whose only difference is in one initial primitive (one will have a primitive to install Docker, while the other one to install containerd). Therefore, it would be much easier for someone to have the same VNFD for both, and simply exclude one or specify the initial primitives within the NSD.

Demo or definition of done

When we are able to successfully exclude an initial/terminate primitive within the NSD. Also, we need to be able to, instead of just excluding one or multiple primitives, have a list of the only primitives to be executed.