2019
DOI: 10.1051/epjconf/201921407027
|View full text |Cite
|
Sign up to set email alerts
|

Exploiting private and commercial clouds to generate on-demand CMS computing facilities with DODAS

Abstract: Minimising time and cost is key to exploit private or commercial clouds. This can be achieved by increasing setup and operational efficiencies. The success and sustainability are thus obtained reducing the learning curve, as well as the operational cost of managing community-specific services running on distributed environments. The greater beneficiaries of this approach are communities willing to exploit opportunistic cloud resources. DODAS builds on several EOSC-hub services developed by the INDIGO-DataCloud… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
10
0

Year Published

2019
2019
2020
2020

Publication Types

Select...
6

Relationship

2
4

Authors

Journals

citations
Cited by 11 publications
(10 citation statements)
references
References 14 publications
0
10
0
Order By: Relevance
“…For instance, following the main route that allocates resources at the grid sites, some HPC centers have setup grid middleware such as CEs, so their CPUs are made accessible via the submission of GlideinWMS [20] pilot jobs that spawn HTCondor execution nodes that join the CMS SI global HTCondor pool (the case of the CSCS Swiss site, for example). Alternatively, the HTCondor execution nodes can be launched at the HPC independently of the CMS SI route, by employing a vacuum model [21], which can be implemented for example, employing a DODAS [22] approach. The access for CMS workloads to HPC resources can also be granted by means of incorporating the HPC slots into externally-managed HTCondor pools, which are then federated with the centralized CMS infrastructure.…”
Section: Resource Provisioningmentioning
confidence: 99%
“…For instance, following the main route that allocates resources at the grid sites, some HPC centers have setup grid middleware such as CEs, so their CPUs are made accessible via the submission of GlideinWMS [20] pilot jobs that spawn HTCondor execution nodes that join the CMS SI global HTCondor pool (the case of the CSCS Swiss site, for example). Alternatively, the HTCondor execution nodes can be launched at the HPC independently of the CMS SI route, by employing a vacuum model [21], which can be implemented for example, employing a DODAS [22] approach. The access for CMS workloads to HPC resources can also be granted by means of incorporating the HPC slots into externally-managed HTCondor pools, which are then federated with the centralized CMS infrastructure.…”
Section: Resource Provisioningmentioning
confidence: 99%
“…However, this does not preclude the possibility to easily run also on other types of infrastructure, and of course allows for a gradual transition from local running to fully Grid-like distributed computing. One more opportunity is the capability of deploying on-demand HTCondor clusters on Cloud resources through for example DoDAS [20], condor_annex (a mechanism provided by HTCondor) or other mechanisms, which is being explored. This would allow the collaborations to exploit heterogeneous or opportunistic resources transparently.…”
Section: Workload Managementmentioning
confidence: 99%
“…These resources are expected to be accessed on demand to create HTC clusters. In order to deal with this scenario we decided to rely on DODAS [5,6]. The latter is an open source deployer manager designed to dynamically exploit hybrid Cloud providers.…”
Section: Access To Cloud Based Resources: Dodasmentioning
confidence: 99%