DistOS 2015W Session 6: Difference between revisions

From Soma-notes
Line 47: Line 47:




==Group 3==
==Group 3== DANY, MOE, DEEP, SAMEER, TROY
 
'''FARSITE'''
 
'''Security'''
• Cascading certificates system through directory hierarchy
• Keys
• Three types of certificates
• CFS required to authorized certificate
 
'''System Architecture'''
• Client Monitor, directory group, file host
• When space runs out in directory group, delegate’s ownership to sub tree to other delegate group.
 
 
'''OCEANSTORE'''
 
'''Security'''
• GUID and ACLs used for write, encryption used for reads.

Revision as of 21:37, 9 February 2015

Midterm

The midterm from last year is now available.

Group 1

Team: Kirill, Jamie, Alexis, Veena, Khaled, Hassan

FARSITE OceanStore
Fault Tolerance Used Byzantine Fault Tolerance Algorithm - Did not manage well Used Byzantine Fault Tolerance Algorithm - Did not manage well
Cryptography Trusted Certificates A strong cryptographic algorithm on read-only operations
Implementation Did not mention what programming they used, but it was based on Windows. They did not implement the file system Implemented in JAVA
Scalability Scalable to a University or large corporations, maximum 105 Worldwide scalability, maximum 1010
File Usage Was designed for general purpose files Was designed for small file sizes
Scope All clients sharing the available resources Transient centralized service
Object Model Didn't use the object model Used the object model

Group 2

Team Members: Apoorv, Ambalica, Ashley, Eric, Mert, Shivjot


==Group 3== DANY, MOE, DEEP, SAMEER, TROY

FARSITE

Security • Cascading certificates system through directory hierarchy • Keys • Three types of certificates • CFS required to authorized certificate

System Architecture • Client Monitor, directory group, file host • When space runs out in directory group, delegate’s ownership to sub tree to other delegate group.


OCEANSTORE

Security • GUID and ACLs used for write, encryption used for reads.