In /grpc: A 2-fault tolerant replicated client/server chat application using gRPC
Sections:
- Setup (pull from github, required libraries, etc.)
- Startup
- Operation - gRPC
- Operation - Unit tests
Overview.
This application is a simple chat room that implements client/server connection and one-to-one client communication. It can be run on a single machine, as well as between multiple different machines. There are other functionalities in addition to sending messsages, which include listing all or a subset of users who exist in the server, login/logout, and deleting one's account. The system is both persistent (it can be stopped and re-started without losing messages that were sent during the time it was running) and 2-fault tolerant in the face of crash/failstop failures. Replication is implemented with a primary-backup architecture, where the primary server sends changes to state along to backups. In the case of a primary server failure, backups hold a leader election and use commit logs and snapshots to maintain consistent state.
In order to run any FILE.py, in the terminal, enter "python FILE.py".
- Setup
The files for these applications are stored in a public GitHub repo, which can be accessed at https://github.com/jamesb2413/replicated-chat. To get the files from this repository to your local machine, run the following command in the terminal when in the desired location for the files to be downloaded to:
git clone https://github.com/jamesb2413/replicated-chat
Now, you should have all of the files necessary to run the applications. There are a couple python libraries that are required to run these programs. You will need the socket library in addition to the unittest library to run the tests, both of which are built into the standard python library.
gRPC install and setup instructions can be found in the gRPC documentation Python Quick Start guide: https://grpc.io/docs/languages/python/quickstart/. This will require installation of grpcio and grpcio-tools using pip or anaconda.
- Startup
We first want to start up the server. To do this, edit the IP addresses in constants.py to match your machine(s). The constants use the following conventions: the three servers in the system use ids 0, 1, 2 respectively. To start the primary (at server 0), run:
python primary.py 0
Or, replace 0 with the desired id for your primary server. If you are running the application on just one machine, use IP address 127.0.0.1 (localhost) or look up your IPv4 (on Mac, Settings -> Network -> Advanced -> TCP/IP, listed as IPv4), start the server using this address, and give this address to each client that wishes to connect to the chat server. As for the port number, 8080, 8081, and 8082 are usually available.
To start backup servers, specify the id of the backup server as the first argument and the primary server id as the second argument, e.g.
python backups.py 1 0
Now that the servers are running, clients can begin to connect to the primary. The argument should match the primary server:
python client.py 0
Congratulations! At this point, you should connect to the server and recieve a welcome message. Replication ensures persistent state and system fault tolerance, but when the primary server fails, clients still need to terminate and connect to the new primary server. An extension of this project could implement a GUI which abstracts client reconnections so the user experience is uninterrupted.
- Operation
Now that the server is running and clients are connected, you will be asked if you already have a username. If so, enter 'y', else 'n'. If 'y' is entered, you will be prompted for your username, and if it matches a username in the database, you will be logged in. If 'n', then you will be asked to create a username. The username must be a single string with no spaces, greater than 0 characters. It also must be unique, so entering a username that someone else already has will trigger an error.
Once you are logged in, you will be given a several different operations that you can request the server to do. If you already had an account and messages were sent to you when you were logged out, they will be instantly printed for you when you logged in the order in which they were recieved. At this point, you can list all or a subset of accounts, send a message to another user, log out, or delete your account by entering 'l', 's', 'o', or 'd', respectively. Each of these operations are detailed below:
'l': list all accounts: You will be prompted for an optional parameter which allows you to enter in a specific username or some characters and a wildcard ('*') to filter down results. If nothing or '*' is entered as this parameter, a list of all users will be displayed. If a specific username is entered, any user that exists within the database will be displayed. If a combination of characters and a wildcard is entered, all names which have the same characters in the same positions preceding and following the wildcard will be returned. In other words, the '*' character signifies any number of arbitrary characters.
's': send a message: You will be prompted for the username of the user you want to send a message to. You can only send a message to one user at a time, and cannot send a message to yourself. If a username that exists within the database is entered, then you will be prompted for the message you wish to send. If that user is logged out, the message will be stored in their message queue, otherwise it will be delivered to them immediately.
'o': log out: You will be logged out and returned to the login screen.
'd': delete account: You will be asked to confirm that you wish to delete your account, as deleted accounts cannot be recovered. Enter 'y' for yes and 'n' for no. If 'n', you will be returned to the operations menu. If 'y', your account will be removed from the database and you will be returned to the login screen.
- Operation - Unit Tests
The unit tests can be found in test_helpers_gRPC.py. To run the tests in test_helpers.py, in the terminal run:
python -m unittest test_helpers_gRPC.py