Collaborative Research: SI2-SSI: Adding Volunteer Computing to the Research Cyberinfrastructure

协作研究：SI2-SSI：将志愿者计算添加到研究网络基础设施中

• 批准号: 1550526
• 负责人: Michael Zentner
• 金额: $ 10.73万
• 依托单位: Purdue University
• 依托单位国家: 美国
• 项目类别: Standard Grant
• 财政年份: 2016
• 资助国家: 美国
• 起止时间: 2016-08-01 至 2017-07-31
• 项目状态: 已结题
• 来源: https://www.nsf.gov/awardsearch/showAward?AWD_ID=1550526&HistoricalAwards=false
• 关键词: Collaborative; Research; SI2; SSI; Adding

The aggregate computing power of consumer devices - desktop and laptop computers, tablets, smartphones - far exceeds that of institutional computing resources. "Volunteer computing" uses these consumer devices, volunteered by their owners, to do scientific computing. In addition to providing additional, much-needed computational resources to scientists, volunteer computing publicizes scientific research and engages citizens in science. BOINC is the primary software system for volunteer computing. It was developed at UC Berkeley with NSF support starting in 2002. Until now, BOINC has been based on a model of independent competing projects. Scientists set up their own BOINC servers, port their applications to run on BOINC, and publicize their projects to attract volunteers. There are about 40 such projects, in many areas of science: examples include Einstein@home, CERN, and SETI@home (astrophysics), Rosetta@home and GPUGrid.net (biomedicine), Climateprediction.net (climate study), and IBM World Community Grid (multiple applications). Together these projects have about 400,000 active volunteers and 12 PetaFLOPS of computing throughput. This model, while successful to an extent, has reached a limit. The number of projects and volunteers has stagnated. Volunteer computing is supplying lots of computing power, but only to a few research projects. For other scientists, there are two major barriers. First, creating a BOINC project has significant overhead: learning a new technology, creating a public web site, generating publicity, and so on. Second, volunteer computing is risky and uncertain; there is no guarantee that a new project will attract volunteers. This project aims to break this barrier, and to make volunteer computing available to all scientists doing high-throughput computing, by replacing the competing-projects model with a new "central broker" model. The new model has two related parts: 1) the integration of BOINC with existing high-throughput computing facilities such as supercomputing centers and science portals. Jobs currently run on cluster nodes will be transparently offloaded to volunteer computers. Scientists using these facilities will see faster turnaround times; they'll benefit from volunteer computing without even knowing it's there. 2) The project will change the volunteer interface so that participants sign up for scientific areas and goals rather then for particular projects. For example, a participant might sign up to contribute to cancer research. A central broker, to be developed as part of this project, would dynamically assign their computing resources to projects doing that type of research. This project mobilizes public support for and interest in scientific research by encouraging "volunteer computing" and engaging citizens in the conduct of the research itself. It simultaneously advances NSF's mission to advance science while broadening citizen engagement.The first year of this project will prototype each of these parts, and will integrate BOINC with TACC and nanoHub. Integrating BOINC with existing HTC systems involves several subtasks: 1) Job routing: modifying existing job processing systems used by TACC and nanoHub (Launcher and Rappture respectively) to decide when a group of jobs should be offloaded to BOINC. This decision might involve the estimated runtime of the jobs, input and output file sizes, data sensitivity, the deadline or priority of the jobs, and the identity of the job submitter. 2) Job format conversion: mapping job descriptions (input/output file specifications, resource and timing requirements) to their BOINC equivalents. 3) Application packaging: adapting existing applications (such as nanoHub's simulation tools and TACC's Autodock) to run under BOINC. We will use BOINC's virtual machine facility, which packages an application as a virtual machine image (VirtualBox or Docker) and a program to be run within the VM. This allows existing Linux applications to run on consumer desktop platforms such as Windows and Mac, as well as providing a strong security sandbox and an efficient application-independent checkpoint/restart mechanism. 4) File handling: moving input and output files between existing storage systems (typically inaccessible from outside firewalls) to Internet-visible servers. This will use existing BOINC components that manage files based on hashes to eliminate duplicate transfer and storage of files. 5) Job monitoring and control: adapting existing web- or command-line based tools for monitoring the progress of batches of jobs, and for aborting jobs, to work with BOINC. This will use existing Web RPCs provided by BOINC for these purposes. This project will carry out these tasks by designing and implementing new software as needed, testing for correctness, performance, and scalability, and deploying it in a production environment. The second part of the project - a brokering system for allocating computing power based on volunteer scientific preferences - will be designed and prototyped. This involves several subtasks: 1) Designing a schema for volunteer preferences, including scientific areas and sub-areas, project nationality and institutions, specific projects and applications, inclusions/exclusions, and so on. 2) Designing a schema for assigning attributes to job streams (e.g. their area, sub-area, institution, etc.), and for assigning quotas or priorities to job streams. 3) Designing a relational database for storing the above information. 4) Designing and implementing policies for assigning volunteer resources to job streams in a way that respects volunteer preferences and optimizes quota, fairness, and throughput criteria. This will be implemented as a BOINC "account manager" so that volunteers see a single interface rather than lots of separate projects and web sites.

