Talk:Untrusted Distributed Storage - Revision history

Bo at 01:02, 6 November 2008

2008-11-06T01:02:22Z

← Older revision		Revision as of 01:02, 6 November 2008
Line 34:		Line 34:
	# What was the programming model used in the implementation of Farsite?		# What was the programming model used in the implementation of Farsite?
	# What was the biggest disadvantage to the implementation?		# What was the biggest disadvantage to the implementation?


			From other groups:

			Group 1:
			# Why use Java? <br>Java is strongly typed and has a built in garbage collector, which makes it easier and faster to develop for. The other reason was that they wanted to use an event driven architecture for the system and the SEDA prototype, SandStorm, was available.<br><br>
			# How was the inner ring chosen? <br>The "responsible party" publishes sets of failure-independent nodes discovered through offline measurement and analysis. The inner ring is selected from each of the 3f + 1 independent node sets.<br><br>
			# How big was the prototype able to scale? <br>There are no clear benchmarks, but Pond was outperformed in most of their benchmarks.

			Group 3:
			# What is the Byzantine protocol? <br>The Byzantine protocol is a distributed decision process in which all non-faulty participants reach the same decision as long as more than 2/3 of the participants follow the protocol correctly. 1/3 cannot be faulty otherwise the protocol will fail. The protocol requires a quadratic number of participants, so synchronizing is fairly infeasible. Also for Pond, authentication is required in the form of proactive threshold signatures.<br><br>
			# What is common between OceanStore and GFS in terms of environment requirements?<br> OceanStore and GFS are quite different. OceanStore uses a network overlay, GFS uses a master server. OceanStore uses untrusted servers, GFS uses trusted servers. OceanStore uses hierchical replication, GFS uses lazy replication. In fact, the only comparable aspect is the number of replicas generated by both systems.<br><br>
			# How did they meet the expectations of the original OceanStore paper and vision? (i.e. how did they solve design problems) <br>One important design decision was to not to support explicit locks or leases on data, and to instead rely on the update model to for consistency, and the atomicity of updates allows locks to be built at the application layer, if they are used. They also added more UIDs to make objects easier to access. They also implemented erasure coding in order to allow more reliable archiving of data.

			Group 4:
			# What is Tapestry and how does it work? <br>Tapestry is a decentralized object location and routing system; a scalable overlay network, built on TCP/IP and designed to manage the location of resources. Instead of routing to an IP like in TCP/IP, requests are sent to a GUID. Tapestry is also locality aware, so it then routes the message to the physical host that contains the resource closest to the message source, with high probability. Physical hosts can join Tapestry by supplying a GUID to identify itself, so other hosts can route messages to it. Hosts publish their resource GUIDs so other hosts can route messages to these. Tapestry does not restrict hosts from unpublishing, leaving the network or where resources are located on the host.<br><br>
			# How did they meet the expectations of the original OceanStore paper and vision? (i.e. how did they solve design problems) <br>Refer to Group 3 Q3.<br><br>
			# What is the difference between the primary and secondary replicas? <br>Each object has one primary and multiple secondary replicas. Primary replica serializes and applies all updates to the object and creates a digital certificate, called a heartbeat, mapping an AGUID to the VGUID of the most recent version. The heartbeat is a tuple containing an AGUID, a VGUID, a timestamp and a version sequence number. The heartbeat are regularly requested to ensure freshness. Primary replicas also enforces access control restrictions and serializes concurrent updates from multiple users. Secondary replicas find a pre-existing replica to serve as a parent, usually a primary replica if there are no other secondaries. Secondary replicas are also the child nodes of dissemination trees with primary replicas as the root, but don't contact the inner ring to handle client requests. The update model of Pond allows updates to propagate from the primary replica to the children secondary replicas.

Yacoub-A: /* Group 3 - Farsite */

2008-11-05T13:14:52Z

Group 3 - Farsite

