Sun Shared Visualization 1.1 Software Server Administration Guide

This chapter discusses installing the Sun Shared Visualization 1.1 software and supporting software. Topics include:

• Installation Summary
• Installing the Sun Grid Engine Software
• Installing Sun Shared Visualization 1.1 Software
• Improving Sun Ray Image Quality at the Expense of Performance

---

Installation Summary

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.

Planning Your Sun Shared Visualization Environment

Before installation, identify your shared visualization resources:

• Graphics application servers, which run applications under control of VirtualGL and optionally run TurboVNC servers on demand.
• Shared graphics accelerator devices, which are installed on the graphics application servers.
• Shared visualization client hosts.
• Shared visualization client users, who start VirtualGL and TurboVNC clients and optionally submit jobs to Sun Grid Engine.

Sun Grid Engine

Sun Shared Visualization 1.1 software includes optional software for use with Sun Grid Engine:

• Sun Grid Engine graphics extensions
• Advance Reservation facility for 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:

• Queue master server for Sun Grid Engine
• NFS server for the Sun Grid Engine installation

All Sun Grid Engine hosts will NFS mount the SGE installation from this NFS server.

• Sun Grid Engine execution hosts

All graphics servers should be execution hosts, but you might have additional execution hosts that do not offer shared visualization services.

• Sun Grid Engine administration hosts
• Sun Grid Engine submit hosts

All shared visualization clients are typically Sun Grid Engine submit hosts.

• Advance Reservation server

If the Advance Reservation facility is installed, only one host must be the Advance Reservation server.

Summary of Preparatory Steps

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.

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.

Summary of the Installation Process

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.

---

Installing the Sun Grid Engine Software

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

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.

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:

# setenv SGE_ROOT /gridware/sge

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:

# mkdir /gridware

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:

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::

# useradd -u 530 -g 4 -d $SGE_ROOT -m -s /bin/tcsh -c "Sun Grid Engine Admin" sgeadmin

8. Assign the sgeadmin user a password:

# passwd sgeadmin

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.

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
• 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 Solaris NFS server, append the following line to the /etc/dfs/dfstab file:

share -F nfs /gridware

where /gridware is the base directory of your $SGE_ROOT.

2. Inform the operating system of the changes you have made:

• For Solaris 10 (or later) OS:


# svcadm -v restart nfs/server


• For Solaris releases earlier than Solaris 10:


# /etc/init.d/nfs*server stop ; /etc/init.d/nfs*server start

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:

# ls /net/nfsserverhostname/$SGE_ROOT

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:

/gridware  -rw,suid,bg,hard,noquota,intr nfsserverhostname:/gridware

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:

/-     auto_direct

c. Restart the automounter:

• For the Solaris 10 (or later) OS:


# svcadm -v restart autofs


• For Solaris releases earlier than Solaris 10:


# /etc/init.d/autofs stop ; /etc/init.d/autofs start

5. Determine port numbers.

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):

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:

# setenv SGE_QMASTER_PORT 6444
# setenv SGE_EXECD_PORT   6445

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:

# pkgadd -d downloaddirectory packagename 

For all packages, answer all questions about where Sun Grid Engine should be installed with the value you chose for $SGE_ROOT.

8. Perform the steps in To Complete the Software Installation.

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:

/gridware     *(rw,sync,no_root_squash)

where /gridware is the base directory of your $SGE_ROOT.

2. Inform the operating system of the changes you have made:

• For SuSE Linux:


# /etc/init.d/nfs*server stop ; /etc/init.d/nfs*server start


• For Red Hat Linux:


# /etc/init.d/nfs restart

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:

# ls /net/nfsserverhostname/$SGE_ROOT

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:

nfsserverhostname:/gridware    /gridware  nfs        auto,suid,bg,intr          0 0

Your Linux system might also need the no_root_squash option in this line.

b. Type these two commands:

# mkdir /gridware
# mount /gridware

where /gridware is the base directory of your $SGE_ROOT.

5. Determine port numbers.

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):

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:

# setenv SGE_QMASTER_PORT 6444
# setenv SGE_EXECD_PORT   6445

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:

# rpm -iv /path-to-rpm-file/sun-nlge-rest-of-filename.rpm

8. Perform the steps in 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.)

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:

# gunzip -c nlge-6_1-platform.tar.gz | (cd $SGE_ROOT; tar xf -)

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:

# cd $SGE_ROOT ; ./install_qmaster

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:

• The Sun N1 Grid Engine 6 Installation Guide has a table to help plan and record the answers to the questions asked during installation. For the simplest installation, accept all the defaults not discussed in the following text, unless your $SGE_ROOT is not /gridware/sge.
• The installation script asks: "Do you want to install Grid Engine as admin user >sgeadmin<? (y/n)". Answer y, so that all spool files are created as owned by that user. This answer avoids a problem where an execution host’s root becomes nobody over NFS and therefore cannot access the spooling directories.

