Detection of VIM events not directly related to VDU infra metrics

Change-Id: Ifa31878db13ce6f7a5d16d44a4158082528a9baf

diff --git a/Release5/detection_of_vim_events_not_directly_related_to_VDU_infra_metrics.md b/Release5/detection_of_vim_events_not_directly_related_to_VDU_infra_metrics.md
new file mode 100644 (file)
index 0000000..a83a1a2
--- /dev/null
+++ b/Release5/detection_of_vim_events_not_directly_related_to_VDU_infra_metrics.md
@@ -0,0 +1,28 @@
+# Detection of VIM events not directly related to VDU infra metrics #
+
+## Proposer ##
+- Gianpietro Lavado (Whitestack)
+
+## Type ##
+**Feature**
+
+## Target MDG/TF ##
+MON
+
+## Description ##
+
+Detection of VIM events not directly related to VDU infra metrics (broken VMs,
+links/networks down, etc.)
+
+OSM should be able to detect the following VIM events:
+1. VM state change (shutdown, pause, not present, etc.)
+2. Network changes (deletion, disconnection, etc.)
+3. Volume changes (detachments, deletion, etc.)
+4. VIM status (API connectivity)
+
+## Demo or definition of done ##
+The following events should make MON throw a log related to the NS, and event in bus.
+- A VM is powered down at the VIM interface.
+- A network is disconnected from a VDU.
+- A volume is detached from a VDU.
+- The VIM API is not available.