Grid Engine Home > Service Domain Manager > SDM Installation Overview >

How to Install SDM

To install SDM, perform the following main tasks:

1. Gather information and verify system requirements.
   See Planning the SDM Installation and SDM Hardware and Software Requirements.
   
   
2. Confirm that Java 6 is installed on all hosts and that the Java binary is in the PATH of all users who need to run the SDM binaries.
   To confirm the Java version on a host, type the following command:

   % java -version
   java version "1.6.0_05"
   Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
   Java HotSpot(TM) Server VM (build 10.0-b19, mixed mode)
   

   
   

3. Download the SDM packages and place them in an appropriate place on all hosts.

   Note Make sure that all SDM installations use the same path, such as /opt/sdm. Do not unpack SDM into the Sun Grid Engine installation directory or mix the SDM installation with any installed software. The SDM software must be in an exclusive directory.

   Follow steps similar to this example:

   % rlogin foo
   % cd /opt
   % su
   # mkdir sdm
   # cd sdm
   # gzip -dc <dist_dir>/sdm-1_0-core.tar.gz | tar xvpf -
   

   
   

4. Set the owner of all SDM files to the SDM administration user, such as sdm_admin.

       
   # chown -R sdm_admin /opt/sdm        
   

   
   

5. Update configuration files to ensure that the SDM administration user's path includes the SDM bin directory.
   
   
6. Use the following command to install the necessary services and components on the master host:

   # sdmadm install_master_host
   

   For more information, see How to Install SDM on the Master Host.
   
   

7. Install additional components on one or more managed hosts as explained in How to Install SDM Components on a Managed Host.
   The managed hosts can perform several different roles:
   • Hosting a service
   • Acting as a host resource that can be assigned two different services
     
     
8. Confirm that JVMs are running on the master host and all managed hosts.
   Use the sdmadm show_jvm command as shown in this example:
   

   Regular installation # sdmadm show_jvm name host state -------------------------------- cs_vm master_host STARTED executor_vm foo1 STARTED master_host STARTED ... rp_vm master_host STARTED The following JVMs should be running: On the master host: cs_vm rp_vm and executor_vm On managed hosts: executor_vm On managed hosts that have a service adapter: rp_vm and executor_vm

   Simple installation # sdmadm show_jvm name host state -------------------------------- cs_vm master_host STARTED foo1 STARTED foo2 STARTED ... The following JVMs should be running: On the master host: cs_vm On managed hosts: cs_vm On managed hosts that have a service adapter: cs_vm

   
   

9. Confirm that all components are running on the master host and all managed hosts.
   Use the sdmadm show_component command as shown in this example:
   

   Regular installation # sdmadm show_component host jvm component type state --------------------------------------------------------------------- foo1 executor_vm executor Executor STARTED foo2 executor_vm executor Executor STARTED ... master_host executor_vm ca Other STARTED executor Executor STARTED master_host rp_vm reporter Other STARTED resource_provider ResourceProvider STARTED spare_pool Service STARTED The following components should exist: On the master host: In executor_vm: ca and executor In rp_vm: reporter, resource_provider, and spare_pool On managed hosts: executor On managed hosts that have a service adapter: executor service adapter - The service adapter component name is obtained from its configuration. For example, the cluster_name of the GE service which is stored in the file $SGE_ROOT/$SGE_CELL/common/cluster_name.

   Simple installation # sdmadm show_component host jvm component type state --------------------------------------------------------------------- foo1 cs_vm executor Executor STARTED foo2 cs_vm executor Executor STARTED ... master_host cs_vm executor Executor STARTED ca Other STARTED reporter Other STARTED resource_provider ResourceProvider STARTED spare_pool Service STARTED The following components should exist: On the master host: In cs_vm: ca, executor, reporter, resource_provider, and spare_pool On managed hosts: executor On managed hosts that have a service adapter: executor service adapter - The service adapter component name is obtained from its configuration. For example, the cluster_name of the GE service which is stored in the file $SGE_ROOT/$SGE_CELL/common/cluster_name.

   
   

10. After managed hosts have been installed, add any service adapters.
    The master host installation adds automatically the first service, the spare pool, to the SDM system. After all managed hosts are installed, you can add additional services, such as Grid Engine services. For more information, see How to Add the Grid Engine Service.