1.0 Introduction

1.1 About this manual

This manual is an introduction to Legion 1.8. It gives instructions for logging in to an active Legion system and a high-level introduction to Legion context space. Users who need to install or start a Legion system should consult the System Administrator Manual. If you need more help please contact us (page 109).

There are four Legion manuals, each aimed at a specific type of user, that can be consulted for more information. The others are:

  • System Administrator Manual: information and documentation for administrators of Legion systems, including installing and running Legion, configuring security features, resource management, and managing a Legion system.
  • Developer Manual: information and documentation for programmers working in Legion, and includes information on languages, libraries, core objects, and implementing new Legion objects.
  • Reference Manual: detailed information about specific elements of the Legion system.

There are also man pages for all Legion commands included with the system files. To view a man page, type the following on the command line:

$ man <command name>

There are on-line tutorials on the Legion web site (http://legion.virginia.edu).

This manual assumes that you are working on a previously installed, compiled, and running system.1 Before going any further, be sure that the system is properly installed and running. Check with your system administrator if you are unsure.

1.2 Style conventions

The manuals at times refer to path names in Unix directory space and in Legion context space. The following style conventions are used:

  • Unix, DOS, and local path names appear in this typeface.
  • Functions, method names, parameters, flags, command-line utilities (such as rm, cp, and legion_ls), and context path names appear in fixed typeface.

1.3 About Legion

Developed at the University of Virginia, Legion is a grid operating system. While fully supporting existing codes written in MPI and PVM, Legion provides features and services that allow users to take advantage of much larger, more complex resource pools. A user can easily run a computation on a supercomputer at a national center while dynamically visualizing the results on a local machine, or schedule and run a large parameter space study on several workstation farms simultaneously. For example, computational scientists can use cycles wherever they are, allowing bigger jobs to run in shorter times through higher degrees of parallelization.

Key capabilities include the following:

  • Legion eliminates the need to move and install binaries manually on multiple platforms. After Legion schedules a set of tasks over multiple remote machines, it automatically transfers the appropriate binaries to each host. A single job can run on multiple heterogeneous architectures simultaneously; Legion will ensure that the right binaries go to each, and that it only schedules onto architectures for which it has binaries.
  • Legion provides a virtual file system that spans all the machines in a Legion system. Input and output files can be seen by all the parts of a computation, even when the computation is split over multiple machines that don't share a common file system. Different users can also use the virtual file system to collaborate, sharing data files and even accessing the same running computations.
  • Legion's object-based architecture dramatically simplifies building add-on tools for tasks such as visualization, application steering, load monitoring, and job migration.
  • Legion provides optional privacy and integrity of communications for applications distributed over public networks. Multiple users in a Legion system are protected from one another.

These features also make Legion attractive to administrators looking for ways to increase and simplify the use of shared high-performance machines. The Legion implementation emphasizes extensibility, and multiple policies for resource use can be embedded in a single Legion system that spans multiple resources or even administrative domains.


1. It is actually not always necessary to have a Legion system running in order to use Legion: some Legion hosts can run as client hosts in a larger Legion system. A client host does not have the full set of Legion system binaries, but a set of binary executable files that can contact other Legion hosts in its Legion system. Please e-mail us at <legion-help@virginia.edu> for more information.

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/

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/