File: install.html

package info (click to toggle)
cctools 3.5.1-2
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 5,704 kB
  • sloc: ansic: 49,398; cpp: 15,568; perl: 12,324; sh: 2,668; python: 1,422; makefile: 632; yacc: 433; lex: 152; xml: 109
file content (114 lines) | stat: -rw-r--r-- 3,877 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
<html>
<head>
<title>Installing the Cooperative Computing Tools</title>
</head>

<body>
<h1>Installing the Cooperative Computing Tools</h1>

<b>Last Modified October 2011</b>
<p>
The Cooperative Computing Tools are Copyright (C) 2003-2004 Douglas Thain and Copyright (C) 2005-2011 The University of Notre Dame.  This software is distributed under the GNU General Public License.  See the file COPYING for details.

<h2>Overview</h2>

The Cooperative Computing Tools (cctools) are a collection of programs designed to
assist users with the difficulties of building and managing complex,
fault-prone distributed systems.  The components of the cctools are:

<dir>
<li> <a href=parrot.html>Parrot</a> - A personal virtual file system.
<li> <a href=chirp.html>Chirp</a> - A distributed file and storage system.
<li> <a href=makeflow.html>Makeflow</a> - A workflow engine similar to Make.
<li> <a href=workqueue.html>Work Queue</a> - A flexible master-worker library.
<li> <a href=sand.html>SAND</a> - A scalable genome assembly framework.
<li> <a href=allpairs.html>All-Pairs</a> - A computational abstraction.
<li> <a href=wavefront.html>Wavefront</a> - A computational abstraction.
</dir>

This short manual describes how to install the cctools.
For more information about the tools themselves, see the links above.

<h2>Installing</h2>

The cctools may already be installed on your system.
Simply run <tt>chirp -v</tt>.  If you see something like

<pre>
chirp version 1.0.1 built by dthain@hedwig on Sep 12 2004 at 20:04:51
</pre>

then the cctools are installed, and you are ready to go.
Otherwise, you must install the cctools yourself.

<h3>Installation From a Binary Package</h3>

From any other location, we recommend that you install a binary
package from the <a href=http://www.cse.nd.edu/~ccl/software/download.shtml>cctools web page</a>
Simply unpack the tarball in any directory that you like,
and then add the <tt>bin</tt> directory to your path.
For example, to install in $HOME/cctools:

<pre>
% cd $HOME
% gunzip cctools-xxx-yyy.tar.gz
% tar xvf cctools-xxx-yyy.tar
% setenv PATH $HOME/cctools/bin:$PATH
</pre>

<h3>Installation From a Source Package </h3>

Building the CCTools from source is very easy.
Just download a source package:

<dir>
<li> <a href=http://www.cse.nd.edu/~ccl/software/download.shtml>CCTools Download</a>(Required)
</dir>

And follow this recipe while logged in as any ordinary user:

<pre>
% gunzip cctools-xxx-src.tar.gz
% tar xvf cctools-xxx-src.tar
% cd cctools-xxx-src
% ./configure
% make
% make install
% setenv PATH ${HOME}/cctools/bin:$PATH
</pre>

The software will happily build and run without installing
any external packages.  Optionally, the cctools will interoperate
with a variety of external packages for security and data access.
To use these, you must download and install them separately:

<dir>
<li> <a href=http://fuse.sourceforge.net>FUSE</a> (Optional)
<li> <a href=http://hadoop.apache.org>Hadoop</a> (Optional)
<li> <a href=http://xrootd.slac.stanford.edu>xRootD</a> (Optional)
<li> <a href=http://www.irods.org>iRODS</a> (Optional)
<li> <a href=http://web.mit.edu/kerberos>Kerberos</a> (Optional)
<li> <a href=http://www.globus.org>Globus</a> (Optional) (Tested with Globus 2.2, 2.4, and 4.0.)
<li> <a href=http://glite.web.cern.ch/glite/packages/R3.0>EGEE GLite</a> (Optional)
</dir>

Once the desired packages are correctly installed, unpack the cctools and
then issue a configure command that points to all of the other
installations.  Then, make and install.  For example:

<pre>
% gunzip cctools-xxx.tar.gz
% tar xvf cctools-xxx.tar
% cd cctools-xxx
% ./configure --with-krb5-path /usr/kerberos --with-globus-path /usr/local/globus ...
% make
% make install
% setenv PATH ${HOME}/cctools/bin:$PATH
</pre>

<dir>
<a href=index.html>Cooperative Computing Tools Documentation Index</a>
</dir>

</body>
</html>