| blob | 90b1df8e4950a1148b71ff12b5f1cbdc0bcc02cb |
2 <html>
3 <head>
9 </head>
12 <h1>
15 </h1>
19 </ul>
30 </ul>
38 </script>
39 </div>
40 </div>
51 </map>
60 </ul>
63 </div>
64 </div>
67 <ol>
71 </ol>
72 </div>
74 <ul>
76 </ul>
77 </div>
81 <p><b>Corral is a lightweight frontend for glideinWMS. It is useful for individuals and when running across national cyberinfrastructures such as OSG and TeraGrid. It is also a useful tool when running
83 </b></p>
84 <p>Although much work has been done in developing the national cyberinfrastructure in support of science, there is still a gap between the needs of the scientific applications and the capabilities provided by the resources. Leadership-class systems are optimized
85 for highly-parallel, tightly coupled applications. Many scientific applications, however, are composed of a large number of loosely-coupled individual components, many with data and control dependencies. Running these complex, many-step workflows robustly
86 and easily still poses difficulties on today?s cyberinfrastructure. One effective solution that allows applications to efficiently use the current cyberinfrastructure is resource provisioning using Condor glideins.
87 </p>
88 <p>GlideinWMS was initially developed to meet the needs of the CMS (Compact Muon Solenoid) experiment at the Large Hadron Collider (LHC) at CERN. It generalizes a Condor glideIn system developed for CDF (The Collider Detector at Fermilab) and first deployed
89 for production in 2003. It has been in production across the Worldwide LHC Computing Grid (WLCG), with major contributions from the Open Science Grid (OSG) in support of CMS for the past two years, and has recently been adopted for user analysis. GlideinWMS
90 also is currently being used by the CDF, DZero, and MINOS experiments, and servicing the NEBioGrid and Holland Computing Center communities. GlideinWMS has been used in production with more than 12,000 concurrently running jobs; the CMS use alone totals over
92 <p>Corral, a tool developed to complement the Pegasus Workflow Management System was recently built to meet the needs of workflow-based applications running on the TeraGrid. It is being used today by the Southern California Earthquake Center (SCEC) CyberShake
93 application. In a period of 10 days in May 2009, SCEC used Corral to provision a total of 33,600 cores and used them to execute 50 workflows, each containing approximately 800,000 application tasks, which corresponded to 852,120 individual jobs executed on
94 the TeraGrid Ranger system. The 50-fold reduction from the number of workflow tasks to the number of jobs is due to job-clustering features within Pegasus designed to improve overall performance for workflows with short duration tasks.
95 </p>
96 <p>The integrated system provides a robust and scalable resource provisioning service that supports a broad set of domain application workflow and workload execution environments. The aim is to integrate and enable these services across local and distributed
97 computing resources, the major national cyberinfrastructure providers (Open Science Grid and TeraGrid), as well as emerging commercial and community cloud environments.
98 </p>
100 </p>
101 </div>
104 <p>There are two parts to a fully working, a frontend and a factory. The frontend in this case is Corral, whereas the factory can either be installed locally, or you can use a hosted version at UCSD.</p>
105 <p>Installing the frontend is done by downloading the Corral frontend tar ball, untarring it and setting the CORRAL_HOME environment variable to point to the new install. Also add $CORRAL_HOME/bin to your path. The host your are deploying on should have GSI
106 set up (host cert, grid-mapfile, ...).</p>
108 <p>The submit host has to be set up to accept the glideins registering. This requires enabling GSI as an authentication method and it is pretty straightforward if the machine is not already part of a bigger pool. Replace the certificate DNs with the ones from
109 your host and user certificate. Example condor_config.local file:</p>
110 <pre>
111 ############################################################
112 ## GSI Security config
113 ############################################################
115 ############################
116 # Authentication settings
117 ############################
118 SEC_DEFAULT_AUTHENTICATION = REQUIRED
119 SEC_READ_AUTHENTICATION = OPTIONAL
120 SEC_WRITE_AUTHENTICATION = REQUIRED
121 SEC_CLIENT_AUTHENTICATION = OPTIONAL
122 SEC_DEFAULT_AUTHENTICATION_METHODS = FS,GSI
123 SEC_ENABLE_MATCH_PASSWORD_AUTHENTICATION = True
124 DENY_WRITE = anonymous@*
125 DENY_ADMINISTRATOR = anonymous@*
126 DENY_DAEMON = anonymous@*
127 DENY_NEGOTIATOR = anonymous@*
128 DENY_CLIENT = anonymous@*
130 ############################
131 # Privacy settings
132 ############################
133 SEC_DEFAULT_ENCRYPTION = OPTIONAL
134 SEC_DEFAULT_INTEGRITY = REQUIRED
135 SEC_READ_INTEGRITY = OPTIONAL
136 SEC_CLIENT_INTEGRITY = OPTIONAL
137 SEC_READ_ENCRYPTION = OPTIONAL
138 SEC_CLIENT_ENCRYPTION = OPTIONAL
140 # Grid Certificate directory
141 GSI_DAEMON_TRUSTED_CA_DIR=/etc/grid-security/certificates
143 ############################
144 # Set daemon cert location
145 ############################
146 GSI_DAEMON_DIRECTORY = /etc/condor
148 ############################
149 # Credentials
150 ############################
151 GSI_DAEMON_CERT = /etc/grid-security/hostcert.pem
152 GSI_DAEMON_KEY = /etc/grid-security/hostkey.pem
154 #################################
155 # Where to find ID->uid mappings
156 #################################
157 CERTIFICATE_MAPFILE=/etc/condor/condor_mapfile
159 #####################################
160 # Add whitelist of condor daemon DNs
161 #####################################
162 GSI_DAEMON_NAME=/DC=org/DC=doegrids/OU=Services/CN=yggdrasil.isi.edu,/DC=org/DC=doegrids/OU=People/CN=Mats Rynge 274484
164 #####################################################
165 # With strong security, do not use IP based controls
166 #####################################################
167 HOSTALLOW_WRITE = *
168 ALLOW_WRITE = $(HOSTALLOW_WRITE)
170 #####################################
171 # Limit session caching to ~12h
172 #####################################
173 SEC_DAEMON_SESSION_DURATION = 50000
174 </pre>
176 <pre>
180 GSI (.*) anonymous
181 FS (.*) \1
182 </pre>
184 </div>
188 <p>The way to tell Corral about your glidein needs, a XML configuration files is needed. Example:</p>
189 <pre>
219 <!-- List of entries for the grid-mapfile for the glideins. Include the daemon
220 certificate of the collector, and the certificate of the user submitting the glideins. -->
223 <entry>"/DC=org/DC=doegrids/OU=Services/CN=cmws-corral.isi.edu" condor002</entry>
229 </pre>
233 <pre>
234 $ corral create-provisioner -h cwms-corral.isi.edu -f firefly.xml
235 </pre>
238 <pre>
239 $ corral list-provisioners -h cwms-corral.isi.edu
241 </pre>
244 <pre>
245 $ corral remove-provisioner -h cwms-corral.isi.edu
246 </pre>
249 </div>
251 Banner image by
253 used under Creative Commons license.<br/>
254 Original Home URL: <a href="http://www.uscms.org/SoftwareComputing/Grid/WMS/glideinWMS">http://www.uscms.org/SoftwareComputing/Grid/WMS/glideinWMS</a>.
255 glideinWMS email support: glideinwms-support at fnal.gov
256 </div>
257 </body>
258 </html>