Changes between Version 17 and Version 18 of WikiStart

Show
Ignore:
Timestamp:
06-02-2009 18:23:14 (4 years ago)
Author:
nuno
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v17 v18  
    2323== Components == 
    2424 
    25 The architecture is composed by the following components: 
     25The architecture is composed by three components: Cerebrum, Monitoring and Storage. An explanation of each component is provided in the following sections. 
    2626 
    27 === [wiki:Cerebrum] === 
     27=== Cerebrum === 
    2828 
    2929Cerebrum is the main component of dumpFS. It will be the interface between the storage, monitoring and client applications through a set of RESTful Webservices.  
    3030 
    31 Webservice [wiki:API]: 
     31Webservice API: 
    3232 * GET 
    3333 * PUT 
    3434 * DEL 
    3535 
    36 If the client wants to retrieve a file from dumpFS it will contact Cerebrum to know what is the best location to get the file from. Cerebrum will then answer with a set of locations and it is up to the client to get the file directly from the storage nodes. On the other hand, if the client wants to store a new file, it will contact the Cerebrum to know the location (which storage node) for storing the file and then contact the primary storage node directly to store the file. 
     36If the client wants to retrieve a file from dumpFS it will contact Cerebrum (GET) to know what is the best location to get the file from. Cerebrum will then answer with a set of locations and it is up to the client to get the file directly from the storage nodes. If the client wants to store a new file (PUT), it will contact Cerebrum to know the location (which storage node) for storing the file and then contact the primary storage node directly to store the file. Along with the file, the client should also send the message gotten from Cerebrum, which includes the set of storage nodes where the file will reside. The primary storage node will be responsible for replicating the file based on the replication policy. If the client wants to delete a file (DEL), it will contact Cerebrum to delete the file. Cerebrum will then contact the storage nodes where the file reside and instruct them to delete the file. 
    3737 
    38  
    39  
     38For more technical information about Cerebrum please read the [wiki:Cerebrum] page or the [wiki:API Webservice API]. 
    4039 
    4140=== Storage nodes ===