How aggelako/distributed-ntua works
Project Type and Purpose
• The README explains that this is a file transfer application using a DHT based on the Chord protocol.
• The project is laid out as a distributed system: a bootstrap node (server.py) to initialize and manage the chord network and slave nodes (slaveserver.py) which join the DHT.
• There is also a CLI (cli.py) that allows a user to issue commands (file transfers or queries) to the network.
File Structure
• Main executable scripts include:
– server.py: Likely the bootstrap node which initializes the chord ring and sets up replication/consistency options.
– slaveserver.py: For individual node instantiation (each representing a slave/worker) that join the chord network.
– cli.py: The command-line interface issuing commands to interact with the system.
– dhtclasses.py: Contains the classes and logic for DHT operations (e.g., node management, finger table, stabilization, file lookup).
• Supporting scripts (runall.sh, script.sh) likely automate the start-up of multiple nodes or execute typical operations.
• Additional files like Report.pdf and assignment20_21.pdf suggest academic or documentation content, but the system’s architecture is fundamentally determined by the DHT and its node interactions.
README for Additional Insights
• The README details how to install dependencies (e.g., Flask, termcolor, pyfiglet) and hints at a possible web component or a simple UI aspect enabled by Flask.
• It specifies required configurations, such as hardcoded IPs and ports, emphasizing the network nature.
• The parameters for starting the server (replication factor and consistency type) indicate that nodes interact with a replication and consistency protocol—this part is key in your design.