Leverage upper-constraints files to pin all dependencies

[holmes/rule-management.git] / docs / platform / delivery.rst

diff --git a/docs/platform/delivery.rst b/docs/platform/delivery.rst
index 27b3770..40186b6 100644 (file)
--- a/docs/platform/delivery.rst
+++ b/docs/platform/delivery.rst
@@ -5,5 +5,12 @@ Delivery
 --------
 
 Describe how functions are packaged into run-time components. For some components a block diagram may be useful.
+As mentioned in the architecture chapter, Holmes mainly comprises two modules: a rule management module and an engine management module.
 
-**TO BE DONE**
\ No newline at end of file
+* Rule Management Docker: The main operations on the rules are performed in this module. The module provides CRUD operation interfaces and is reponsible of the persistence of the rules as well.
+
+* Engine Management Docker: The Drools rules are actually deployed into the Drools engine which is embedded within the engine management module. The analysis tasks are excuted in this module as well. Alarm messages are converted to Holmes-compatible format and put into the Drools engine for analysis.
+
+* Common Library: The library hosts some supportive tools for both the rule management module and the engine management module. It is not run separately. Instead, it is introduced into the main modules of Holmes during the compile and package phase.
+
+.. image:: images/holmes-delivery.png