#3291 log: shutdown log agent when not in use

[Hieu Hong Hoang]

Currently, the log agent keeps running even if we finalize it and no more log client. We should unregister the mds of log agent in final step. Be careful when closing the mds of log agent because we could face an old problem which is mentioned in 1396.

[Hieu Hong Hoang]

commit fbcb58c1dfa384c2922f65861befa478fff7ee41 (HEAD -> develop, origin/develop, ticket-3291)
Author: hieu.h.hoang hieu.h.hoang@dektech.com.au
Date: Tue Dec 7 19:37:40 2021 +0700

log: Increase timeout in logtest [#3291]

Because the log agent have to wait for the clm node status message, increase timeout in logtest.

commit 3ad2021efdc1796406e8240c98c6da2cad99e3bc
Author: hieu.h.hoang hieu.h.hoang@dektech.com.au
Date: Fri Nov 26 11:42:18 2021 +0700

log: Shutdown log agent when not in use [#3291]

When there are no more log client in log agent, unregister mds and shutdown log agent.

commit 318d3684184f707fd2dbd2f74a2aafb149ee0334
Author: hieu.h.hoang hieu.h.hoang@dektech.com.au
Date: Sun Oct 10 18:29:17 2021 +0700

log: Introduce the initial clm node status [#3291]

When logd detected loga is up, it will send a callback message to loga.
Loga should wait for the callback message when loga was just created.
This callback helps the messages are processed in right order in logd,
unorder message was mentioned in #1396.
Following is the order of processing messages:
1. logd: agent up message
2. loga: initial clm node status message
3. logd: initial client message
4. logd: final client message
5. logd: agent down message