• The installation script asks: “Did you install this version with >pkgadd< or did you already verify and set the file permissions of your distribution (enter: y)”. If you installed exclusively from packages, answer y. If you installed even partially from tar files (as in Step 1) or other means, answer n, and the install_qmaster script sets the file permissions appropriately.
• The installation script asks: "Are all hosts of your cluster in a single DNS domain (y/n)". Unless you are certain that you need domain checking, answer y. Sun Grid Engine then ignores domain components when comparing hostnames.

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:

myhost1 my1 myhost1-ib my1-ib

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.

• Select to use the BerkeleyDB, but do not configure a separate BerkeleyDB server.
• If your site uses NIS, a usable group ID range can be determined by studying the output of:


# ypcat -k group.bygid | sort -n | more

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.

• When prompted for administrative and submit hosts, include the name of the queue master host as an administrative and submit host, unless you forbid submissions from that host.
• You can create a shadow host that takes over for the qmaster if it becomes unavailable. This action is optional.
• Use the following command to add administrative hosts (which might be configured to be execution hosts) if those hosts were omitted:


# qconf -ah hostname, anotherhost


• You can display the administrative host list by typing:


# qconf -sh


• You can add submit hosts by typing:


# qconf -as myhost,anotherhost,stillmore


• Typing the following displays the submit host list:


# qconf -ss

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:

unsetenv SGE_QMASTER_PORT
unsetenv SGE_EXECD_PORT

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:

setenv SGE_QMASTER_PORT 6444
setenv SGE_EXECD_PORT   6445

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:

unset SGE_QMASTER_PORT
unset SGE_EXECD_PORT

If you find such lines, change them to use your port numbers.

For example, change the lines to the following:

SGE_QMASTER_PORT=6444;   export SGE_QMASTER_PORT
SGE_EXECD_PORT=6445;     export SGE_EXECD_PORT

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.

• For tcsh/csh users, type:


% source /gridware/sge/default/common/settings.csh

Substitute /gridware/sge with your value of $SGE_ROOT. Consider having root’s .login do so.

• For sh/bash/ksh users, type:


$ . /gridware/sge/default/common/settings.sh

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:

# useradd -u 530 -g 4 -d $SGE_ROOT -s /bin/tcsh -c "Sun Grid Engine Admin" sgeadmin

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:

# cd $SGE_ROOT ; ./install_execd

You might need to create the execution host’s default spooling directory. As superuser on the NFS server, type:

# mkdir $SGE_ROOT/default/spool/exec-hostname

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:

exechost% qsub -q all.q@‘hostname‘ $SGE_ROOT/examples/jobs/simple.sh
exechost% qstat -f

Job output and errors are in the initiating user’s home directory, with filenames similar to the following:

simple.sh.e1			simple.sh.o1

  Use one of the following commands:

• For tcsh and csh users, type:


% source /gridware/sge/default/common/settings.csh

Substitute /gridware/sge with your $SGE_ROOT.

• For sh, bash, and ksh users, type:


$ . /gridware/sge/default/common/settings.sh

Substitute /gridware/sge with your $SGE_ROOT.

Messages from Sun Grid Engine can be found in:

• /tmp/qmaster_messages (during Sun Grid Engine queue master startup)
• /tmp/execd_messages (during Sun Grid Engine exec daemon startup)

After the startup the daemons log messages in the spool directories.

• Sun Grid Engine queue master:

$SGE_ROOT/default/spool/qmaster/messages

• Sun Grid Engine execution daemon:

$SGE_ROOT/default/spool/exec-hostname/messages

  Type:

# qconf -sh

  Type:

# qconf -ah hostname

  Type:

# qstat -f

1. Ensure that your DISPLAY environment variable is set appropriately.

2. Type:

# qmon &

---

Installing Sun Shared Visualization 1.1 Software

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.

1. Decide what source to use for installing this software.

• If you are installing the software from a download directory, perform Step 2.
• If you are installing the software from the CD-ROM, perform Step 3.

2. Install this software from a download directory.

a. As superuser, change to that directory and extract each desired zip file.

# cd /path/to/download/directory
# unzip SharedVisualization_1.1_name.zip

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:

The directory structure is created and the files are extracted.

b. Change to the installation directory you selected from TABLE 3-4:

# cd Shared_Visualization_1.1_version

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:

# mkdir -p /cdrom/SSV1.1
# mount -F hsfs -o ro device /cdrom/SSV1.1

where device is:

Solaris - A path such as /dev/dsk/c0t6d0s2, obtained by running the rmformat command, but using dsk rather than rdsk

Linux - /dev/cdrom

b. Change to the installation directory with a cd command.

The name of this directory varies.

• For Solaris, go to /cdrom/ssv_1.1:


# cd /cdrom/ssv_1.1