消费设备（台式机和笔记本电脑、平板电脑、智能手机）的总计算能力远远超过机构计算资源。 “志愿计算”使用这些由其所有者自愿提供的消费设备来进行科学计算。除了为科学家提供额外的、急需的计算资源外，志愿者计算还宣传科学研究并吸引公民参与科学。 BOINC 是志愿者计算的主要软件系统。 它是在 2002 年开始在美国国家科学基金会 (NSF) 的支持下在加州大学伯克利分校开发的。到目前为止，BOINC 一直基于独立竞争项目的模型。 科学家们建立自己的BOINC服务器，将他们的应用程序移植到BOINC上运行，并宣传他们的项目来吸引志愿者。 此类项目大约有 40 个，涉及许多科学领域：例如 Einstein@home、CERN 和 SETI@home（天体物理学）、Rosetta@home 和 GPUGrid.net（生物医学）、Climateprediction.net（气候研究）和 IBM世界网格社区（多个应用程序）。 这些项目总共拥有约 400,000 名活跃志愿者和 12 PetaFLOPS 的计算吞吐量。这种模式虽然在一定程度上取得了成功，但已经达到了极限。 项目和志愿者的数量停滞不前。 志愿计算正在提供大量的计算能力，但仅限于少数研究项目。 对于其他科学家来说，存在两个主要障碍。 首先，创建 BOINC 项目需要大量开销：学习新技术、创建公共网站、进行宣传等等。 其次，志愿计算具有风险和不确定性；无法保证新项目会吸引志愿者。该项目旨在打破这一障碍，通过用新的“中央代理”模型取代竞争项目模型，使所有从事高通量计算的科学家都可以使用志愿计算。新模型有两个相关部分：1）BOINC与现有高通量计算设施（例如超级计算中心和科学门户）的集成。当前在集群节点上运行的作业将透明地卸载到志愿者计算机上。使用这些设施的科学家将看到更快的周转时间；他们会从志愿者计算中受益，甚至不知道它的存在。 2）该项目将改变志愿者界面，以便参与者注册科学领域和目标，而不是特定项目。例如，参与者可能会报名为癌症研究做出贡献。作为该项目的一部分开发的中央经纪人将动态地将其计算资源分配给进行此类研究的项目。该项目通过鼓励“志愿者计算”和让公民参与研究本身来调动公众对科学研究的支持和兴趣。它同时推进了 NSF 推进科学发展并扩大公民参与的使命。该项目的第一年将对每个部分进行原型设计，并将 BOINC 与 TACC 和 nanoHub 集成。将 BOINC 与现有 HTC 系统集成涉及几个子任务： 1) 作业路由：修改 TACC 和 nanoHub（分别为 Launcher 和 Rappture）使用的现有作业处理系统，以决定何时应将一组作业卸载到 BOINC。此决策可能涉及作业的估计运行时间、输入和输出文件大小、数据敏感性、作业的截止日期或优先级以及作业提交者的身份。 2) 作业格式转换：将作业描述（输入/输出文件规范、资源和时间要求）映射到其 BOINC 等效项。 3）应用程序打包：将现有应用程序（例如nanoHub的模拟工具和TACC的Autodock）改编为在BOINC下运行。我们将使用 BOINC 的虚拟机工具，它将应用程序打包为虚拟机映像（VirtualBox 或 Docker）和要在 VM 中运行的程序。 这使得现有的 Linux 应用程序可以在 Windows 和 Mac 等消费者桌面平台上运行，并提供强大的安全沙箱和高效的独立于应用程序的检查点/重启机制。 4) 文件处理：将现有存储系统（通常无法从外部防火墙访问）之间的输入和输出文件移动到互联网可见的服务器。 这将使用基于哈希值管理文件的现有 BOINC 组件来消除文件的重复传输和存储。 5) 作业监控和控制：采用现有的基于 Web 或命令行的工具来监控批量作业的进度以及中止作业，以与 BOINC 配合使用。这将使用 BOINC 提供的现有 Web RPC 来实现这些目的。该项目将通过根据需要设计和实现新软件、测试正确性、性能和可扩展性并将其部署在生产环境中来执行这些任务。该项目的第二部分——一个根据志愿者科学偏好分配计算能力的经纪系统——将被设计和原型化。 这涉及几个子任务：1）设计志愿者偏好的模式，包括科学领域和子领域、项目国籍和机构、具体项目和应用、包含/排除等。 2) 设计一个架构，用于为作业流分配属性（例如，其区域、子区域、机构等），以及为作业流分配配额或优先级。 3）设计一个关系数据库来存储上述信息。 4) 设计和实施政策，以尊重志愿者偏好并优化配额、公平性和吞吐量标准的方式将志愿者资源分配给工作流。 这将作为 BOINC“客户经理”实施，以便志愿者看到一个界面，而不是许多单独的项目和网站。