Support of multi-VDU VNFs

Change-Id: I5dcffab568053151df9a2e0d37cda7e1cec359f7
Signed-off-by: garciadeblas <gerardo.garciadeblas@telefonica.com>

diff --git a/Release3/Support_of_multi-VDU_VNFs.md b/Release3/Support_of_multi-VDU_VNFs.md
new file mode 100644 (file)
index 0000000..38c92d8
--- /dev/null
+++ b/Release3/Support_of_multi-VDU_VNFs.md
@@ -0,0 +1,32 @@
+# Support of multi-VDU VNFs #
+
+## Proposer ##
+- Gerardo Garcia (Telefonica)
+- Alfonso Tierno (Telefonica)
+- Francisco Javier Ramon (Telefonica)
+
+## Type ##
+**Feature**
+
+## Target MDG/TF ##
+SO, VCA
+
+## Description ##
+Many common use cases involve VNFs that are composed of several types of VDUs 
+that need to be scaled and operated independently but still belong to the same 
+VNF and, hence, need to be completely described in the VNF Package, not at NS 
+level.
+
+Some common examples are composite VNFs -such as IMS or EPC- or simple but 
+decomposed VNFs, such as a vRouter with control and data plane that are 
+intended to run in separate VMs.
+
+## Demo or definition of done ##
+- A VNF Package of a VNF composed of more than one type of VDUs (e.g. 2 types 
+of VNUs: user and data plane) is successfully onboarded in the system. The set 
+of primitives available is unified at VNF level.
+- The VNF is properly deployed, with the VMs interconnected as specified in the 
+descriptor and the VNF as a whole can be operated with VNF primitives.
+
+**This feature might obsolete feature #655 _partially_: 
+https://osm.etsi.org/gerrit/#/c/655/**
\ No newline at end of file