CMS partial releases: Model, tools, and applications online and framework-light releases

Christopher D. Jones; David Lange; Emilio Meschi; Shahzad Muzaffar; Andreas Pfeiffer; Natalia Ratnikova; Elizabeth Sexton-Kennedy

doi:10.1088/1742-6596/219/4/042051

CMS partial releases: Model, tools, and applications online and framework-light releases

Christopher D. Jones, David Lange, Emilio Meschi, Shahzad Muzaffar, Andreas Pfeiffer, Natalia Ratnikova, Elizabeth Sexton-Kennedy

Research output: Contribution to journal › Conference article › peer-review

Abstract

With the integration of all CMS software packages into one release, the CMS software release management team faced the problem that for some applications a big distribution size and a large number of unused packages have become a real issue. TWe describe a solution to this problem. Based on functionality requirements and dependency analysis, we define a self-contained subset of the full CMS software release and create a Partial Release for such applications. We describe a high level architecture for this model, and tools that are used to automate the release preparation. Finally we discuss the two most important use cases for which this approach is currently implemented.

Original language	English (US)
Article number	042051
Journal	Journal of Physics: Conference Series
Volume	219
Issue number	1 PART 4
DOIs	https://doi.org/10.1088/1742-6596/219/4/042051
State	Published - 2010
Externally published	Yes
Event	17th International Conference on Computing in High Energy and Nuclear Physics, CHEP 2009 - Prague, Czech Republic Duration: Mar 21 2009 → Mar 27 2009

All Science Journal Classification (ASJC) codes

General Physics and Astronomy

Access to Document

10.1088/1742-6596/219/4/042051

Cite this

@article{8eae4b25483a4ab2aba4ee13740c46f0,

title = "CMS partial releases: Model, tools, and applications online and framework-light releases",

abstract = "With the integration of all CMS software packages into one release, the CMS software release management team faced the problem that for some applications a big distribution size and a large number of unused packages have become a real issue. TWe describe a solution to this problem. Based on functionality requirements and dependency analysis, we define a self-contained subset of the full CMS software release and create a Partial Release for such applications. We describe a high level architecture for this model, and tools that are used to automate the release preparation. Finally we discuss the two most important use cases for which this approach is currently implemented.",

author = "Jones, {Christopher D.} and David Lange and Emilio Meschi and Shahzad Muzaffar and Andreas Pfeiffer and Natalia Ratnikova and Elizabeth Sexton-Kennedy",

year = "2010",

doi = "10.1088/1742-6596/219/4/042051",

language = "English (US)",

volume = "219",

journal = "Journal of Physics: Conference Series",

issn = "1742-6588",

publisher = "IOP Publishing Ltd.",

number = "1 PART 4",

note = "17th International Conference on Computing in High Energy and Nuclear Physics, CHEP 2009 ; Conference date: 21-03-2009 Through 27-03-2009",

}

TY - JOUR

T1 - CMS partial releases

T2 - 17th International Conference on Computing in High Energy and Nuclear Physics, CHEP 2009

AU - Jones, Christopher D.

AU - Lange, David

AU - Meschi, Emilio

AU - Muzaffar, Shahzad

AU - Pfeiffer, Andreas

AU - Ratnikova, Natalia

AU - Sexton-Kennedy, Elizabeth

PY - 2010

Y1 - 2010

N2 - With the integration of all CMS software packages into one release, the CMS software release management team faced the problem that for some applications a big distribution size and a large number of unused packages have become a real issue. TWe describe a solution to this problem. Based on functionality requirements and dependency analysis, we define a self-contained subset of the full CMS software release and create a Partial Release for such applications. We describe a high level architecture for this model, and tools that are used to automate the release preparation. Finally we discuss the two most important use cases for which this approach is currently implemented.

AB - With the integration of all CMS software packages into one release, the CMS software release management team faced the problem that for some applications a big distribution size and a large number of unused packages have become a real issue. TWe describe a solution to this problem. Based on functionality requirements and dependency analysis, we define a self-contained subset of the full CMS software release and create a Partial Release for such applications. We describe a high level architecture for this model, and tools that are used to automate the release preparation. Finally we discuss the two most important use cases for which this approach is currently implemented.

UR - http://www.scopus.com/inward/record.url?scp=77955403211&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=77955403211&partnerID=8YFLogxK

U2 - 10.1088/1742-6596/219/4/042051

DO - 10.1088/1742-6596/219/4/042051

M3 - Conference article

AN - SCOPUS:77955403211

SN - 1742-6588

VL - 219

JO - Journal of Physics: Conference Series

JF - Journal of Physics: Conference Series

IS - 1 PART 4

M1 - 042051

Y2 - 21 March 2009 through 27 March 2009

ER -

CMS partial releases: Model, tools, and applications online and framework-light releases

Abstract

All Science Journal Classification (ASJC) codes

Access to Document

Other files and links

Fingerprint

Cite this