DOC PREVIEW
UMD CMSC 714 - BOINC

This preview shows page 1-2-20-21 out of 21 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

BOINCBOINC: A System for Public-Resource Computing and StorageDavid P. AndersonSerge KorenCMSC714November 22, 2005Outline➲Introduction➲Contrast to Grid Computing➲BOINC Goals➲BOINC Project/Server➲BOINC Client➲Conclusion11/22/2005 2 of 21Introduction●Many personal PCs (petaFLOPs)●Many large storage devices on personal PCs (exabytes)●Can be exploited for appropriate programs●Low data to compute ratio●Independently parallel●Server/worker model3 of 2111/22/2005Introduction (cont)4 of 21●Computers connected with lower connectivity (DSL, cable, telephone)●Participants volunteer to participate (rewards)●Risk of malicious participants●Forged results●Forged reward11/22/2005Contrasting Approaches●Grid computing●Designed for centrally managed expensive equipment●Targets high performance, high bandwidth, full-time connectivity machines●Strict performance/availability guarantees●Need for resource discovery and access●Less concern over authorized malicious users (hard to become authorized user)5 of 2111/22/2005BOINC Goals●Reduce the barriers of entry to public-resource computing●Share resources among autonomous projects●participants can be part of multiple projects●Support diverse applications●Reward participants●Cheat-resistant “credit”6 of 2111/22/2005BOINC Architecture●BOINC Project●Identified by master URL●Includes multiple applications●DB containing info on applications/participants/work/results/teams●Task Servers●issues work to clients and accepts results●Data Servers●accept file uploads7 of 2111/22/2005BOINC Server11/22/2005 8 of 21How it Works●Application versions ●Support different client machines●Workunits (version independent)●Contains input data, command-line args●Lists compute/memory/storage requirements and deadline●Results●Result of a specific workunit●Consists of output files11/22/2005 11 of 21Task Server●Work generator – generates workunits●Scheduler – determines appropriate workunits for a client●Feeder – caches database information●Transitioner – manages state of workunit●Validater – examines results and selects canonical●Assimilater – assimilates validated results11/22/2005 9 of 21Task Server11/22/2005 10 of 21Security Issues (Server)●Result falsification●redundant computing●Credit falsification●credit verification●DoS attacks on server●limited file upload sizes/signed result description●Theft of project files●BOINC does not encrypt project files11/22/2005 12 of 21Redundant Computing●Redundancy●N copies of each workunit created●Two instances never sent to same participant●If an instance times out, another one is sent●Validation●Each result compared to canonical result (if available)●Otherwise a quorum must be reached●Validated using application specific function11/22/2005 13 of 21Redundancy (Example)11/22/2005 14 of 21Credit and Failure●Credit●claimed credit – CPU time * BOINC benchmark●can include other application-specific credit●granted credit●actual credit based on average or min of workunit instances●trickle messages●allow credit for intermediate computation●Failure●all communications use exponential backoff11/22/2005 15 of 21BOINC Client●Used by participants●Shared for all projects●Constructed from several components●Core client●Client GUI●API for applications to get CPU access●Screensaver11/22/2005 16 of 21BOINC Client Features●Participant preferences●when computation is allowed●limits of CPU time/bandwidth●Anonymous platforms●participants compile source code and report results as anonymous●Local scheduler●satisfy requirements and workunit deadlines●maintain variety between multiple projects17 of 2111/22/2005Security Issues (Participant)●Malicious executable distribution●code/executable signed by server●Theft of account information from server●server must be secured●Theft of account information over network●no protection●Intentional/Accidental abuse of machine ●no sandboxing, projects should be well tested 11/22/2005 18 of 21BOINC Client11/22/2005 19 of 21Conclusion●Many examples of projects●DoS on server still possible by malicious client●Centralized DB for project server is bottleneck (MySQL)●No sandboxing of project executables20 of 2111/22/2005References●D. P. Anderson. BOINC: A System for Public-Resource Computing and Storage. 5th IEEE/ACM International Workshop on Grid Computing, November, 2004.●D. P. Anderson, E. Korpela, R. Walton. High-Performance Task Distribution for Volunteer Computing. To appear in First IEEE International Conference on e-Science and Grid Technologies, December 2005.●BOINC Homepage. http://boinc.berkeley.edu/11/22/2005 21 of


View Full Document

UMD CMSC 714 - BOINC

Documents in this Course
MTOOL

MTOOL

7 pages

Eraser

Eraser

14 pages

Load more
Download BOINC
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view BOINC and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view BOINC 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?