Status
Status of the Hydra Filesystem
Week 8
- Testing and debugging different scenarios
- Developed a small & simple monitor to see what goes on during requests
- Code freezed. HydraFS 0.01a ready for presentation!
Week 7
- Fixed some really obscure threading bugs
- Successfully submitted my entire home directory to the file system (851 files)
- Clients can now get info on files and directory listings from metadata server
- Currently testing with a couple of custom applications (and fixing a few bugs)
- Data servers are now syncing with the metadata server upon startup
- Implemented a simple round-robin selection policy for dataservers
Week 6
- Clients can now delete files from the filesystem
- Cleaned up and rewrote part of the client library
- Newly created files are now being replicated through the data nodes
Week 5
- Data servers already storing files as objects, per requests of clients directed from metadata server
- Clients can now get files that are stored in the filesystems
- Clients can now append and write to files stored in the filesystems, and both metadata and data servers are tracking versions succesfully
Week 4
- Database & abstraction layer for storing filesystem structure finished
- Created small console utility for displaying the full contents of the database
- Metadata server is now accepting requests for creating files & adding them to the location/versioning database
- Clients can now connect to the metadata server to request file creation & be redirected to a proper dataserver to balance load
Week 3
- Metadata server is now threaded and serves requests
- Data servers are able to announce themselves to the metadata servers and keep their status alive with heartbeats.
- Both metadata & data server now read their config from XML files
Week 2:
- Created request dispatch mechanism for metadata & data servers
- Created socket transport layer & packet creation module
Week 1
- Designed transport communications layer