X-Git-Url: https://osm.etsi.org/gitweb/?a=blobdiff_plain;f=Release3%2FSupport_of_multi-VDU_VNFs.md;fp=Release3%2FSupport_of_multi-VDU_VNFs.md;h=0000000000000000000000000000000000000000;hb=4d22e84b474a80ec41487f2ea2758379c71206ae;hp=38c92d86872671e7de2950f73925a39daa24596c;hpb=434f30de30cf2e4361ba2163a3c121345ade6a33;p=osm%2FFeatures.git

diff --git a/Release3/Support_of_multi-VDU_VNFs.md b/Release3/Support_of_multi-VDU_VNFs.md
deleted file mode 100644
index 38c92d8..0000000
--- a/Release3/Support_of_multi-VDU_VNFs.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# 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