From: kasar <pkasar@vmware.com>
Date: Mon, 29 Apr 2019 09:32:07 +0000 (-0700)
Subject: Collection of VCD/VIO VIM metrics by OSM
X-Git-Url: https://osm.etsi.org/gitweb/?a=commitdiff_plain;h=a9c8f56af2e05bb8c29b1df558d301479026c145;p=osm%2FFeatures.git

Collection of VCD/VIO VIM metrics by OSM

Change-Id: I00844d0a3877576cd52fcdccb80337c8c490f994
Signed-off-by: kasar <pkasar@vmware.com>
---

diff --git a/Release6/Collection_of_VCD_VIO_VIM_metrics_by_OSM b/Release6/Collection_of_VCD_VIO_VIM_metrics_by_OSM
new file mode 100644
index 0000000..2b87871
--- /dev/null
+++ b/Release6/Collection_of_VCD_VIO_VIM_metrics_by_OSM
@@ -0,0 +1,20 @@
+# Collection of VCD/VIO VIM metrics by OSM #
+
+## Proposer ##
+- Prakash Kasar (VMware)
+
+## Type ##
+**Feature**
+
+## Target MDG/TF ##
+MON
+
+## Description ##
+OSM should be able to collect VIM metrics from VCD/VIO through vROPS.
+Just as with OpenStack, it should map OSM metrics to the corresponding
+metric in the VIM and get the corresponding metric for VDUs with nfvi
+monitoring params defined in the VNFD, and then inject them in Prometheus.
+
+## Demo or definition of done ##
+OSM collects automatically metrics defined in the VNFD for VNFs deployed
+over VCD/VIO.