Interface name collisions among VNFs

[mpeuster]

Using the same interface names inside the VNF containers can lead to problems with VNFs that need to run in privileged mode, like the vTC (PF_RING).

A workaround is to modify the VNFDs to not have duplicated interface names (e.g., not have input or output twice in a service).

We should think about having a better naming scheme (e.g. include the vnf_id in the interface name). Not sure how long these names are allowed to be?

This is an issue that should be investigated after the Y1 demo.