2.0 Downloading Legion 1.8

Legion 1.8 is available in binary form only. Information about downloading 1.8 is on the Legion web site (<http://legion.virginia.edu/download/index.html>) and below. Legion is currently available for the following platforms:

  • Sun Workstation/Solaris 5.7 or later (solaris)
  • SGI Workstations/IRIX 6.5 n32 build or later (sgi_n32)1
  • SGI Workstations/IRIX 6.5 n64 build or later (sgi_n64)
  • x86/Red Hat 6.x Linux (linux)
  • DEC Alpha/Red Hat Linux 6.x (alpha_linux)
  • DEC Alpha/OSF1 v4 (alpha_DEC)
  • IBM RS6000/AIX 4.3 (rs6000)
  • HPUX 11.x (hppa_hpux)2

Legion has been ported to several Cray IEEE architectures (C90, T90, T3E) using the native Cray C++ compiler. However, the binaries produced are excessively large, due to a compiler bug. Therefore, we are not releasing a binary version of Legion for the Cray platform. You can start a virtual host on these machines (see page 69).

We are no longer supporting the x86/FreeBSD 4.2 platform, although we will consider adding it back in if someone needs it. We are not currently supporting a Windows platform.

The Legion software is currently available to qualified educational, research, and commercial customers. However, we ask that any interested users submit the following information:

  1. Your full name, e-mail address, phone number, and mailing address.
  2. Your organization or university's full name and (if applicable) line of business.
  3. A brief description of what you wish to do with Legion (applications you wish to use or develop, research you wish to pursue, etc.).

This will be used to determine appropriate licensing agreements only and will not be distributed or sold to any outside parties. Please send it via e-mail to <legion@virginia.edu>.

If you are interested in a corporate license, Avaki (<www.avaki.com>) is the corporate distributor of Legion software.

2.1 Legion structure

As of version 1.8, Legion has been restructured. It is now split into packages. This change does not affect any tools or context space, but you may need to update paths in makefiles or change library paths from previous Legion versions. You need to run extra commands to start up some of the packages (see page 21).

  1. Core: This is the basic Legion package and the minimum for running a Legion system. It lets you start up and shut down Legion, work in context space, run Legion security, etc.
  2. Software Development Kit (SDK): This contains development-oriented tools and libraries, such as the stub generator, Legion Grid library, LegionArray library, etc. This package is not necessary if you aren't planning on writing Legion applications.
  3. High-Performance Computing (HPC): The HPC module lets you run your programs in Legion. It contains PVM and MPI tools, the two-dimensional FileObject interfaces, JobProxy and JobQueue objects, batch queue class and host object, and legion_run and legion_run_multi.
  4. Extra: This adds functionality to the basic Legion package. It contains the round robin scheduler, simple k-copy class (SKCC), process control daemon host objects, etc. It is not necessary, but it gives you more control over your objects. You must have the HPC package in order to use the Apps package.
  5. Applications (Apps): The Apps package also extends the basic Legion package. The current version gives you more flexibility in moving files between Legion and your desktop, via legion_export_dir and the Legion FTP daemon.

2.2 Space requirements

You will need about 250-300MB of free disk space and at least 256MB virtual memory (we suggest 512MB, if possible) on your bootstrap node in order to run Legion.

2.3 Software requirements

You must have /bin/ksh installed in your system. There are a number of Legion scripts that will look for ksh, and if it is not installed in your system you will get error messages.

Depending on your platform and package, you will need a set of GNU tools (all available from <http://www.gnu.org>). The NT/2000 platform doesn't need any GNU tools. See Downloading binary files for lists of tools for untarring binary files.

2.4 RSA and OpenSSL

Current Legion release use public key cryptography based on the RSA 2.0 algorithm, as implemented by OpenSSL. You will need to download OpenSSL 0.9.5 or higher from <www.openssl.org>. You'll need to untar, configure, and compile it. Be sure that you set your $OPENSSL_INC and $OPENSSL_LIB variables to the correct directory. Suggested values are:

(ksh or sh users)

export OPENSSL_INC=<OpenSSL installation directory>/include
export OPENSSL_LIB=<OpenSSL installation directory>/lib

(csh users)

setenv OPENSSL_INC <OpenSSL installation directory>/include
setenv OPENSSL_LIB <OpenSSL installation directory>/lib

2.5 Downloading binary files

All Legion distribution binaries are compressed tar files created with GNU tar and gzip. Using a non-gnu tar program may result in some files names being truncated. You can download these tools for free from GNU at <http://www.gnu.org>.

Decide where you want your Legion root directory to reside and move the distribution file to that directory. Next, uncompress and untar the file (<platform_name> is one of {solaris, sgi_n32, sgi_n64, linux, alpha_linux, alpha_DEC, rs6000, hppa_hpux}). The binaries files are all compressed tar files created with GNU tar and gzip.

If you have GNU tar you can unzip and untar the binary by running:

tar zxvf Legion-binary-<platform_name>-V1.8.tar

If you do not have GNU tar, you must use gunzip (part of GNU gzip package). Run the following:

gunzip -c Legion-binary-<platform_name>-V1.8.tar.gz | tar -xvf -

This will create a root directory called "Legion" in the current directory, and will include all necessary sub-directories and files.

Note that the compressed binary files are large (ranging from 12 to 100+ MB), so it may take a few minutes for them to arrive, and that the uncompressed tar file will be about two to three times larger. The system will actually need even more space once it is running, since it will be making copies of some of the files. In addition, the binary tar files do not include intermediary object files, which will be created when the system is started.


1. We have previously supported SGI Workstations IRIX o32 build (sgi_o32) but it is not available in this release. Please contact us at <legion-help@virginia.edu> if you have any questions.

2. The HPUX 11 platform is available upon request. We will include an HPUX 10 platform in a future release.

Directory of Legion 1.8 Manuals
[Home] [General] [Documentation] [Software]
[Testbeds] [Et Cetera] [Map/Search]

Free JavaScripts provided by The JavaScript Source

legion@Virginia.edu
http://legion.virginia.edu/