Clean-up of gerrit: move completed features to right release folder

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

diff --git a/Control_of_LCM_operations_over_a_NS_instance b/Control_of_LCM_operations_over_a_NS_instance
deleted file mode 100644 (file)
index 895caf5..0000000
--- a/Control_of_LCM_operations_over_a_NS_instance
+++ /dev/null
@@ -1,44 +0,0 @@
-# Control of LCM operations over a NS instance #
-
-## Proposer ##
-- Gerardo Garcia (Telefonica)
-- Alfonso Tierno (Telefonica)
-- Francisco Javier Ramon (Telefonica)
-
-## Type ##
-**Feature**
-
-## Target MDG/TF ##
-NBI, LW-UI, osmclient
-
-## Description ##
-The set of operations that can be done over a NS instance is the following:
-- Initiate
-- Update
-- Scale
-- Terminate
-- Action/primitive
-
-While running an operation over a NS instance, other operation calls might
-arrive to OSM and a mechanism is necessary to control how to deal with these
-coming operations while in the middle of a previous transaction.
-
-Since most probably there will be several consumers of the NBI, the natural
-mechanism is not allowing an operation to be executed if another operation
-arrives in the middle of the transaction. The LCM module will be in charge of
-that since it is the module involved in all LCM operations over a NS,
-originated from both NBI or other internal modules.
-
-There is a special case that should be handled in a different way: the
-"terminate" operation. In this case, two behaviours are possible:
-- Reject the operation while in the middle of a previous transaction
-- Force the termination of the NS instance, forcing the end of previous
-transactions.
-
-An appropriate modeling of the NB API call should allow both cases.
-
-## Demo or definition of done ##
-This demo could work:
-- A first action will be executed over a NS instance. It will succeed.
-- A second action will be executed while in the middle of the transaction. It
-will fail. The status could be checked from the NBI (LW-UI and client)

diff --git a/Release5/Basic_functionality_for_OSM_Performance_Management_in_LW-UI.md b/Release5/Basic_functionality_for_OSM_Performance_Management_in_LW-UI.md
deleted file mode 100644 (file)
index 8ff96fa..0000000
--- a/Release5/Basic_functionality_for_OSM_Performance_Management_in_LW-UI.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Basic functionality for OSM Performance Management in LW-UI #
-
-## Proposer ##
-Francesco Lombardo
-Stefano Salsano
-
-## Type ##
-**Feature**
-
-## Target MDG/TF ##
-LW-UI
-
-## Description ##
-The goal is to implement in the LW-UI new actions for the NS instances
-exploiting the NBI calls for performance and fault management. This includes:
-* Alarm creation
-* One-time metric export
-* Request for starting continuous metric export
-* Request for stopping continuous metric export
-
-No impact is expected in other modules.

diff --git a/Release5/Control_of_LCM_operations_over_a_NS_instance b/Release5/Control_of_LCM_operations_over_a_NS_instance
new file mode 100644 (file)
index 0000000..895caf5
--- /dev/null
+++ b/Release5/Control_of_LCM_operations_over_a_NS_instance
@@ -0,0 +1,44 @@
+# Control of LCM operations over a NS instance #
+
+## Proposer ##
+- Gerardo Garcia (Telefonica)
+- Alfonso Tierno (Telefonica)
+- Francisco Javier Ramon (Telefonica)
+
+## Type ##
+**Feature**
+
+## Target MDG/TF ##
+NBI, LW-UI, osmclient
+
+## Description ##
+The set of operations that can be done over a NS instance is the following:
+- Initiate
+- Update
+- Scale
+- Terminate
+- Action/primitive
+
+While running an operation over a NS instance, other operation calls might
+arrive to OSM and a mechanism is necessary to control how to deal with these
+coming operations while in the middle of a previous transaction.
+
+Since most probably there will be several consumers of the NBI, the natural
+mechanism is not allowing an operation to be executed if another operation
+arrives in the middle of the transaction. The LCM module will be in charge of
+that since it is the module involved in all LCM operations over a NS,
+originated from both NBI or other internal modules.
+
+There is a special case that should be handled in a different way: the
+"terminate" operation. In this case, two behaviours are possible:
+- Reject the operation while in the middle of a previous transaction
+- Force the termination of the NS instance, forcing the end of previous
+transactions.
+
+An appropriate modeling of the NB API call should allow both cases.
+
+## Demo or definition of done ##
+This demo could work:
+- A first action will be executed over a NS instance. It will succeed.
+- A second action will be executed while in the middle of the transaction. It
+will fail. The status could be checked from the NBI (LW-UI and client)

diff --git a/Release6/Basic_functionality_for_OSM_Performance_Management_in_LW-UI.md b/Release6/Basic_functionality_for_OSM_Performance_Management_in_LW-UI.md
new file mode 100644 (file)
index 0000000..8ff96fa
--- /dev/null
+++ b/Release6/Basic_functionality_for_OSM_Performance_Management_in_LW-UI.md
@@ -0,0 +1,21 @@
+# Basic functionality for OSM Performance Management in LW-UI #
+
+## Proposer ##
+Francesco Lombardo
+Stefano Salsano
+
+## Type ##
+**Feature**
+
+## Target MDG/TF ##
+LW-UI
+
+## Description ##
+The goal is to implement in the LW-UI new actions for the NS instances
+exploiting the NBI calls for performance and fault management. This includes:
+* Alarm creation
+* One-time metric export
+* Request for starting continuous metric export
+* Request for stopping continuous metric export
+
+No impact is expected in other modules.