How to Install SDM on the Master Host

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

How to Install the SDM Module on the Master Host

When you install SDM on the master host, the sdmadm install_master_host command does the following:

Regular installation
  • Creates the bootstrap configuration for the system. The bootstrap configuration for the master host must be installed in the system preferences (-p system).
  • Creates the necessary files and directories in the local spool directory.
  • Initializes the Certificate Authority (CA) and creates the security certification and credentials for the CA.
  • Creates the certification and credentials for the SDM processes (cs_vm, rp_vm, and executor_vm) and for the SDM admin user.
  • Creates the basic configuration for the master host:
    • Setup of cs_vm, rp_vm and executor_vm JVMs
    • Setup of configuration service component, CA component, resource provider component, reporter component, spare pool component, and executor component
Simple installation
  • Creates the bootstrap configuration for the system. The bootstrap configuration for the master host must be installed in the system preferences (-p system).
  • Creates the necessary files and directories in the local spool directory.
  • Initializes the Certificate Authority (CA) and creates the security certification and credentials for the CA.
  • Creates the certification and credentials for the SDM process (cs_vm) and for the SDM admin user.
  • Creates the basic configuration for the master host:
    • Setup of cs_vm JVM
    • Setup of configuration service component, CA component, resource provider component, reporter component, spare pool component, and executor component

Before You Begin

Steps

  1. Log in as the root user on the master host.
  2. Install the SDM primary components on the master host.
    Use the following command with the information that you wrote down on your planning sheet:
    # sdmadm -s <system-name> -p system install_master_host -ca_admin_mail <mail-address> \
    -ca_state <state> -ca_country <country> -ca_location <location> -ca_org_unit <unit> \
    -ca_org <org> -au <admin-user-name> -cs_port <port-number> -l <path-to-spool-dir> \
    -sge_root <path-to-$SGE_ROOT>
    
    Note
    • The sdmadm command resides in the sdm-install-dir/bin directory on the host.
    • For information about sdmadm install_master_host command options, see Install Master Host Command Options.
  3. Start all processes on the master host.
    Use the following command with the same system-name as in the previous step:
    # sdmadm -system <system-name> startup_jvm 
    
  4. When all processes are successfully started on the master host, install SDM components on all managed hosts.
    See How to Install SDM Components on a Managed Host.

Example – Installing SDM Master Host and Starting All Processes

The first command in the following example:

  • Installs the SDM master host on the local host foo.
  • Uses the specified -ca options to create the security (CA) certificate.
  • Specifies a free port on the master server to use for the configuration service in the cs_port value. All components will contact this service to get their configuration.
Regular installation
foo# sdmadm -s hedeby1 -p system              \
          install_master_host                 \
          -ca_admin_mail "userFoo@foo.com"    \
          -ca_state "fooLand"                 \
          -ca_country "FO"                    \
          -ca_location "fooLocation"          \
          -ca_org_unit "fooUnit"              \
          -ca_org "fooOrg"                    \ 
          -au sdm_admin                       \
          -cs_port 31118                      \
          -l /var/spool/sdm/hedeby1           \
          -sge_root /opt/sge62
Simple installation
foo# sdmadm -s hedeby1 -p system              \
          install_master_host                 \
          -ca_admin_mail "userFoo@foo.com"    \
          -ca_state "fooLand"                 \
          -ca_country "FO"                    \
          -ca_location "fooLocation"          \
          -ca_org_unit "fooUnit"              \
          -ca_org "fooOrg"                    \ 
          -au sdm_admin                       \
          -cs_port 31118                      \
          -l /var/spool/sdm/hedeby1           \
          -sge_root /opt/sge62                \
          -simple_install

After the first command completes successfully, the bootstrap information for the SDM system hedeby1 is stored in the system preferences.

To verify that installation was complete, the next command shows the bootstrap configuration.

foo# sdmadm sbc
system   type   host     port  properties version 
--------------------------------------------------
hedeby1  SYSTEM foo      31118            1.0u3

The last command starts the configuration service, executor, and resource provider processes on the system hedeby1.

Regular installation
foo# sdmadm -s hedeby1 startup_jvm
jvm         host  result  message
---------------------------------
cs_vm       foo   STARTED 
executor_vm foo   STARTED  
rp_vm       foo   STARTED 
Simple installation
foo# sdmadm -s hedeby1 startup_jvm
jvm         host  result  message
---------------------------------
cs_vm       foo   STARTED 

Install Master Host Command Options

Use the sdmadm install_master_host command to install the SDM functionality onto the master host.

Synopsis
sdmadm  install_master_host|imsth [-autostart] [-nossl] -au <admin-user> -ca_admin_mail <mail-address> 
-ca_country <country> -ca_location <location> -ca_org <organization> -ca_org_unit <unit> 
-ca_state <state> -cs_port <port-number> [-l <path-to-local-spool-dir>] 
-sge_root <path-to-sge-root-dir> [-d <dist-dir>] [-al] [-simple_install]
Option Required or Optional Description
-al Optional Automatically accept the license. If used, the installation displays the license text and assumes that the user accepts it. No additional user response is required.
-au admin-user Required User name of the admin user. For example, sdm_admin.
-autostart Optional Specifies that SDM be restarted upon system boot. Applies only on systems with system preferences. If SMF is supported on the host, autostart uses SMF services; otherwise, autostart uses a startup script.
-ca_admin_mail mail-address Required Administrator mail address used for the security certificate.
-ca_country country Required Two-letter country designation used for creating the security certificate. For example, US or DE.
-ca_location location Required Location token used for creating the security certificate.
-ca_org organization Required Organization name used for creating the security certificate.
-ca_org_unit unit Required Organization unit name used for creating the security certificate.
-ca_state state Required State name used for creating the security certificate.
-cs_port port-number Required Port where the configuration service should run. There is no default.
-d path-to-dist-dir Optional Path of the distribution directory. The default value is derived from the path to the sdmadm command.
-l path-to-local-spool-dir Required Complete path to the local spool directory. Default: /var/spool/sdm/<system-name>
-nossl Optional Turns off SSL encryption for the master host
-sge_root path-to-sge-root-dir Required SDM uses the Grid Engine CA utilities for security. These utilities must know the location of the installed Grid Engine product as defined in $SGE_ROOT.
-simple_install Optional Install system with simplified configuration
Security
  • Optional Privileges
    • SUPER_USER
      If the -p parameter is set to SYSTEM the executing user must have the SUPER_USER privilege. In this case the bootstrap configuration is stored in /etc/sdm/bootstrap. The owner of the jvm keystore will be the user running the jvm (according to the global config) and the owner of admin keystore will be the admin user.
      If the -p parameter is set to USER the SUPER_USER privilege is not necessary.The bootstrap configuration is stored in $HOME/.sdm/bootstrap and the owner of all keystores is the executing user.
      The SUPER_USER privilege includes the WRITE_KEYSTORE WRITE_KEYSTORE privilege, hence the WRITE_KEYSTORE privilege is not necessary for this command.

Also see Global Options for the sdmadm Command.

Participate
Have a best practice to share? Questions? Suggestions? Comments?

Learn More
For more on this topic, check out the following resources:

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact