Support for 802.1q trunk modeling at VNFDs

Proposers

• Gianpietro Lavado (Whitestack)

Description

Some VNFs need to expose more than 8 VLANs in a provider network, which are not supported as individual VM interfaces in most VIM. VNF vendors recommend the use of the trunk feature to be enabled at the VIM level, so it exposes a 802.1q connection point to the VM. It is available on OpenStack, as shown here.

The objective of this feature is to be able to define the VNFD descriptor in a way it can model a Connection Point (CP) in trunk-mode, with a "parent-port" and "sub-ports" that support the definition of segmentation-ids.

ETSI SOL006 data model supports this definition since v3.3.2. Details can be seen in this v3.5.1 repository.

The suggestion is to implement this feature as part of the migration to v3.5.1 or v3.6.1.

The necessary configuration inside the VM to use different VLANs will not be part of this feature.

Demo or definition of done

A robot test will be created to test the following:

• The VNF will include at least one connection defined in "trunk mode" in the descriptor, along with the parent-port and sub-ports details.
• The instantiaiton will lead to the creation of VMs that leverage the trunking feature of OpenStack, completely configured at that level.
• A connectivity test between two VNFs with ping over the same VLAN will be done.