C H A P T E R 3 |
Installing the Software |
This chapter discusses installing the Sun Shared Visualization 1.1 software and supporting software. Topics include:
Note - Unless stated otherwise, the majority of examples provided in this chapter are for the Solaris 10 Operating System. |
The Sun Shared Visualization Software 1.1 supports different use models and administration models, as described in Software Overview. The supplied installation script installs the software needed by most sites and optionally installs software for use with Sun Grid Engine.
Note - If you are sure you do not need to install Sun Grid Engine and Sun Shared Visualization optional extensions for Sun Grid Engine, you can begin installation with the procedures in Installing Sun Shared Visualization 1.1 Software. |
Before installation, identify your shared visualization resources:
Note - Sun Grid Engine was formerly called Sun N1 Grid Engine. Some documentation for the current product includes the earlier name. |
Sun Shared Visualization 1.1 software includes optional software for use with Sun Grid Engine:
You might not need Sun Grid Engine if your site has only one Sun Shared Visualization 1.1 server and that server has only one graphics accelerator. However, if you have multiple servers or multiple graphics accelerators, Sun Grid Engine can allocate these resources to users with load balancing.
If you are using Sun Grid Engine, you need to determine which hosts are:
All Sun Grid Engine hosts will NFS mount the SGE installation from this NFS server.
All graphics servers should be execution hosts, but you might have additional execution hosts that do not offer shared visualization services.
All shared visualization clients are typically Sun Grid Engine submit hosts.
If the Advance Reservation facility is installed, only one host must be the Advance Reservation server.
Note - A single host can have multiple roles. |
Note - Sun Shared Visualization 1.1 software does not include Sun Grid Engine. This software is available from:
http://www.sun.com |
1. Install and configure hardware, operating systems, and windowing systems on each host.
Ensure that the graphics servers have supported hardware and operating system versions. Ensure that the latest drivers for the graphics accelerators are installed and patched.
2. Install visualization applications on graphics servers and computation applications on Sun Grid Engine execution hosts.
Or, applications can be remotely mounted as needed.
Note - Licensing and appropriate use of all visualization applications is entirely the responsibility of the user. |
3. If you are using Sun Ray thin clients, install the Sun Ray Server software and configure any Sun Ray servers.
Refer to Appendix A for additional guidelines.
4. If your site is using Sun Grid Engine, install Sun Grid Engine on the site’s NFS server.
Instructions to help you install and configure Sun Grid Engine are provided in Installing the Sun Grid Engine Software.
1. If your site is using Sun Grid Engine, install the Sun Shared Visualization 1.1 software, including the optional software, on the NFS server host for the Sun Grid Engine installation.
See Installing Sun Shared Visualization 1.1 Software.
2. Install the Sun Shared Visualization 1.1 software on all graphics servers.
The Sun Grid Engine optional software is not installed on these servers. Instead, these servers mount the optional software from the NFS server.
3. Configure each system planned to be a graphics server.
See Chapter 4.
4. Test use of VirtualGL (and, optionally, TurboVNC) on each Sun Shared Visualization 1.1 server.
See Chapter 3 of the Sun Shared Visualization 1.1 Software Client Administration Guide.
5. If your site is using Sun Grid Engine, add graphics to Sun Grid Engine.
See Adding Graphics to Sun Grid Engine.
6. If your site is using Sun Grid Engine and Advance Reservation, configure the Advance Reservation server on a single host.
See Advance Reservation.
This section describes installing the Sun Grid Engine software. These instructions are streamlined for installations particular to the Sun Shared Visualization 1.1 software.
Complete Sun Grid Engine documentation, including an installation guide, is available at:
http://docs.sun.com/app/docs/coll/1017.3
To Prepare to Install the Sun Grid Engine Software |
This procedure is for installations on all Solaris and Linux servers.
1. Determine which host is to be the queue master (qmaster) and which host is to be the NFS server for your grid.
If the resources are available, the same host can perform both roles.
2. Determine which hosts are to be the execution hosts for your grid.
If the resources are available and these systems are configured with graphics accelerators, the execution hosts can also be the graphics servers.
Note - Execution hosts need the korn shell, ksh. Solaris hosts include ksh by default, but Linux hosts might need ksh to be installed. |
3. Determine your installation root directory.
The package default is /gridware/sge, however the Sun Grid Engine documentation calls this <sge_root> or /sge_root. These instructions use the variable, $SGE_ROOT.
4. Become superuser of the NFS server and declare the variable:
If you chose a different installation root directory in Step 3, type that directory name instead of /gridware/sge.
5. Create the base directory for $SGE_ROOT if the path has multiple directory components:
6. Determine an SGE administrative login that can be used on all systems intended to be administration hosts.
For example, you might plan to use these parameters:
$SGE_ROOT
|
|
The Sun Grid Engine administrator can have a different user ID than sgeadmin. However, the administrative user ID (530 in this example) must be available across all hosts in the grid.
On SuSE hosts, group 4 (adm) might not already be defined in /etc/group. In that case, you need to add that group.
7. Create the sgeadmin user on the NFS server for your grid.
Use the values you selected in Step 6, as in this example::
8. Assign the sgeadmin user a password:
9. Append the following lines to the sgeadmin .cshrc file:
if ( $?prompt == 1 ) then if ( -f /gridware/sge/default/common/settings.csh ) then source /gridware/sge/default/common/settings.csh endif endif |
Replace /gridware/sge with the value of $SGE_ROOT if different.
Note - You cannot use the $SGE_ROOT variable in Step 9, as the variable will not be set in a fresh shell until the settings.csh file is sourced. |
You might choose to do the same for root’s .cshrc or .tcshrc, or the equivalent file for root’s shell.
10. Continue the installation of software on the NFS server by performing one of these procedures:
To Install the Software on a Solaris System |
1. Permit $SGE_ROOT to be shared (exported) by the NFS server.
If your base directory of $SGE_ROOT is already shared, you do not need to perform this step.
On the Solaris NFS server, append the following line to the /etc/dfs/dfstab file:
where /gridware is the base directory of your $SGE_ROOT.
2. Inform the operating system of the changes you have made:
3. If the system automounts using the hosts map, you can test the accessibility of the $SGE_ROOT directory from other systems on the network with this command:
4. From each server in the grid, access the NFS server’s $SGE_ROOT as each server’s $SGE_ROOT using /etc/vfstab, /etc/fstab, or automounting.
a. Add the following line to the /etc/auto_direct file:
where /gridware is the base directory of your $SGE_ROOT. If the NFS client prefers NFS version 4 but the NFS server does not, this line might also need the nfs=3 option.
b. Ensure that the /etc/auto_master or the auto_master NIS map contains this entry:
You must determine an available port on the qmaster system. Sun Grid Engine components will use this port to communicate with the qmaster daemon. This port must be a single port number that is available on all current or prospective submit and execution hosts in your grid.
These port numbers can be any value, but the following port numbers have been assigned by the Internet Assigned Number Authority (IANA):
Note - For more information about IANA, see:
http://www.iana.org/assignments/port-numbers |
If you are running a firewall on any execution host, ensure that the execution daemon’s port allows traffic in.
6. Communicate the port numbers to the hosts.
These port numbers can be communicated to the hosts involved either by inserting the port numbers into every host’s /etc/inet/services or /etc/services file, or by setting Sun Grid Engine environment variables. The latter method, detailed in Step 4 of To Complete the Software Installation, is more convenient, because each Sun Grid Engine user already needs to use a Sun Grid Engine environment setup file. If you allow Sun Grid Engine to use this setup file, you will not have to add sge entries into every host’s services file.
To use this environment variable technique, set these environment variables before you invoke ./install_qmaster in Step 2 of To Complete the Software Installation. Use the port numbers determined in Step 5 in place of 6444 and 6445 in these commands:
The lines you include in the setup file for Sun Grid Engine will be executed by Step 5 of To Complete the Software Installation. (After installation, you will need to ensure that the setup file’s set and export environment variables are naming SGE_QMASTER_PORT and SGE_EXECD_PORT.)
7. As superuser of the NFS server, install the Sun Grid Engine packages into $SGE_ROOT.
The NGS server will need both Sun Grid Engine architecture-independent common files and architecture-dependent files for the architecture of every submit and execution host. (Each architecture is a pairing of processor instruction set and operating system.) You might also choose to install documentation files.
These files can be installed from Solaris packages on a Solaris system or from RPM packages on a Linux system. Files for additional nonnative architectures need to be installed from tar bundles, which is explained in Step 1 of To Complete the Software Installation.
Refer to TABLE 3-1, which lists commonly used Sun Grid Engine 6.1 Solaris software packages and the download files that contain those packages. If you are installing a release other than Sun Grid Engine 6.1, the download file names will refer to that version instead of reading 6_1. Also, newer versions of Sun Grid Engine might use file names that say sge instead of n1ge.
To install Sun Grid Engine from the packages you selected, first unzip the download files. then install each package by typing a pkgadd command line such as this:
For all packages, answer all questions about where Sun Grid Engine should be installed with the value you chose for $SGE_ROOT.
Note - Some of these packages install setuid or setgid files for which pkgadd asks for permission. This permission should be granted. |
8. Perform the steps in To Complete the Software Installation.
To Install the Software on a Linux System |
1. Permit $SGE_ROOT to be shared (exported) by the NFS server.
If your base directory of $SGE_ROOT is already shared, you do not need to perform this step.
On the Linux NFS server, append the following line to the /etc/exports file:
where /gridware is the base directory of your $SGE_ROOT.
2. Inform the operating system of the changes you have made:
3. If the system automounts using the hosts map, you can test the accessibility of the $SGE_ROOT directory from other systems on the network with this command:
4. From each server in the grid, access the NFS server’s $SGE_ROOT as each server’s $SGE_ROOT using /etc/vfstab, /etc/fstab, or automounting.
a. Add the following line to the /etc/fstab file:
Your Linux system might also need the no_root_squash option in this line.
where /gridware is the base directory of your $SGE_ROOT.
You must determine an available port on the qmaster system. Sun Grid Engine components will use this port to communicate with the qmaster daemon. This port must be a single port number that is available on all current or prospect submit and execution hosts in your grid.
These port numbers can be any value, but the following port numbers have been assigned by the Internet Assigned Number Authority (IANA):
Note - For more information about IANA, see:
http://www.iana.org/assignments/port-numbers |
If you are running a firewall on any execution host, ensure that the execution daemon’s port allows traffic in.
6. Communicate the port numbers to the hosts.
These port numbers can be communicated to the hosts involved either by inserting the port numbers into every host’s /etc/inet/services or /etc/services file or by setting Sun Grid Engine environment variables. The latter method, detailed in Step 4 of To Complete the Software Installation, is more convenient, because each Sun Grid Engine user already needs to use a Sun Grid Engine environment setup file. If you allow Sun Grid Engine to use this setup file, you will not have to add sge entries into every host’s services file.
To use this environment variable technique, set these environment variables before you invoke ./install_qmaster in Step 2 of To Complete the Software Installation. Use the port numbers determined in Step 5 in place of 6444 and 6445 in these commands:
The lines you include in the setup file for Sun Grid Engine will be executed by Step 5 of To Complete the Software Installation. (After installation, you will need to ensure that the setup file’s set and export environment variables are naming SGE_QMASTER_PORT and SGE_EXECD_PORT.)
7. As superuser of the NFS server, install the Sun Grid Engine packages into $SGE_ROOT.
The NGS server will need both Sun Grid Engine architecture-independent common files and architecture-dependent files for the architecture of every submit and execution host. (Each architecture is a pairing of processor instruction set and operating system.) You might also choose to install documentation files.
These files can be installed from RPM packages on a Linux system. Files for additional nonnative architectures need to be installed from tar bundles, which is explained in Step 1 in To Complete the Software Installation.
Refer to TABLE 3-2, which lists commonly used Sun Grid Engine 6.1 Linux software RPM packages and the download files that contain those packages. If you are installing a release other than Sun Grid Engine 6.1, the download file names will refer to that version instead of reading 6_1. Also, newer versions of Sun Grid Engine might use file names that say sge instead of n1ge.
To install each of the RPM packages you selected, type an rpm command line such as this:
8. Perform the steps in To Complete the Software Installation.
To Complete the Software Installation |
This procedure is for installations on all Solaris and Linux servers.
1. Install additional Sun Grid Engine tar bundles of files needed by hosts with a different operating system than the NFS server.
TABLE 3-3 lists Sun Grid Engine 6.1 software tar bundles, which can install nonnative software on a Solaris or Linux NFS server. Use these bundles to install software on an NFS server as needed to support hosts with a different operating system. (Newer versions of Sun Grid Engine might use file names that say sge instead of n1ge.)
Architecture independent files (required, but was already installed from packages on the NFS server) |
|
Linux kernel 2.4 or 2.6, glibc >= 2.3.2, for AMD Opteron and Intel EM64T |
|
Microsoft Windows[1] |
|
Accounting and Reporting Console (ARCo) for all architectures, not needed for the core product |
|
Sun Web Console, required for ARCo, Solaris, for 64-bit SPARC |
After you download the additional software you need, you can install the contents of each tar.gz file in the $SGE_ROOT directory with a command such as this:
If you installed any of the tar bundles mentioned in this step, you will need to answer n when the installation script asks (as in Step 3):
Did you install this version with >pkgadd< or did you already verify and set the file permissions of your distribution (enter: y) |
2. On the queue master host, type:
The Sun Grid Engine installation script begins.
3. The script prompts you for information and requests confirmation of selected values.
As you progress through the script, consider the following:
Note - The installation script might instead ask this question: “Do you want to install Grid Engine under a user id other than >root<? (y/n) [y]”. Answer y. Later, you are asked for the user ID, which can be sgeadmin (as created in Step 6 of To Prepare to Install the Sun Grid Engine Software). |
Execution hosts and the queue master must agree on the primary name of the execution host. If the execution host and the queue master do not agree on hostnames, a host_aliases file in the $SGE_ROOT directory enables SGE to understand that certain names are equivalent. For example, a host_aliases file might include this line:
Every host name on this line is considered equivalent to the first name on the line (myhost1), which is the primary host name. For more details, see the Sun Grid Engine man page for host_aliases (5).
In addition, Sun Grid Engine requires that a host’s unique hostname is associated with a true IP address, not the localhost address 127.0.0.1.
Or, ask your administrator for a reasonable range of unused group IDs. Sun Grid Engine uses the group IDs for each of the parallel jobs that are running at a given time.
4. Update environment variables in settings files.
If you decided to communicate the port numbers to all SGE hosts using SGE’s environment setup file, you now need to assure that SGE sets the correct port numbers for environment variables SGE_QMASTER_PORT and SGE_EXECD_PORT. (You would have made that choice at Step 6 of To Install the Software on a Solaris System or Step 6 of To Install the Software on a Linux System, and would have determined the port numbers in the step before these steps.)
You might find that the proper variable values were written when you ran install_qmaster.
a. Edit the SGE settings file for csh or tcsh.
The file is $SGE_ROOT/default/common/settings.csh.
b. In the settings.csh file, look for lines such as these:
If you find such lines, change them to use your port numbers.
You determined the port numbers in Step 5 of To Install the Software on a Solaris System or Step 5 of To Install the Software on a Linux System. For example, change the lines to the following:
c. Edit the SGE settings file for sh, bash, and ksh.
The file is $SGE_ROOT/default/common/settings.sh
d. In the settings.sh file, look for lines such as these:
If you find such lines, change them to use your port numbers.
For example, change the lines to the following:
The settings files contain the lines to unset these environment variables by default. This default behavior is desirable if you if had instead decided to enter the port numbers in every SGE host’s /etc/services or /etc/inet/services file.
5. Source the file to set up your environment to use Sun Grid Engine.
Substitute /gridware/sge with your value of $SGE_ROOT. Consider having root’s .login do so.
Substitute /gridware/sge with the $SGE_ROOT. Consider having root’s .profile or .bashrc do so.
6. Create the sgeadmin user on each of the other administration hosts of the grid:
Note - Unlike Step 7 of To Prepare to Install the Sun Grid Engine Software, the -m option is not needed for these other administration hosts. Assign the sgeadmin a password, as in Step 8 of that procedure. |
Alternatively, you can add the sgeadmin entries to the respective /etc/passwd and /etc/shadow files.
7. As superuser on every execution host, set the SGE_ROOT environment variable and then type:
You might need to create the execution host’s default spooling directory. As superuser on the NFS server, type:
The same value for exec-hostname is needed in the procedure To Set Up Sun Grid Engine Environment Variables
8. After the environment is set up, submit a test job.
To specify the job to execute on your host:
Job output and errors are in the initiating user’s home directory, with filenames similar to the following:
To Set Up Sun Grid Engine Environment Variables |
Use one of the following commands:
Substitute /gridware/sge with your $SGE_ROOT.
Substitute /gridware/sge with your $SGE_ROOT.
Note - These commands add $SGE_ROOT/bin/$ARCH to $path, add $SGE_ROOT/man to $MANPATH, set $SGE_ROOT, and if needed set $SGE_CELL to $COMMD_PORT. |
Messages from Sun Grid Engine can be found in:
After the startup the daemons log messages in the spool directories.
$SGE_ROOT/default/spool/qmaster/messages
$SGE_ROOT/default/spool/exec-hostname/messages
To Verify Your Administrative Hosts |
To Add Administrative Hosts |
To Obtain Current Status |
To Start the Sun Grid Engine GUI |
1. Ensure that your DISPLAY environment variable is set appropriately.
The section describes how to install the Sun Shared Visualization 1.1 software, and how to remove the software on Solaris and Linux systems. (Instructions for installing and removing this software on Windows and Mac OS X clients is provided in the Sun Shared Visualization 1.1 Software Client Administration Guide.)
If you are installing the Sun Shared Visualization 1.1 software onto a Linux host, you might see the following error if using the automounter with default options, or you have noexec in the CD-ROM mount entry of the /etc/fstab file:
bash: ./install: /bin/bash: bad interpreter: Permission denied
To prevent this error, change the noexec option to exec, or mount the CD-ROM manually using the exec option.
To Install the Sun Shared Visualization 1.1 Software |
1. Decide what source to use for installing this software.
2. Install this software from a download directory.
a. As superuser, change to that directory and extract each desired zip file.
See TABLE 3-4 for the names of each available zip file and the name of the directory where the expanded files will be installed:
TurboVNC-version.dmg[2] |
The directory structure is created and the files are extracted.
b. Change to the installation directory you selected from TABLE 3-4:
c. Continue to Step 4.
3. Install this software from a CD-ROM.
a. As superuser, insert the Sun Shared Visualization 1.1 CD-ROM into an optical drive that is connected to your system.
If your system is running the volume manager, continue to Step b. Otherwise, type the following commands:
Solaris - A path such as /dev/dsk/c0t6d0s2, obtained by running the rmformat command, but using dsk rather than rdsk
b. Change to the installation directory with a cd command.
The name of this directory varies.
c. Continue to Step 4.
4. Run the installation script:
Sun Microsystems, Inc. ("Sun") ENTITLEMENT for SOFTWARE Licensee/Company: Entity receiving Software. Effective Date: Date of delivery of the Software to You. .... |
The script displays the licensing agreement, and asks:
5. To proceed with software installation, type y.
After agreement, the script begins installation:
This program installs the software for the Sun Shared Visualization 1.1 Copyright 2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. |
The script checks for a newer version of the Sun Shared Visualization 1.1 software. If the script finds one, the script displays:
This system has a higher version of Sun Shared Visualization software than is available in this Release. Sun Shared Visualization software from this release will not be installed. |
Otherwise, the script begins adding packages and asks you:
Note - The names of the packages shown here are for Solaris 10 versions. |
6. If you are installing on the NFS server for your Sun Grid Engine, answer y. Otherwise, answer n and go to Step 8.
Press "Return" to accept the above path location or Enter the desired install base directory path location [default install path: /gridware/sge, ? for help] [?,q] |
7. If the value of $SGE_ROOT is not displayed or is different than /gridware/sge, type the new value and press Return.
Note - Optional software is only installed if you answered y at Step 6 |
8. Press Return to continue installation.
The script begins installing required patches, packages, and optional software:
Note - Optional software is only installed if you answered y at Step 6 |
The script informs you how to remove the software, and where a log file of the installation is located:
The log file is named with a date and time stamp. In this example, December 22, 2007 at 9:52am.
9. If your Sun Shared Visualization 1.1 server is also your Sun Ray server, refer to the section, Improving Sun Ray Image Quality at the Expense of Performance.
10. (Optional) If you are going to use the Sun Shared Visualization 1.1 software with Sun Grid Engine, see Adding Graphics to Sun Grid Engine.
To Remove the Sun Shared Visualization 1.1 Software |
You might need to remove the Sun Shared Visualization 1.1 software in the future. This procedure explains how. (Instructions for installing and removing this software on Windows clients is provided in the Sun Shared Visualization 1.1 Software Client Administration Guide.)
1. Take one of the following actions:
The script starts and identifies the software packages that are to be removed.
All required software for the Sun Shared Visualization Software software will be REMOVED. The following packages will be removed: SUNWsge3D SUNWsgearsmr SUNWsgeau SUNWvglsr SUNWvgl SUNWtvnc SUNWvrpt |
To cancel removal of this software, press ’q’ followed by a Return. **OR** Press Return key to begin package removal: |
2. Press Return to begin package removal.
Pressing the Q key and the Return key aborts the script.
The script does a search for the installed packages and displays the progress.
The script concludes and tells you where a log file of the removal is located.
The log file is named with a date stamp. In this example, December 22, 2007.
Displayed image quality is typically improved by sending uncompressed images to the Sun Ray server for compression and transfer to the Sun Ray desktop unit (DTU). Compared to using the VirtualGL Sun Ray plug-in, this approach improves image quality, but decreases performance. The performance decrease is less severe when the Sun Ray server is also the Sun Shared Visualization 1.1 graphics server, but the performance change is still noticeable. See Appendix A for more information.
The VirtualGL Sun Ray plug-in can be disabled by using the -c proxy option with vglrun or by setting the environment variable VGL_COMPRESS to proxy. See the appendix, VirtualGL Reference, of the Sun Shared Visualization 1.1 Software Client Administration Guide, 820-3257.
Alternatively, the VirtualGL Sun Ray plug-in can be disabled for all users on the server by removing the SUNWvglsr package after installing the Sun Shared Visualization 1.1 software. Once removed, VirtualGL does not use compression and the Sun Ray X server is responsible for sending the images to the Sun Ray clients.
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.