• For Red Hat, go to /cdrom/ssv_1.1 (or /cdrom/SSV_1.1 or /media/cdrom or whatever name is provided by your version of the operating system):


# cd /cdrom/ssv_1.1


• For SuSE, the dot in 1.1 might be replaced with an underscore character, so go to /media/ssv_1_1 (or /media/dvd or whatever name is provided by your version of the operating system):


# cd /media/SSV1_1

c. Continue to Step 4.

4. Run the installation script:

# ./install

The script begins:

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:

...
Agreement. No modification of this Agreement will be binding, unless in writing
and signed by an authorized representative of each party.
 
Please contact Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, 
California 95054 if you have questions.
 
 
Do you accept the license agreement? [y/n]:

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:

application SUNWsge3D    Sun N1 Grid Engine Graphic Extensions
application SUNWsgearsmr Sun N1 Grid Engine Graphic Advance Reservations
application SUNWsgeau    Sun N1 Grid Engine Graphic Advance Reservations (Usr)
 
Do you wish to install the optional Software (SUNWsge3D SUNWsgeau
SUNWsgearsmr)?  [y,n,?,q]

6. If you are installing on the NFS server for your Sun Grid Engine, answer y. Otherwise, answer n and go to Step 8.

• If you installed the Sun Grid Engine software into the default directory, you see this message:


Install script has determine that the Grid Engine Product install directory as: /gridware/sge


• If you installed the Sun Grid Engine software into a directory other than the default (/gridware/sge), or if the Sun Grid Engine software is not installed at all, you might see this message:


Unable to determine the installation directory for the Grid Engine Product. Using default path of /gridware/sge.

The script continues:

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.

The script informs you:

This script is about to take the following actions:
- Install Sun Shared Visualization Software 
- Install Optional Software (SUNWsge3D SUNWsgeau SUNWsgearsmr)
  using the installation path: /gridware/sge 
 
To cancel installation of this software, press ’q’ followed by a Return.
	 **OR**
Press Return key to begin installation: 

8. Press Return to continue installation.

The script begins installing required patches, packages, and optional software:

*** Installing Sun Shared Visualization Software for Solaris 10...
Installing required packages:
	SUNWtvnc SUNWvgl SUNWvglsr SUNWvrpt
 
Installation of <SUNWtvnc> was successful.
Installation of <SUNWvgl> was successful.
Installation of <SUNWvglsr> was successful.
Installation of <SUNWvrpt> was successful.
 
*** Installing selected optional software for Solaris...
Installing optional package(s):
	SUNWsge3D SUNWsgeau SUNWsgearsmr
 
Installation of <SUNWsge3D> was successful.
Installation of <SUNWsgeau> was successful.
Installation of <SUNWsgearsmr> was successful.
 
*** Installation complete.

The script informs you how to remove the software, and where a log file of the installation is located:

To remove this software, use the ’remove’ script on this CDROM, or
the following script:
 
	/var/tmp/SharedVis_remove
 
A log of this installation can be found at:
	/var/tmp/SharedVis.install.2007.12.22.0952

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.

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:

• If you are running the removal script from the Sun Shared Visualization 1.1 server, as superuser, type:


# /var/tmp/SharedVis_remove


• If you are running the removal script from the CD-ROM, as a Solaris or Linux superuser, first insert, mount, and change directories (with the cd command) to the CD-ROM as done in Step 3 of To Install the Sun Shared Visualization 1.1 Software. Then type one of these commands:


# SharedVisualization_1.1/Solaris/remove

Or:

# SharedVisualization_1.1/Linux/remove

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

The script asks:

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.

*** Found the following packages to remove:
              SUNWsge3D SUNWsgearsmr SUNWsgeau SUNWvglsr SUNWvgl SUNWtvnc SUNWvrpt
*** Removing old package(s)...
 
Removal of <SUNWsge3D> was successful.
 
Removal of <SUNWsgearsmr> was successful.
 
Removal of <SUNWsgeau> was successful.
 
Removal of <SUNWvglsr> was successful.
 
Removal of <SUNWvgl> was successful.
 
Removal of <SUNWtvnc> was successful.
 
Removal of <SUNWvrpt> was successful.

The script concludes and tells you where a log file of the removal is located.

*** Done.  A log of this removal can be found at:
	/var/tmp/SharedVis.remove.2007.12.22

The log file is named with a date stamp. In this example, December 22, 2007.

---

Improving Sun Ray Image Quality at the Expense of Performance

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.

^{1 (TableFootnote) When NFS mounts onto a Microsoft WIndows client, qrsh will not work. A combination of locally installing on the Windows client and copying configuration from the qmaster host to the Windows client might enable qrsh to work on that client. Seek Sun Grid Engine support if this is necessary.}

^{2 (TableFootnote) The version number indicates a release of TurboVNC or VirtualGL softwarea, not of Sun Shared Visualization.}

Sun Shared Visualization 1.1 Software Server Administration Guide

820-3256-12

Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.