1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.0 Transitional//EN">
4 <meta http-equiv=
"CONTENT-TYPE" content=
"text/html; charset=UTF-8">
5 <title>glideinWMS Installation Guide
</title>
6 <meta name=
"CREATED" content=
"0;0">
7 <meta name=
"CHANGED" content=
"20100521;20081031;14115200">
8 <link rel=
"stylesheet" type=
"text/css" href=
"common/glideinWMS.css" media=
"screen, projection" />
11 <body lang=
"en-US" dir=
"ltr">
13 <a href=
"index.html">GlideinWMS
</a>
14 <span>The Glidein-based Workflow Management System
</span>
16 <ul class=
"breadcrumbs">
17 <li><a href=
"index.html">Home
</a></li>
21 <div class=
"leftmenu">
22 <ul class=
"components">
23 <li> <a href=
"./index.html">Home
</a></li>
24 <li> <a href=
"./download.html">Download
</a></li>
25 <li> <a href=
"./frontend/index.html">Glidein Frontend
</a></li>
26 <li> <a href=
"./corral.html">Corral Frontend
</a></li>
27 <li> <a href=
"./factory/index.html">WMS Factory
</a></li>
28 <li> <a href=
"./components/index.html" >Components
</a></li>
29 <li> <a href=
"./components/faq.html" class=
"last">FAQ
</a></li>
32 <div id=
"cse-search-form" style=
"width: 100%;">Loading
</div>
33 <script src=
"http://www.google.com/jsapi" type=
"text/javascript"></script>
34 <script src=
"./common/glidein.js" type=
"text/javascript"></script>
35 <script type=
"text/javascript">
36 google
.load('search', '1', {language
: 'en', style
: google
.loader
.themes
.MINIMALIST
});
37 google
.setOnLoadCallback(onLoad
);
41 <div id=
"searchcontent"><h2>Search Results
</h2><div id=
"cse"></div> </div>
44 <img align=
"right" width=
"280px" border=
"0px"
45 src=
"./images/simple_diagram.png" usemap=
"#rightimage">
46 <map name=
"rightimage">
47 <area shape=
"rect" coords=
"90,3,177,60" href=
"frontend/index.html" />
48 <area shape=
"rect" coords=
"5,88,118,146" href=
"components/collector_install.html" />
49 <area shape=
"rect" coords=
"134,88,275,146" href=
"factory/index.html" />
50 <area shape=
"rect" coords=
"189,3,274,60" target=
"_blank" href=
"./corral.html" />
54 <ul class=
"subcomponents">
55 <li> <a href=
"./index.html">Overview
</a></li>
56 <li> <a href=
"./download.html">Download
</a></li>
57 <li> <a href=
"./documentation.html">Documentation
</a></li>
59 <li> <a href=
"./history.html">History
</a></li>
60 <li class=
"last"> <a href=
"./license.html">License
</a></li>
67 <li> <a href=
"#process">Installation Process
</a></li>
68 <li> <a href=
"#documents">Additional documents
</a></li>
69 <li> <a href=
"#configuration">Possible Configurations
</a></li>
70 <li> <a href=
"#osg">Connecting to OSG Factory
</a></li>
74 Installation at a glance:
76 <li><a href=
"./components/prerequisites.html">Pre-requisites
</a></li>
77 <li><a href=
"./factory/install.html">WMS Collector and Factory
</a></li>
78 <li><a href=
"./components/collector_install.html">User Pool Collector
</a> </li>
79 <li><a href=
"./components/pool_install.html">User Pool Schedd
</a> </li>
80 <li><a href=
"./frontend/install.html">Glidein Frontend
</a> </li>
82 <!-- Commenting this out as it will not be available until next version.
83 <a href="components/configuration_install.html">Configuration based installer.</a><br/>
85 <a href=
"upgrade.html">Upgrade Guide
</a><br/>
89 <h3>Installation Process
</h3>
90 <p>Installation of glideinWMS is
91 a multi-step process:
</p>
93 <li><a href=
"components/prerequisites.html">Components and Pre-requisites
</a>:
94 Includes a consolidated table of requirements for each server.
96 <li><a href=
"factory/install.html">The glidein WMS Collector and
97 collocated glidein Factory node
</a> </li>
99 <li><a href=
"components/collector_install.html">The glidein pool Collector
101 <li><a href=
"components/pool_install.html">One or more scheduler nodes for
102 user submission
</a> </li>
103 <li><a href=
"frontend/install.html">The Glidein Frontend
</a> </li>
106 The above process should suffice for typical installs. More information can be found below.
</p>
107 <!-- Commenting this section out as it will not be available until the
109 <h3>Configuration based installer</h3>
111 Alternatively, you can use the <a href="components/configuration_install.html">Configuration based installer.</a> This approach requires filling out a
112 configuration file (ini file) with all the required fields up front. Once
113 this is done, you can install each component using the tool and this ini file.
114 It prevents the frustration of running the Q&A installer multiple times
115 in case of errors.</p>
117 <b>Important Note:</b> You can only use either the Q&A installer to install all components or the configuration based installer to install all components. You cannot mix installations by installing partially with the Q&A installer and partially with the configuration installer.
118 Also, note that both installers assume you are performing a full installation of all components. For upgrades, see the <a href="upgrade.html">upgrade guide</a>
119 or contact glidein support.
123 <div class=
"section">
124 <a name=
"documents" />
126 <h3>Additional Documents:
</h3>
128 <li><a href=
"components/prerequisites.html">Component Installation
</a>: Installation tips for components needed by glideinWMS, such as HTTP, VDT, JavascriptRRD, etc.
</li>
129 <li><a href=
"components/condor.html#gcb">Installation of a GCB node
</a>: (only if
130 you are gliding into Grid sites with restrictive network policies
131 and cannot use CCB)
<br/>
132 <b>NOTE:
</b> It is strongly recommended to use CCB over GCB if possible.
136 <a href=
"components/gsi.html">Quick Reference Guide to GSI Authentication Setup in glideinWMS
</a>:
137 for information on how to configure the GSI security, and additional GSI configuration.
140 <a href=
"components/condor.html#schedds">Multiple Schedds
</a> for increased scalability.
144 <a href=
"components/condor.html#quill">Quill setup
</a> for older condor installs.
147 <a href=
"frontend/troubleshooting.html">Troubleshooting Frontend
</a> installation problems and
148 <a href=
"factory/troubleshooting.html">Troubleshooting Factory
</a> installation problems.
151 <a href=
"components/faq.html">Frequently Asked Questions
</a> for advanced configuration tips.
156 <img src=
"./images/glideinWMS_at_a_glance_medium.png">
157 <div class=
"section">
158 <a name=
"configurations" />
159 <h3>Possible Configurations
</h3>
160 <p>While the documents presented here assume you will install each
161 component on a different machine, there is nothing preventing you
162 from installing all of them on fewer machines, or even on one machine
163 only (excluding GCB, but you should not use it anyhow). Note that
164 only configurations with the WMS collector and factory on the
165 same node are supported. Also note that worker nodes must be
166 able to access the web server on the factory node in order to
167 download neccessary files.
168 It should be noted that it is possible to install the glideinWMS
169 across administrative boundaries (i.e. you will only install part
170 of the glideinWMS infrastructure). See the OSG section below for
173 Several possible configurations are below:
175 <p><b>Two Server configuration
</b> (recommended minimum):
177 <li><a href=
"factory/install.html">The glidein WMS Collector and collocated
178 glidein Factory node
</a> </li>
180 <li>A node containing the
<a href=
"frontend/install.html">Glidein Frontend
</a>,
181 the
<a href=
"components/collector_install.html">glidein pool Collector
</a> together with the
<a href=
"components/pool_install.html">scheduler for user submissions
</a>
186 <p><b>Three Server configuration
</b> (recommended for
1000+ glideins)
189 <li><a href=
"factory/install.html">The glidein WMS Collector and collocated
190 glidein Factory node
</a> </li>
191 <li>A node containing the
<a href=
"components/collector_install.html">glidein pool Collector
</a> together with the
<a href=
"frontend/install.html">VO
193 <li>A node containing the
<a href=
"components/pool_install.html">scheduler for user
194 submissions
</a> </li>
198 <p><b>One Server configuration
</b> (Use only for test installs)
200 <li><a href=
"factory/install.html">The glidein WMS Collector and collocated
201 glidein Factory node
</a>, with the collector running on
8618.
202 <a href=
"frontend/install.html">Glidein Frontend
</a>,
203 the
<a href=
"components/collector_install.html">glidein pool Collector
</a>
204 (running on
9618) together with the
<a href=
"components/pool_install.html">scheduler for user submissions
</a>.
205 With this configuration, take special care of the ports assigned and of the condor.sh currently sourced
206 when running commands.
209 <p><a name=
"osg"/><b>OSG Factory configuration
</b></p>
211 Members of the Open Science Grid can use the OSG factory at UCSD.
212 In this case, only the following installation is necessary:
214 <li><a href=
"components/collector_install.html">
215 glidein pool Collector
217 <li><a href=
"components/pool_install.html">
218 scheduler for user submissions
220 <li><a href=
"frontend/install.html">Glidein Frontend
</a></li>
224 See
<a target=
"_blank" href=
"http://hepuser.ucsd.edu/twiki2/bin/view/UCSDTier2/OSGgfactory">OSG Glidein Factory
</a> for more details on how to use this setup.
233 <a href=
"http://www.flickr.com/people/leafwarbler/">Madhusudan Katti
</a>
234 used under Creative Commons license.
<br/>
235 Original Home URL:
<a href=
"http://www.uscms.org/SoftwareComputing/Grid/WMS/glideinWMS">http://www.uscms.org/SoftwareComputing/Grid/WMS/glideinWMS
</a>.
236 glideinWMS email support: glideinwms-support at fnal.gov