Peach Installation

System Requirements:

• Peach is written with a minimum requirement of Perl 5.8. On systems with Perl 5.6 (such as SGI IRIX, an additional 3 perl modules need to be installed on to the system: MIME::Base64, Digest  and Digest::MD5 have to be installed in this order.
• Starting of the server and job daemons requires root permissions.
• There must be at least one common shared disk to all participating computers.
  
• Shared disk mount points have to be the same on all participating computers.
• Eg.  If a shared disk is accessible on a computer by typing cd /disk1, then any other participating computer which mounts this disk must also allow access by typing cd /disk1.
• Unix User ID(UID) and Group ID(GID) have to be the same on all participating computers.
• Eg.  User leong has a UID of 273 and GID of 116 on all participating computers.
• This requirement is normally fulfilled if the network is using a NIS system.
• Programs to be run on Peach must have the same program directory names on computers of the same operating platform.
• Eg.  If a program called bint is found on a Darwin operating system at /disk1/Darwin/bin/bint, then another computer with a Darwin operating system must have the same program accessed from /disk1/Darwin/bin/bint.

Installation Steps:

1. Log on to the computer which will be used as the server.
• The server may be moved to a different computer at a later time.
  
2. Download the Peach package (Peach.tar.gz)
• The software is available at the Peach website.
  
3. Extract the Package
• Unzip Peach.tar.gz using tar: tar -xvzf Peach.tar.gz
• The package will be written to a directory called Peach in your current directory.
4. Run the Installation Script (install.pl)
• Change to the directory called Peach: cd Peach
• This directory called Peach will be refered to as the installation directory from now onwards
• Before proceeding, decide which directory to install the Peach system onto
• This directory (full path), which you will choose, will be refered to as the program directory from now onwards
• The program directory must be on a shared disk that is accessible by all participating computers.
• Decide on the primary administrative user.
• This user will have administrative access to the Peach system.
• The primary administrative user must run the installation script.
• Additional or secondary administrative users may be added to the configuration files at a later time.
  
• Decide on the network setup.
• During installation, a port number will need to be selected.
  
• This port is the port at which the server will bind to.
• The first available port on this computer will be suggested by the installation script.
• The user has the option to choose a port other than the suggested port or change it at a later time.
  
• During installation, a list of shared disks will need to be selected.
• The installation script will search for all mounted disks.
• The user will have the choice to accept any number of these disks.
• The user will also need to enter the mount points of the accepted shared disks.
• Changes in the mount points or the addition of shared disks may be performed at a later time.
  
• Once you have collected the information for these options type: ./install.pl program_directory
• Example: install.pl /home4/EMprogs/Peach where /home4/EMprogs/Peach is on a shared disk that is accessible to all participating computers
• In some cases, you will require root access to create your program directory. 
  
• Using root access or by logging on to the computer which holds the shared disk, create the directory. 
  
• Return back to the administrative user's account on the server computer to re-run the installation script.
  
• An example installation session
  
5. Starting up the Peach server
   
• Once the installation is complete, the Peach directory should be specified in an environmental variable, "PEACH" (e.g., setenv PEACH /home4/EMprogs/Peach) in the following global resource files on each computer:
• Darwin: /etc/csh.cshrc
• OSF1: /etc/csh.login
• IRIX: /etc/cshrc
• Linux: ?
  
• Log on to the computer which will run the Peach server with any user which has root privileges.
  
• Change to the Peach directory, type: cd program_directory
• When using the root account, run the server by typing: pserv -verbose
• When using a non-root account: run the server by typing: sudo pserv -verbose
  
• For safety reasons, the administrative user will be required to verify the last change of the files.
• The last message will say: "pserv start up complete at IP_ADDRESS:PORT"
• IP_ADDRESS will be the IP address of the of the server
• PORT will be the port number of the server
• Only one job server can exist at a time
• An example pserv startup
  
6. Installing job daemon startup scripts and starting them:
• Log on to the computer which will run the Peach job daemon with any user which has root privileges.
• Change to the Peach program directory, type: cd program_directory
• When using the root account, run the job daemon by typing: pjobd
• When using a non-root account, run the job daemon by typing: sudo pjobd
• The job daemon will automatically generate startup scripts to enable starting up when a computer reboots
• The job daemon will ask if the startup on reboot should be switched on or off
  
• A message will say: pjobd start up complete
• Only one job daemon can be run per participating computer
7. Check the system:
• Change to the Peach program directory, type: cd program_directory
• Once the system is started, type pview to monitor the system
• Pview provides you with an interface to monitor the system
• Press h for help
• Pview can be run on any computer with access to the programs directory and where the environmental variable PEACH is defined.
  
8. Configure the System to run programs:
• An empty .Peachpath is provided in the program directory
• Environmental variables required to run programs must be defined in the .Peachpath file in the program directory.
• Programs will not run if the environmental variables have not been set.
  
• Path information should be entered as follows:
• Darwin:
  $ENV{PATH} = "/bin:/sbin:/usr/bin:/usr/sbin";
  $ENV{LD_LIBRARY_PATH} = "/disk1/Darwin/lib";
  
• The name before the colon and the Path variable is the operating system name.
• Available operating systems include:
• Darwin: Mac OS X (G4, G5)
• IRIX64: SGIs
  
• OSF1: Alphas
  
• Linux i686: PCs
  
• Linux x86_64: AMD64s
9. Adding Users
• The administrator must login to any computer with access to the program directory
• Users can be added by typing ppass username uid gid in the program directory where username, uid and gid are the name, user ID and group ID of the new Peach user.
• The UID and GID must be the same on all participating computers.
  
10. Change the PATH variable
• Edit your shell resource file (eg. .tcshrc, .bashrc, cshrc) with full_path_of_program_directory
• Or temporarily add this to your path
• Tcsh or csh: setenv PATH  $PATH:full_path_of_program_directory
  
• Bash or sh: PATH= $PATH:full_path_of_program_directory
11. Submit a test job
• To submit jobs type: psubmit command_line
• Example: psubmit touch test.txt
• It is important to note that psubmit can only be used with the shared disks specified earlier
  
12. Troubleshooting
• The mount point for each shared disk must be the same on all computers.
  
• Access is controlled by user name and password and every Peach program requires password access.
  
• Each user must have the same user id and group id on all their accounts on different computers.
• All environmental variables required for all programs must be correctly defined in .Peachpath.
• Always check that the limits on the shell launching the job daemon are big enough