T-07S-05 - Revision history

Fbechstein: /* Distributed Filesystem for Wireless Mesh Networks */

2007-07-30T17:17:43Z

Distributed Filesystem for Wireless Mesh Networks

← Older revision		Revision as of 17:17, 30 July 2007
Line 1:		Line 1:
	=Distributed Filesystem for Wireless Mesh Networks=		=Distributed Filesystem for Wireless Mesh Networks=
	Assigned to: [~~[User~~:~~Fbechstein\|~~Felix Bechstein]]		Assigned to: [http://www2.informatik.hu-berlin.de/~bechstei/ Felix Bechstein]

	Advisor: Anatolij Zubow		Advisor: Anatolij Zubow

2007-07-30T17:16:26Z

Project Log

← Older revision		Revision as of 17:16, 30 July 2007
Line 41:		Line 41:
	** Implement a DHT interface localy (not distributed).		** Implement a DHT interface localy (not distributed).
	** Implement the Blocklayer.		** Implement the Blocklayer.
			*** hardcopys on blocklayer
	** Implement Direcorys:		** Implement Direcorys:
	*** openDir		*** openDir
Line 46:		Line 47:
	*** rmdir		*** rmdir
	*** ls		*** ls
			*** close
	*** <s>chdir</s>		*** <s>chdir</s>
	*** <s>pwd</s>		*** <s>pwd</s>
Line 54:		Line 56:
	*** write		*** write
	*** truncate		*** truncate
			*** close
	** Implement Fuse Frontend		** Implement Fuse Frontend
			** first prototype
	* What You plan to do next?		* What You plan to do next?
	** fix bugs		** fix bugs

2007-07-10T09:31:43Z

Project Log

← Older revision		Revision as of 09:31, 10 July 2007
Line 42:		Line 42:
	** Implement the Blocklayer.		** Implement the Blocklayer.
	** Implement Direcorys:		** Implement Direcorys:
			*** openDir
	*** mkdir		*** mkdir
			*** rmdir
	*** ls		*** ls
	*** chdir		*** <s>chdir</s>
	*** pwd		*** <s>pwd</s>
			** Implement Files
			*** openFile
			*** unlink
			*** read
			*** write
			*** truncate
			** Implement Fuse Frontend
	* What You plan to do next?		* What You plan to do next?
	** ~~Implement~~ ~~Files.~~		** fix bugs
	** ~~Build~~ ~~an abstraction~~ to ~~fuse or~~ ~~nfs.~~		** push performance to its limits

2007-06-26T12:46:55Z

Problem Statement

← Older revision		Revision as of 12:46, 26 June 2007
Line 11:		Line 11:
	*To which domain of Computer Science does this problem relate to?		*To which domain of Computer Science does this problem relate to?
	*Why is the problem interesting? Why is it difficult?		*Why is the problem interesting? Why is it difficult?
	** A filesystem is ~~abasic~~ service for many applications on top. It can be used for class- and update-distribution, backup- or storage-service and many more.		** A filesystem is a basic service for many applications on top. It can be used for class- and update-distribution, backup- or storage-service and many more.

	==Deliverables==		==Deliverables==

2007-06-26T08:40:10Z

Project Log

← Older revision		Revision as of 08:40, 26 June 2007
Line 47:		Line 47:
	*** pwd		*** pwd
	* What You plan to do next?		* What You plan to do next?
	** Implement Files		** Implement Files.
	** Build an abstraction to fuse or nfs.		** Build an abstraction to fuse or nfs.

2007-06-26T08:40:02Z

Project Log

← Older revision		Revision as of 08:40, 26 June 2007
Line 37:		Line 37:

	==Project Log==		==Project Log==
	* What you have done so far~~? What You plan to do next~~?		* What you have done so far?
			** Define some Interfaces (not fixed yet).
			** Implement a DHT interface localy (not distributed).
			** Implement the Blocklayer.
			** Implement Direcorys:
			*** mkdir
			*** ls
			*** chdir
			*** pwd
			* What You plan to do next?
			** Implement Files
			** Build an abstraction to fuse or nfs.

2007-06-26T08:35:59Z

Key Ideas / Project Execution Plan

← Older revision		Revision as of 08:35, 26 June 2007
Line 27:		Line 27:
	==Key Ideas / Project Execution Plan ==		==Key Ideas / Project Execution Plan ==
	*How will you approach the problem?		*How will you approach the problem?
	** I'll build the filesystem from bottom to top.		** I'll build the filesystem from bottom to top:
	*** abstraction to fuse, nfs or similar		*** abstraction to fuse, nfs or similar
	*** fs-layer: c# library, with an ioctl-like interface		*** fs-layer: c# library, with an ioctl-like interface
	*** block-layer: abstract the dht to simple blocks/extends variable in size		*** block-layer: abstract the dht to simple blocks/extends variable in size
	*** dht-layer: use the [[T-07S-04\|DHT]]		*** dht-layer: use the [[T-07S-04\|DHT]]
			** All the BRN-magic is done in the DHT, so i'll try to build a clever block structure with some caching to improve everything's speed.
	*On which contributions of others do you depend on?		*On which contributions of others do you depend on?
	** [[T-07S-04\|Distributed Hash Table]] by Anselm Ringleben		** [[T-07S-04\|Distributed Hash Table]] by Anselm Ringleben

2007-06-26T08:33:01Z

Key Ideas / Project Execution Plan

← Older revision		Revision as of 08:33, 26 June 2007
Line 27:		Line 27:
	==Key Ideas / Project Execution Plan ==		==Key Ideas / Project Execution Plan ==
	*How will you approach the problem?		*How will you approach the problem?
			** I'll build the filesystem from bottom to top.
			*** abstraction to fuse, nfs or similar
			*** fs-layer: c# library, with an ioctl-like interface
			*** block-layer: abstract the dht to simple blocks/extends variable in size
			*** dht-layer: use the [[T-07S-04\|DHT]]
	*On which contributions of others do you depend on?		*On which contributions of others do you depend on?
			** [[T-07S-04\|Distributed Hash Table]] by Anselm Ringleben

	==Project Log==		==Project Log==

2007-06-26T08:24:18Z

Problem Statement

← Older revision		Revision as of 08:24, 26 June 2007
Line 8:		Line 8:
	==Problem Statement==		==Problem Statement==
	*Which problem do you want to solve?		*Which problem do you want to solve?
			** There is no filesystem only based on DHT for decentralized use, like our BRN.
	*To which domain of Computer Science does this problem relate to?		*To which domain of Computer Science does this problem relate to?
	*Why is the problem interesting? Why is it difficult?		*Why is the problem interesting? Why is it difficult?
			** A filesystem is abasic service for many applications on top. It can be used for class- and update-distribution, backup- or storage-service and many more.

	==Deliverables==		==Deliverables==

2007-06-19T08:17:36Z

Deliverables

← Older revision		Revision as of 08:17, 19 June 2007
Line 13:		Line 13:
	==Deliverables==		==Deliverables==
	*At the end of the project, what will you have delivered?		*At the end of the project, what will you have delivered?
			** A basic distributed (high-performance) filesystem, using only the [[T-07S-04\|DHT]].
			** An interface to that filesystem in fuse or nfs, to mount it.
	*What does it mean that the project was successful?		*What does it mean that the project was successful?
			** The filesystem's performance is sufficient for class- or upgrade-distribution.

	==Prior Art==		==Prior Art==