juju/paxos
juju/paxos
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update README

Browse Source
This commit is contained in:
Julien CLEMENT 2020-05-06 19:13:00 +02:00
parent 53d36d8569
commit 60772b4db1
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -31,18 +31,18 @@ A C++ compiler I guess
### Launch ### Launch
You must then launch the binary by putting a configuration file in argument You must then launch the binary by putting a configuration file in argument and a server name
```shell=zsh ```shell=zsh
./paxos {config} ./paxos {config} {name}
``` ```
### Configuration ### Configuration
You can find multiple configuration files in the repository already done for you, they are pretty straight forward to understand. You can find multiple configuration files in the repository already done for you, they are pretty straight forward to understand.
Let's say you want to distribute your system on 2 server, you have to launch 2 instances of the binary each with its configuration file. The configuration file contains informations on all the others servers and also about itself. Let's say you want to distribute your system on 2 server, you have to launch 2 instances of the binary each with the same configuration file but each with a distinct name. The configuration file contains informations on all the servers composing the system.
A boolean ("self") in the configuration allows to know if a server corresponds to the actual instance you launched or to a distant server. This boolean must be the only difference in the configuration of all your instances. The second argument you are giving in the command line is the name of the server that THIS instance represents.
The server with "self" as true, will have its specified ip and port binded for listening, the others are simply the other servers composing your system (which also binded their corresponding ip/port in their respective instances). The server with a name equal to the one in the command line, will have its specified ip and port binded for listening, the others are simply the other servers composing your system (which also binded their corresponding ip/port in their respective instances).
### Use ### Use