summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorGuangrongFu <fu.guangrong@zte.com.cn>2017-10-10 21:58:20 +0800
committerGuangrongFu <fu.guangrong@zte.com.cn>2017-10-10 21:58:20 +0800
commitf5a25bfcba09ba5443e3c3bc130ded015b0e2b3a (patch)
tree2b447d4be5d08bc23ebd1edc0a7e07681fcb43a1 /docs
parent6919750fe2f8c1193dde3ec7f8e8891c39b17abd (diff)
Add Consumed APIs
Change-Id: Idaba08ae077d76fc00ab13205e6722fb3ad26e08 Issue-ID: HOLMES-66 Signed-off-by: GuangrongFu <fu.guangrong@zte.com.cn>
Diffstat (limited to 'docs')
-rw-r--r--docs/platform/consumedapis.rst48
1 files changed, 47 insertions, 1 deletions
diff --git a/docs/platform/consumedapis.rst b/docs/platform/consumedapis.rst
index 5124ec4..d7ce362 100644
--- a/docs/platform/consumedapis.rst
+++ b/docs/platform/consumedapis.rst
@@ -4,4 +4,50 @@
Consumed APIs
-------------
-In the Amsterdam release, Holmes does not consume any APIs provided by other ONAP components.
+In the Amsterdam release, Holmes mainly depends on the APIs provided by DCAE, A&AI, DMaaP and MSB.
+
+DCAE
+^^^^
+
+Holmes uses DCAE APIs to fetch the information of the microservices that are registered to the DCAE Consul via the Config Binding Service provided by DCAE. The definition of the APIs could be found at `Config Binding Service APIs <https://wiki.onap.org/download/attachments/13599708/cb.html?version=1&modificationDate=1503378245000&api=v2>`_.
+
+A&AI
+^^^^
+
+In order to get the correlation between different alarms with the help of the topological information provided by A&AI. Holmes needs to call the A&AI APIs. Generally, we have to query the information of VNFs, VMs and the corresponding relation between resources from different layers. The following APIs are invoked by Holmes.
+
+#. Query a VNF by name:
+ ``/aai/v11/network/generic-vnfs/generic-vnf?vnf-name={vnf-name}``
+
+#. Query a VNF by ID:
+ ``/aai/v11/network/generic-vnfs/generic-vnf?vnf-id={vnf-id}``
+
+#. Query a VM by name:
+ ``/aai/v11/search/nodes-query?search-node-type=vserver&filter=vserver-name:EQUALS:{vserver-name}``
+
+#. Query a VM by ID:
+ ``/aai/v11/search/nodes-query?search-node-type=vserver&filter=vserver-id:EQUALS:{vserver-id}``
+
+More details could be found at `A&AI APIs <https://wiki.onap.org/pages/viewpage.action?pageId=13598793>`_.
+
+DMaaP
+^^^^^
+
+Holmes fetches VES data from DMaaP and publishes the control loop event back to DMaaP. The related APIs are:
+
+#. Subscribing:
+ ``events/{topic}/{consumergroup}/{consumerid}``
+
+#. Publishing:
+ ``/events/{topic}``
+
+More details could be found at `DMaaP APIs <https://wiki.onap.org/display/DW/DMaaP+API>`_.
+
+MSB
+^^^
+
+MSB is a key component that Holmes depends on. Almost all communications between Holmes and other components are performed using MSB as a proxy. In order to utilize the service registration and discovery functions provided by MSB, Holmes has to register itself to MSB in advance.
+
+Service Registration: ``/api/microservices/v1/services``
+
+More details could be found at `MSB APIs <https://wiki.onap.org/display/DW/Microservice+Bus+API+Documentation>`_.