GuokeCui

Support the basic operation and awareness methods, then we could add more necessary convenient methods in order to support more flexible test purpose.

With PR #4311, we have found different bugs or flaws, which is the exact purpose of this service integration test framework. The related bug or flaw could be learned from...

Now, I've implemented basic features for this test framework. Next, I will continue on the simulation of network partition. The timeline seems to be longer than expected, but in the...

For network partition feature in this integration test framework, we implement logic at the side of `morpc.Client` by taking advantage of its option `morpc.WithBackendFilter`.

All the basic features were completed. There may be some necessary updates needed in order to cope with practical requirements when using this framework.

Rough design for our integration test framework: 1. Start a cluster in which `log service` and `dn service` were started according to expectation; 2. After cluster started, do some operation,...

For `log service`, we need to handle `Add`, `Remove`, `Start`, `Stop` commands. As to `dn service`, we only need to handle `Add` and `Remove`. - `Add` and `Remove` implies data...

In order to start test cluster, we should start dn and log stores first.

`dn` services depends on `log` services, we should start log services first.

## Log of testing client taking use of log extensional binding: ``` 2020/04/18 15:46:00 [20] authenticate: fail to read len data 2020/04/18 15:46:00 [20] loop: After authenticate: LastZxidSeen=30064771079, TimeOut=4000, SessionID=31960860706013185,...