170 likes | 194 Views
This workshop presentation discusses the installation, management, and publication of CMS software on the Open Science Grid (OSG) in a dynamic and efficient manner. Topics covered include software installation issues, validation considerations, and handling user requests.
E N D
EGEE/OSG OPS. Workshop-3 Sep. 28, 2005 Dynamic Application Installation(Case of CMS on OSG) • Introduction • CMS Software Installation Overview • Software Installation Issues • Validation Considerations • Publication of Software Installation • Considering User Request • Summary Bockjoo Kim U of Florida
Introduction • Application software can be installed without publication and notification • If software installation could be organized and managed in a consistent manner, one could share the responsibility and efficiently use the grid resources. • This presentation shows how CMS software that is used by the CMS collaboration for physics analyses can be installed, maintained, and published on OSG in a managed way • LCG counter part is doing this on LCG
An Overview of CMS Software Deployment on OSG GridCat Client CSD-GUI : X509 Persistent Interface MySQL DB CMS Grid Users GridCat Deploy Scripts Local Scripts Submit Condor-G Grid Middle Ware Local Scripts $app CMSI Tool Discovery Service RPMs A Remote Site CSD-GUI OSG IS CMSI Tool RPMs CMS IS CMS CMSI Repository
CMS Software Installation Tool • is used to install CMS softwares • xcmsi is a tool to install CMS software written in PERL • Arbitrary installation directory $CMS_PATH to relocate RPM packages • No root privileges required • Typically 1 GCC compiler, 1 SCRAM (Soft. Management Tool), ~40 CMS RPMs, ~30 LCG RPMs. ~4 GB space • Essential ingredients to the installation are the RPMs
A Schematic of OSGAuthorization and Resources MDS+GIP Publish $app OSG Monitoring
Implementation of CSD-GUI(CMS Software Deployment Grid User Interface for USCMS) HTTPS MySQL voms proxy globus client CGI OSG Client/Condor-G GUI script(python) GridCat Client condor_submit/condor_q undo upload. csd upload condor_q/rm undo install. csd install. undo verify csd verify create info file Installation Table check arch Execution Scripts Site Info.
CSD-GUI Features • Managed Software Installation • Persistent Installation Task • Installation Control Using X509 Proxy • Installation Bookkeeping Using MySQL • Publish Installation Info in Text -> • GIP and CMSSoftDB • Switch Between OSG-ITB and OSG • Undo in CSD-GUI MySQL Operation/GIP/CMSSoftDB • Non-DAG/Single Job Submission for Success
Software Installation Issues • Different Linux Flavors • 64-bit at 32-bit mode • Network Insulation • Missing Client Tools on WN, e.g., wget, pm • Different Shared File Systems • Some applications are sensitive to them • Issues have to be fed back
Site Specific Issues • Dedicated Slot (Busy Site) • Dedicated CPU slot • Dedicated Time slot • Disk Space Issue : • Problem disk • Soft-linking • Problem resolution occurs : • IM • Phone • Email • GOC
Validation • A series of particular applications should run successfully • Only partial validation is possible • An iterative process from user feedback and testing • Different validation procedures can provide redundant
Publishing Software Installation • Three different types of publications • GIP publication : Job submission time discovery • OSG publication (grid3 style) favored by USAtlas : Job submission time discovery • CMSSoftDB : for just in time discovery
Considering User Demand • What if a user wants a particular version of software to be installed on weekends or holidays. • A request submission interface is necessary ? • How to authorize the request ? • What if site admin wants to install it ? --> Everything is done through emails/meetings at the moment
Summary (1) • Managed/Persistent CMS software installation on OSG is performed • Interoperability is considered for both OSG and LCG job submission in mind • Local Installation Information for Discovery Service • Non-trivial Sites to be handled with different methods and special arrangement
Summary (2) • Use Real Physics Analysis for Validation • More validation is required as more grid users will try to use the installation • Versatile deployment (retiring old and deploying new) options should be considered • With a careful planning and communications with counter part, dynamic software installation can be used for interoperable job submission