From e2ceeb47c1c83bbb3e1b741bfc6fca052ca758fd Mon Sep 17 00:00:00 2001 From: garciadeblas Date: Wed, 27 Jun 2018 09:33:32 +0100 Subject: [PATCH] Re-enable NS primitives Change-Id: I15c9a8de7ae8055696d7040df0cf4fa6532d699d --- Release7/Re-enable_NS_primitives.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 Release7/Re-enable_NS_primitives.md diff --git a/Release7/Re-enable_NS_primitives.md b/Release7/Re-enable_NS_primitives.md new file mode 100644 index 0000000..e675e01 --- /dev/null +++ b/Release7/Re-enable_NS_primitives.md @@ -0,0 +1,27 @@ +# Re-enable NS primitives # + +## Proposer ## +Adam Israel +Gerardo Garcia + +## Type ## +**Feature** + +## Target MDG/TF ## +IM, LCM, N2VC, NBI, osmclient + +## Description ## +With the new OSM internal architecture, support of NS primitives based on +scripts, offered in the past by the SO, has disappeared. Enabling again NS +primitives is required to allow day-1 and day-2 operations over NS. + +Due to the need to implement it from scratch, it is better to follow an approach +for NS primitives similar to VNF so that the same procedures and code could +be used. Moreover, similar constructs for VNF and NS primitives enable a +natural path for nesting NS, where a NS can be considered as a VNF building +block to construct other NS. In this regard, the IM changes for NS primitives +(primitives, charms, relations) should be as similar as possible to the ones +currently present in the VNFD and VNFR IM. + +## Demo or definition of done ## +To be added. -- 2.25.1