Changes between Version 33 and Version 34 of OrgGrid


Ignore:
Timestamp:
Jul 16, 2008, 10:49:43 AM (16 years ago)
Author:
teleyinex
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • OrgGrid

    v33 v34  
    44OGM (TODO: pick a better name) is a system for grid computing on organizational resources, using BOINC.
    55
    6 BOINC is thought to rely on user decisions because they are the owners of the computers. However, there are situations where the users are not the owners of the PCs, for example the PCs from an institution like an University. In this case, the computers are controlled by the institution, and therefore the institution decides in which tasks can be used those computers. In this new scenario BOINC lacks a tool to harness remotely all the BOINC enabled computers without the intervention of the user. For this reason, we are developing the tool called OGM.
     6BOINC is designed to rely on user decisions because they are the owners of the computer resources. However, there are situations where the users are not the owners of the PCs, for example the PCs of an institution like an University. In this case, the computers are controlled by the institution, so the institution decides in which tasks can be used those computers. In this new scenario BOINC lacks a tool to harness remotely all the BOINC enabled computers without the intervention of the user. For this reason, we are developing a tool called OGM.
    77
    8 OGM is a tool which basically works in the same way as the Account Managers does. The main difference is that OGM is institutional oriented instead of user oriented. Hence, the OGM employs the Account Manager protocol, and uses a Master Slave architecture. To support this software, all the clients will have to install a BOINC client and attach to the OGM server. Once the clients have contacted the OGM server, the clients will receive all the BOINC projects that they have to process.
     8OGM is a tool which basically works in the same way as the Account Managers do. The main difference is that OGM is institutional oriented instead of user oriented. Hence, the OGM employs the Account Manager protocol, and uses a Master Slave architecture. To support this software, all the clients will have to install a BOINC client and attach it to the OGM server. Once the clients have contacted the OGM server, the clients will receive all the BOINC projects that they have to process.
    99
    1010As now the institution has the power of deciding which projects they are going to support with its resources, the institution could receive petitions for using those BOINC resources. For this reason, the institution will have a committee. This committee will decide which BOINC projects are interesting for the institution. Based on this decision, the institution will donate its BOINC enabled PCs to the chosen projects.
    1111
    1212== OGM Components ==
    13 OGM consists in two main parts: the hardware and the administrators. Therefore, for OGM, from the point of view of hardware components, an institution is composed with the following items:
    14  * PC. This is the basic item of OGM. A PC here is named as a "BOINC working node". The institution must have at least one PC.
    15  * Pool. A Pool is a set of zero or more PCs that share something in common. For example, all the PCs are located in the same laboratory. The institution must have at least one pool of computers.
    16  * Department. A Department is a set of one or more Pools of computers that share something in common. For example, all the pools belongs to the math research group of the institution. An institution must have at least one Department.
     13OGM has two main components: the hardware and the administrators. Therefore, for OGM, from the point of view of hardware components, an institution has the following items:
     14 * '''Computer'''. This is the ''basic'' item of OGM. A computer here is named as a "BOINC working node". ''The institution must have at least one computer''.
     15 * '''Pool'''. A Pool is a set of ''zero or more computers'' that share something in common. For example, all the computers are located in the same laboratory. ''The institution must have at least one pool of computers''.
     16 * '''Department'''. A Department is a set of ''one or more Pools'' of computers that share something in common. For example, all the pools belongs to the math research group of the institution. ''An institution must have at least one Department''.
    1717
    18 For OGM, from the point of view of managers, an institution is composed with the following persons:
    19  * IT Manager. An IT Manager always belongs to one Department. For this reason, the IT Manager can only administer the computer pools which belongs to his department.
    20  * Project Manager. A Project Manager is in charge of choosing and attaching the BOINC projects that will run on the institution BOINC PCs.
     18For OGM, from the point of view of managers, an institution has the following persons:
     19 * '''IT Manager'''. An IT Manager ''always belongs to one Department''. For this reason, the IT Manager can only administer the pools that belong to his department.
     20 * '''Project Manager'''. A Project Manager is in charge of choosing and attaching the BOINC projects that will run on the institution BOINC computers.
    2121
    2222A visual summary of the explained components is in the following figure: