From: Francisco-Javier Ramón Salguero <javier.ramon@telefonica.com>
Date: Mon, 4 Feb 2019 03:00:10 +0000 (+0100)
Subject: Instantiation in VIMs with more than one physnet
X-Git-Url: https://osm.etsi.org/gitweb/?p=osm%2FFeatures.git;a=commitdiff_plain;h=cb970c08ec05a749ba1490ea78d95b488584bd72

Instantiation in VIMs with more than one physnet

Change-Id: I873a34765878b42f1f932a82945227d80d6512f0
Signed-off-by: Francisco-Javier Ramón Salguero <javier.ramon@telefonica.com>
---

diff --git a/Release6/Instantiation in VIMs with more than one physnet.md b/Release6/Instantiation in VIMs with more than one physnet.md
new file mode 100644
index 0000000..7cf8264
--- /dev/null
+++ b/Release6/Instantiation in VIMs with more than one physnet.md	
@@ -0,0 +1,45 @@
+# Instantiation in VIMs with more than one physnet
+
+## Proposer
+
+- Gerardo Garcia (Telefonica)
+- Alfonso Tierno (Telefonica)
+- Francisco Javier Ramon (Telefonica)
+
+## Type
+
+**Feature**
+
+## Target MDG/TF
+
+RO, CLI (optional)
+
+## Description
+
+In environments where some physical redundancy is required in terms of 
+networking, it is common the use of schemas with more than one switch upstream, 
+dividing the physical medium in groups of physical interfaces depending of the 
+upstream switch they are attached. In order to facilitate a sensible management 
+of these physical interfaces belonging to different "redundancy groups" by the 
+VIM, there is the possibility to classify them into the so-called 'physnets', 
+so that the VIM can leverage on that physical redundacy if needed.
+
+While this feature should not create a fundamental change in OSM operation or 
+the way its modelling works, and it is a fact that OSM can work with these 
+environments, it is also true that it works today with some limitations when 
+SDN Assist is in place. Thus, in a VIM with multiple physnets, only one can be 
+registered today when configuring a VIM target in OSM, leading to potential 
+underuse of resources (usually, by one half). Furthermore, when those physnets 
+obbey to some kind of physical active-active scheme, OSM cannot leverage on 
+this information to make NS/NSI deployments more reliable.
+
+This feature intends to solve the limitations described above.
+
+## Demo or definition of done
+
+With a VIM with multiple physnets, check that it is possible:
+
+- Register the VIM with all its physnets when defining a VIM target in OSM with 
+SDN Assist.
+- Deploy a large NS requiring SDN Assist in such a VIM so that no interfaces 
+are excluded because of the physnet they belong.