Using the glideinWMS System as a Common Resource Provisioning Layer in CMS

Using the glideinWMS System as a Common Resource Provisioning Layer in CMS
复制标题

DOI:
10.1088/1742-6596/664/6/062031
复制
发表时间:
2015-12
期刊:
Journal of Physics: Conference Series
影响因子:
--
通讯作者:
J. Balcas;S. Belforte;B. Bockelman;D. Colling;O. Gutsche;D. Hufnagel;F. Khan;K. Larson;J. Letts;M. Mascheroni;D. Mason;A. McCrea;S. Piperov;M. Saiz-Santos;I. Sfiligoi;A. Tanasijczuk;C. Wissing
J. Balcas;S. Belforte;B. Bockelman;D. Colling;O. Gutsche;D. Hufnagel;F. Khan;K. Larson;J. Letts;M. Mascheroni;D. Mason;A. McCrea;S. Piperov;M. Saiz-Santos;I. Sfiligoi;A. Tanasijczuk;C. Wissing
中科院分区:
其他
文献类型:
--
作者:
J. Balcas;S. Belforte;B. Bockelman;D. Colling;O. Gutsche;D. Hufnagel;F. Khan;K. Larson;J. Letts;M. Mascheroni;D. Mason;A. McCrea;S. Piperov;M. Saiz-Santos;I. Sfiligoi;A. Tanasijczuk;C. Wissing

文献摘要

被引文献

相似文献

CMS将需要在2015年开始第二次运行时获得超过125k的处理器核心,以执行其雄心勃勃的物理计划,包括更多和更高复杂性的事件。在Run1期间,这些资源主要由网格站点和本地批处理资源混合提供。在长期关闭的云基础设施期间,各种机会资源和HPC超级计算中心被提供给CMS,这进一步复杂化了提交基础设施的操作。在本演示文稿中,我们将讨论CMS为采用和部署glideinWMS系统作为网格、云、本地批处理和机会资源和站点的公共资源供应层所做的努力。我们将解决与整合各种类型的资源相关的挑战、与使用公共资源供应层相关的效率提升和简化,并讨论找到的解决方案。最后,我们将展望CMS在为更多异类架构和服务提供资源方面取得进展的未来计划。
CMS will require access to more than 125k processor cores for the beginning of Run 2 in 2015 to carry out its ambitious physics program with more and higher complexity events. During Run1 these resources were predominantly provided by a mix of grid sites and local batch resources. During the long shut down cloud infrastructures, diverse opportunistic resources and HPC supercomputing centers were made available to CMS, which further complicated the operations of the submission infrastructure. In this presentation we will discuss the CMS effort to adopt and deploy the glideinWMS system as a common resource provisioning layer to grid, cloud, local batch, and opportunistic resources and sites. We will address the challenges associated with integrating the various types of resources, the efficiency gains and simplifications associated with using a common resource provisioning layer, and discuss the solutions found. We will finish with an outlook of future plans for how CMS is moving forward on resource provisioning for more heterogenous architectures and services.