2015
DOI: 10.1088/1742-6596/664/6/062031
|View full text |Cite
|
Sign up to set email alerts
|

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

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
23
0

Year Published

2015
2015
2019
2019

Publication Types

Select...
6
1

Relationship

1
6

Authors

Journals

citations
Cited by 25 publications
(23 citation statements)
references
References 3 publications
0
23
0
Order By: Relevance
“…priority of the work, etc. Each WMAgent is responsible for splitting the work into smaller chunks (jobs) and sending them to the CMS Global Pool [4], an HTCondor [5] batch system overlayed, using Glidein-WMS [6], on the CMS-accessible grid resources. The batch system then distributes the jobs to computing resources all over the world-the tiered system mentioned above.…”
Section: Cms Workflow Management Systemmentioning
confidence: 99%
“…priority of the work, etc. Each WMAgent is responsible for splitting the work into smaller chunks (jobs) and sending them to the CMS Global Pool [4], an HTCondor [5] batch system overlayed, using Glidein-WMS [6], on the CMS-accessible grid resources. The batch system then distributes the jobs to computing resources all over the world-the tiered system mentioned above.…”
Section: Cms Workflow Management Systemmentioning
confidence: 99%
“…CMS Global pool has over 30 schedds connected to it in total, and over a dozen of them are active at the same time. Resource provisioning is based on GlideinWMS [28] which has the knowledge of all the sites supporting CMS computing. DODAS implements a model which de facto bypasses the resource provisioning glidein based and, upon user request, creates a CMS ephemeral WLCG [29] site which auto-registers to the Global Pool.…”
Section: Cms Use Casementioning
confidence: 99%
“…As a unified pool [5], it joins geographically distributed resources together under control of a single HTCondor Central Manager (CM) and also provides a single entry point for tasks with diverse resource requests (e.g. single-core and multi-core jobs [6], jobs with higher-thanstandard memory requirements, etc).…”
Section: Introductionmentioning
confidence: 99%