From 812ff6ca9fcd3e629e49d4328905f33eee8ca3f5 Mon Sep 17 00:00:00 2001 From: Qiaowei Ren Date: Thu, 4 Jan 2018 13:43:33 +0800 Subject: initial code repo This patch creates initial code repo. For ceph, luminous stable release will be used for base code, and next changes and optimization for ceph will be added to it. For opensds, currently any changes can be upstreamed into original opensds repo (https://github.com/opensds/opensds), and so stor4nfv will directly clone opensds code to deploy stor4nfv environment. And the scripts for deployment based on ceph and opensds will be put into 'ci' directory. Change-Id: I46a32218884c75dda2936337604ff03c554648e4 Signed-off-by: Qiaowei Ren --- src/ceph/doc/mon/README.txt | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 src/ceph/doc/mon/README.txt (limited to 'src/ceph/doc/mon/README.txt') diff --git a/src/ceph/doc/mon/README.txt b/src/ceph/doc/mon/README.txt new file mode 100644 index 0000000..fa1bf79 --- /dev/null +++ b/src/ceph/doc/mon/README.txt @@ -0,0 +1,27 @@ +paxos-call-chain.dot describes to some detail the call chain involved in the +Paxos algorithm, paying special consideration to the messages involved. + +This information is not easily obtainable by Doxygen, as it does not follow +the call chain when messages are involved, since it becomes an async workflow. + +To obtain the graph one should run + + dot -T paxos-call-chain.dot -o paxos-call-chain. + +e.g., + + dot -Tps paxos-call-chain.dot -o paxos-call-chain.ps + +or + + dot -Tpng paxos-call-chain.dot -o paxos-call-chain.png + +It should do the trick. + +Also, for future reference, we consider that: + - boxed nodes refer to the Leader; + - elliptical nodes refer to the Peon; + - diamond shaped nodes refer to state changes; + - dotted lines illustrate a message being sent from the Leader to the Peon, + or vice-versa. + -- cgit 1.2.3-korg