Grid Engine Home > Service Domain Manager > SDM Installation Overview >
Planning the SDM Installation
Before you install the SDM module on a master host and on managed hosts, you should gather some information and make some decisions.
Decisions That You Must Make
Before installing SDM, consider the following questions:
Which host will be used as the master host?
The SDM master host runs the central components for the SDM system.
What type of installation to choose (regular or simple)?
In regular installation, SDM runs three Java processes on the master host:
- The cs_vm process includes the configuration service component. This process runs under the sdm_admin user.
- The rp_vm process includes the resource provider, reporter, and spare pool components. This process runs under the sdm_admin user.
- The executor_vm process includes the executor and the certificate authority (CA) component. This process runs under the root user.
In simple installation, SDM runs one Java process on master host:
- The cs_vm process includes the configuration service, resource provider, reporter, spare pool, executor and the certificate authority (CA) component. This process runs under root user.
The CA component uses the Sun Grid Engine sge_ca script for managing the certificate authority. As a result, the SDM master host must have access to a Grid Engine 6.2 $SGE_ROOT directory.
Which Grid Engine instances will SDM manage?
SDM can manage Sun Grid Engine instances starting with Version 6.2.
For each Grid Engine instance that SDM will manage, you must install a Grid Engine service adapter component. This component can live in any JVM of the SDM system. However, the host on which the JVM is running must have access to the $SGE_ROOT directory of the Grid Engine instance. You should install the Grid Engine service adapter on the Grid Engine master host on which JMX is enabled.
The Grid Engine service adapter automatically discovers any existing Grid Engine execution hosts. However, SDM can manage only those hosts on which the SDM executor component is running. To manage existing execution daemons with SDM, you must install managed host functionality on these hosts.
Which hosts will be managed resources for the SDM system?
Typically, an SDM system has a pool of hosts that are not assigned to any service. You must install the managed host functionality on each of these hosts.
Which user account is the SDM admin user?
The SDM admin user account must exist on all hosts of the SDM system. The SDM admin user owns the SDM distribution files and can run all sdmadm commands. During the SDM installation, the security setup will create the necessary files for passwordless authentication of this user.
From SGE 6.2u3, the root user is automatically added as the SDM administrative user when you install an SDM system with system preferences. When you install an SDM system with user preferences, the operation of adding root user as the SDM administrative user is not performed.
| Note The UNIX root user cannot run sdmadm commands unless the root user has been added as an SDM administrative user. For information on adding administrative users, see Adding an Administrative User. |
Where can SDM spool files?
Each host of an SDM system needs to have a local spool directory. The default path is /var/spool/sdm/SDM-system-name. SDM has the following space requirements for the local spool directory:
| Type of Host | Space Requirements |
|---|---|
| Master host | 200 MBytes |
| Managed host with GEServiceAdapter | 50 MBytes |
| Managed host (host resource) | 20 MBytes |
| Warning The SDM system will store the private credentials for password less authentication in the local spool directory. If the local spool directory is located on a shared file system (NFS, CIFS) there is a risk that unauthorized users get access to the private credentials. For security reasons a host local file system for the local spool directory. |
Which port can be used for the configuration server?
SDM needs one static port for the JVM that runs the configuration service (CS port).
What name will you use for the SDM system instance?
The SDM system name uniquely identifies the specific SDM instance on the master host. The SDM system name is a string that may include the following characters:
- Uppercase or lowercase alphabetic characters (a-z, A-Z)
- Digits (0-9)
Gather the Necessary Information
Gather the following information before you start the installation. By writing down these values, you more easily achieve the results that fit your environment.
| Parameter | Explanation | Example | Your Value |
|---|---|---|---|
| sdmadm-path | Path to the location of the SDM administration tool | /opt/sdm/bin/sdmadm | |
| dist-path | Path of the distribution directory | /opt/sdm | |
| dist-bin_path | Path to the distribution directory binaries | /opt/sdm/bin | |
| spool-dir | Path of the local spool directory | /var/spool/sdm/SDMproductive | |
| cs-port | Port where the config service should run | 31016 | |
| system-name | Name for the SDM system instance | SDMproductive | |
| sge-root directory | Path to the Grid Engine $SGE_ROOT directory | /opt/sge | |
| ca-admin-mail | Administrator mail address used for the CA information | first.last@sun.com | |
| ca-location | Location token used for the CA information | Regensburg | |
| ca-country | Country name used for the CA information | DE | |
| ca-org | Organization name used for the CA information | Sun Microsystems | |
| ca-org-unit | Organization unit name used for the CA information | Development | |
| ca-state | State name used for the CA information | Germany | |
| master-host | Host name for the SDM master host | master_host | |
| ssl disabled | Turns off SSL encryption for the master host | false | |
| simple_install | Turns on simplified installation with one jvm | false |
|
Participate
|
Learn More
|

