Add more documentation

Add tutorials;
Add terminology;
Rewrite the dashboard operations;
Add more screenshots.

Change-Id: I8677d5a036f053ae30cf01695aefaac3c9f7467d
Signed-off-by: Baohua Yang <yangbaohua@gmail.com>

Author: yeasy

README.md

@@ -32,8 +32,9 @@ You can also find more [scenarios](docs/scenario.md).
 ## Documentation
 
 ### Operational Docs
-* [Installation & Deployment](docs/deployment.md)
-* [Dashboard](docs/dashboard.md)
+* [Installation & Deployment](docs/install.md)
+* [Terminologies](docs/terminology.md)
+* [Tutorial](docs/tutorial.md)
 * [Scenarios](docs/scenario.md)
 * [Production Configuration](docs/production_config.md)
 

docs/arch.md

@@ -2,11 +2,7 @@
 
 Here we discuss the architecture design for the mangement services on the Master node.
 
-## Terminology
-* Cluster | Chain: A blockchain with unique access API address, including several peer nodes. May support Hyperledger Fabric, SawthoothLake and Iroha.
-* Host: A resource server, usually it can be a naive Docker host or a Swarm cluster.
-* Master Node: Running the cello platform, to manage the compute nodes.
-* Compute | Worker Node: The servers to have blockchains running inside.
+
 
 ## Philosophy and principles
 The architecture will follow the following principles:

docs/dashboard.md

@@ -1,50 +1,81 @@
 # Dashboard
 
-System operators can utilize dashboard service to check system status or change configurations.
+By default, the dashboard will listen on port `8080` at the Master Node.
+
+The left panel gives quick link to various functions, including `overview`, `system status`, `Hosts`, `Active Clusters`, `Inused Clusters`, `Release History` and `About`.
+
+| Name | URL | Function |
+| --- | --- | --- |
+| Overview | `/index` | See a high-level overview on system status |
+| System Status | `/stat` | See statistics on the system |
+| Hosts | `/hosts` | Operate on the hosts managed by the system |
+| Active Clusters | `/clusters?type=active` | Operate on existing running chains in the pool |
+| Inused Clusters | `/clusters?type=inused` | Operate on user occupied chains in the system |
+| Released History  | `/clusters?type=released` | See cluster releasing history data |
 
-The dashboard service will listen on port `8080`.
 
 ## Overview
 
-URL: `/index`.
+![Dashboard Overview](imgs/dashboard_overview.png)
+
+
+The default overview page show the overall status of the system, e.g., how many hosts are deployed within the system, how many clusters are running on those hosts. And there are status numbers for both hosts and clusters.
 
-See a high-level overview on system status.
 
-## System Status
+## System Status Page
 
-URL: `/stat`.
+![dashboard status](imgs/dashboard_status.png)
 
-See statistics on the system.
+The system status page shows the host and cluster statistics in terms of types and active/inactive in the system.
 
 ## Hosts
 
-URL: `/hosts`.
+![dashboard hosts](imgs/dashboard_hosts.png)
+
+In Host page, you can manage all the existing hosts in the pool, and add new hosts. The host shows its `Type` (e.g., SINGLE for Native Docker, or SWARM for Docker Swarm), `Status` (active or not) , `Chains` (How many chains running in the host), `Cap` (Capacity) and `Log Config` (level, receiver). Those non-schedulable host will have a grey line
+
+In the Action dropdown menu, you can
+
+* Fillup: Fill a host with chains till it's full `capacity`.
+* Clean: Clean all unused chains at the host.
+* Config: Set configurations of the host, e.g., `name` or `capacity`. 
+* Reset: Reset everything on the host, useful when u meet problems of running chains on the host. Notice a host can be `reset` only when there's no inused chains on it.
+* Delete: Remove the host from the pool, then the system will not care about it.
+
+### Add Host
+
+You can click the `Add Host` button to add more hosts into the pool.
+
+![dashboard add-host](imgs/dashboard_add_host.png)
+
+
+## Active Chains
+
+The `Active Chains` page shows all existing running chains in the system, with their Name, Type, Status, Health, Size and Host. Those inused chains will have a grey line.
+
+
+![dashboard clusters](imgs/dashboard_clusters.png)
 
-Operate on the hosts managed by the system.
+In the Action dropdown menu, you can
 
-## Clusters_active
+* Start: Start a chain that is not running.
+* Stop: Stop a running chain to stopped status.
+* Restart: Restart a chain. 
+* Delete: Delete the chain.
+* Release: Release a user-occupuied chain back to the pool, which will be deleted later.
 
-URL: `/clusters?type=active`.
+You can click the `Add Chain` button to add more chains into the pool if there are non-full hosts.
 
-Operate on existing running chains in the pool.
+![dashboard add-cluster](imgs/dashboard_add_cluster.png)
 
-## Clusters_inused
 
-URL: `/clusters?type=inused`.
+## Inused Chains
 
-Operate on user occupied chains in the system.
+Filter out those running chains that are occupied by users.
 
-## Clusters_released
+## Release History
 
-URL: `/clusters?type=released`.
+Record all the user releasing chain history.
 
-See cluster releasing history data.
 
-## Screenshots
 
-![dashboard-main](imgs/dashboard_main.png)
-![dashboard-status](imgs/dashboard_status.png)
-![dashboard-hosts](imgs/dashboard_hosts.png)
-![dashboard-clusters](imgs/dashboard_clusters.png)
-![dashboard-add-host](imgs/dashboard_add_host.png)
-![dashboard-add-cluster](imgs/dashboard_add_cluster.png)