← Older revision		Revision as of 13:14, 5 November 2008
Line 91:		Line 91:

	Second: NTFS does not allow a directory to be renamed if there is an open handle on a file in the directory or in any of its descendents. Thus, Farsite instead implements the Unixlike semantics of not name-locking an open file's path.		Second: NTFS does not allow a directory to be renamed if there is an open handle on a file in the directory or in any of its descendents. Thus, Farsite instead implements the Unixlike semantics of not name-locking an open file's path.


	2) How is the content lease system similar to lease systems in distributed systems we’ve already seen and which is most similar.		2) How is the content lease system similar to lease systems in distributed systems we’ve already seen and which is most similar.


	3) What is the scope of Farsite? Could it work as a World Wide file system like OceanStore.		3) What is the scope of Farsite? Could it work as a World Wide file system like OceanStore.

Yacoub-A: /* Group 3 - Farsite */

2008-11-05T13:14:09Z

Group 3 - Farsite

← Older revision		Revision as of 13:14, 5 November 2008
Line 86:		Line 86:

	1) Farsite was designed to look like NTFS. How do Farsite’s semantics differ from NTFS?		1) Farsite was designed to look like NTFS. How do Farsite’s semantics differ from NTFS?

	Ans.		Ans.
	First: Farsite has multi reader single writer policy. Additional attempts to read an open file will receive a handle to a snapshot of the file, it will not change to reflect updates by remote writers. An application can query the Farsite client to find out whether it has a snapshot handle or a true file handle, but this is not part of NTFS semantics.		First: Farsite has multi reader single writer policy. Additional attempts to read an open file will receive a handle to a snapshot of the file, it will not change to reflect updates by remote writers. An application can query the Farsite client to find out whether it has a snapshot handle or a true file handle, but this is not part of NTFS semantics.

Yacoub-A: /* Group 3 - Farsite */

2008-11-05T13:13:28Z

Group 3 - Farsite

← Older revision		Revision as of 13:13, 5 November 2008
Line 86:		Line 86:

	1) Farsite was designed to look like NTFS. How do Farsite’s semantics differ from NTFS?		1) Farsite was designed to look like NTFS. How do Farsite’s semantics differ from NTFS?
			Ans.
			First: Farsite has multi reader single writer policy. Additional attempts to read an open file will receive a handle to a snapshot of the file, it will not change to reflect updates by remote writers. An application can query the Farsite client to find out whether it has a snapshot handle or a true file handle, but this is not part of NTFS semantics.

			Second: NTFS does not allow a directory to be renamed if there is an open handle on a file in the directory or in any of its descendents. Thus, Farsite instead implements the Unixlike semantics of not name-locking an open file's path.

	2) How is the content lease system similar to lease systems in distributed systems we’ve already seen and which is most similar.		2) How is the content lease system similar to lease systems in distributed systems we’ve already seen and which is most similar.
Line 92:		Line 96:

	Ans. Farsites main scope was that of a univertisy, governement or large company. Analysis points to a scale of approximately 10^5 machines whereas OceanStore is around 10^10		Ans. Farsites main scope was that of a univertisy, governement or large company. Analysis points to a scale of approximately 10^5 machines whereas OceanStore is around 10^10


	==Group 4 - Farsite Retrospective==		==Group 4 - Farsite Retrospective==

Joshua Tessier at 22:23, 3 November 2008

2008-11-03T22:23:09Z

