From 9208eb1e0f4b44e7e9ddaf05642c3cfadd61e95b Mon Sep 17 00:00:00 2001 From: shentao Date: Sun, 12 Nov 2017 09:36:51 +0800 Subject: Update usecase-ui docs Change-Id: I55065209062d721cfdaea8310854f2cfd4e7e446 Issue-Id: USECASEUI-57 Signed-off-by: shentao --- docs/platform/administration.rst | 28 ---------------------------- 1 file changed, 28 deletions(-) (limited to 'docs/platform/administration.rst') diff --git a/docs/platform/administration.rst b/docs/platform/administration.rst index 977e024e..3b9f75c8 100644 --- a/docs/platform/administration.rst +++ b/docs/platform/administration.rst @@ -3,31 +3,3 @@ Administration -------------- - -It is not hard to manage Holmes becasue it's been dockerized and split into two dockers. One is for rule management and the other for engine management. - -Processes / Dockers -^^^^^^^^^^^^^^^^^^^ - -For both of the dockers of Holmes, there's only one process running during the run time. But the rule management docker sort of relies on the enginemanagement docker. Once the engine management module is stopped, the whole Holmes will malfunction because the Drools engine which is managed by the engine management module is the core component of Holmes. - -Holmes mainly consists of two dockers: - -* Rule Management Docker - -* Engine Management Docker - -Actions -^^^^^^^ - -All actions performed on the Holmes modules are docker-based. - -* Create a Container: ``sudo docker run [OPTIONS] IMAGE [COMMAND] [ARG...]`` - -* Kill a Container: ``sudo docker kill [OPTIONS] CONTAINER [CONTAINER...]`` - -* Stop a Container: ``sudo docker stop [OPTIONS] CONTAINER [CONTAINER...]`` - -* Start a Container: ``sudo docker start [OPTIONS] CONTAINER [CONTAINER...]`` - -* Restart a Container: ``sudo docker restart [OPTIONS] CONTAINER [CONTAINER...]`` -- cgit 1.2.3-korg