← Older revision		Revision as of 22:23, 3 November 2008
Line 92:		Line 92:

	Ans. Farsites main scope was that of a univertisy, governement or large company. Analysis points to a scale of approximately 10^5 machines whereas OceanStore is around 10^10		Ans. Farsites main scope was that of a univertisy, governement or large company. Analysis points to a scale of approximately 10^5 machines whereas OceanStore is around 10^10


			==Group 4 - Farsite Retrospective==
			Some questions were received by paper so they are put here as well as "FROM <GROUP>"

			TO OceanStore
			# What is their business model?
			# What is introspective and what are its many applications?¬
			# What are the advantages of using a “Version Control System” over a typical file system model?

			TO Pond
			# What is Tapestry and how does it work?
			# How did they meet the expectations of the original OceanStore paper and vision? (i.e. how did they solve design problems)
			# What is the difference between the primary and secondary replicas?

			TO FARSITE
			# What was the target environment for FARSITE?
			# What were the three different types of certificates and what were their purposes?
			# What is convergent encryption?

			FROM Pond

			# How did the lease system change between planning and implementation?
			# What are the programming models used in the implementation?
			# What was the biggest disadvantage to their implementation?

			From FARSITE(?)

			# What are the trends in technology that justify FARSITE?
			# Were the team members familiar with windows SIS driver?
			# What's WebDAV?

Satpal at 16:35, 3 November 2008

2008-11-03T16:35:09Z

← Older revision		Revision as of 16:35, 3 November 2008
Line 63:		Line 63:

	Retro		Retro


	1)Whats is the main target environment for farsite?		1)Whats is the main target environment for farsite?
Line 85:		Line 84:

	Ponds		Ponds


	1) Farsite was designed to look like NTFS. How do Farsite’s semantics differ from NTFS?		1) Farsite was designed to look like NTFS. How do Farsite’s semantics differ from NTFS?

Satpal at 16:34, 3 November 2008

2008-11-03T16:34:35Z

← Older revision		Revision as of 16:34, 3 November 2008
Line 89:		Line 89:
	1) Farsite was designed to look like NTFS. How do Farsite’s semantics differ from NTFS?		1) Farsite was designed to look like NTFS. How do Farsite’s semantics differ from NTFS?

	2) How is the content lease system similar to lease ~~system~~ in distributed systems we’ve already seen and which is most similar.		2) How is the content lease system similar to lease systems in distributed systems we’ve already seen and which is most similar.

	3) What is the scope of Farsite? Could it work as a World Wide file system like OceanStore.		3) What is the scope of Farsite? Could it work as a World Wide file system like OceanStore.

	Ans. Farsites main scope was that of a univertisy, governement or large company. Analysis points to a scale of approximately 10^5 machines whereas OceanStore is around 10^10		Ans. Farsites main scope was that of a univertisy, governement or large company. Analysis points to a scale of approximately 10^5 machines whereas OceanStore is around 10^10

Satpal at 16:32, 3 November 2008

2008-11-03T16:32:07Z

← Older revision		Revision as of 16:32, 3 November 2008
Line 92:		Line 92:

	3) What is the scope of Farsite? Could it work as a World Wide file system like OceanStore.		3) What is the scope of Farsite? Could it work as a World Wide file system like OceanStore.

			Ans. Farsites main scope was that of a univertisy, governement or large company. Analysis points to a scale of approximately 10^5 machines whereas OceanStore is around 10^10

Satpal at 16:16, 3 November 2008

2008-11-03T16:16:01Z

@@ Line 26: / Line 26: @@
 #	Farsite was desgined to look like NTFS. How do Farsite's semantics differ from NTFS?
-#	How is the content lease system similar to lease systems in distributed systems we've already soon, and which is most similar?
+#	How is the content lease system similar to lease systems in distributed systems we've already seen, and which is most similar?
 #	What is the scope of Farsite? Could it work as a world wide filesystem like OceanStore.
@@ Line 34: / Line 34: @@
 #	What was the programming model used in the implementation of Farsite?
 #	What was the biggest disadvantage to the implementation?

Laszlo at 14:36, 3 November 2008

2008-11-03T14:36:43Z

← Older revision		Revision as of 14:36, 3 November 2008
Line 20:		Line 20:

	# What was the purpose of introspection in terms of nomadic data?		# What was the purpose of introspection in terms of nomadic data?
	# How does the less-reliable-but-faster		# How does the less-reliable-but-faster probabalistic lookup work?
	# What is a Bloom filter and how is it used in OceanStore?		# What is a Bloom filter and how is it used in OceanStore?