View Source

[Grid Engine Home|Home] > [Service Domain Manager] > [SDM Installation Overview] >
\\
{excerpt}
h1. !sdm.png! How to Install SDM

To install SDM, perform the following main tasks:

# *Gather information and verify system requirements.*
See [Planning the SDM Installation] and [SDM Hardware and Software Requirements].
\\
\\
# *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:
{code:none}
% 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)
{code}
\\
# *Download the SDM packages and place them in an appropriate place on all hosts.*
{info:title=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. {info}
Follow steps similar to this example:
{code:none}
% rlogin foo
% cd /opt
% su
# mkdir sdm
# cd sdm
# gzip -dc <dist_dir>/sdm-1_0-core.tar.gz | tar xvpf -
{code}
\\
# *Set the owner of all SDM files to the SDM administration user, such as {{sdm_admin}}.*
{code}
# chown -R sdm_admin /opt/sdm
{code}
\\
# *Update configuration files to ensure that the SDM administration user's path includes the SDM {{bin}} directory.*
\\
\\
# *Use the following command to install the necessary services and components on the master host:*
{code}
# sdmadm install_master_host
{code}
For more information, see [How to Install SDM on the Master Host].
\\
\\
# *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
\\
\\
# *Confirm that JVMs are running on the master host and all managed hosts.*
Use the sdmadm show_jvm command as shown in this example:
\\
{section}
{column:width=40%}
{panel:title=Regular installation}
{code}
# sdmadm show_jvm
name host state
--------------------------------
cs_vm master_host STARTED
executor_vm foo1 STARTED
master_host STARTED
...
rp_vm master_host STARTED
{code}
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}}
{panel}
{column}
{column:width=40%}
{panel:title=Simple installation}
{code}
# sdmadm show_jvm
name host state
--------------------------------
cs_vm master_host STARTED
foo1 STARTED
foo2 STARTED
...

{code}
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}}
{panel}
{column}
{section}
\\
# *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:
\\
{section}
{column:width=40%}
{panel:title=Regular installation}
{code}
# 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
{code}
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}}.
{panel}
{column}
{column:width=40%}
{panel:title=Simple installation}
{code}
# 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

{code}
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}}.
{panel}
{column}
{section}
\\
# *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|Using SDM With the Sun Grid Engine Adapter#How to Add the Grid Engine Service].
{excerpt}

{section}
{column:width=50%}
{panel:borderStyle=solid|borderColor=#5382a1|titleBGColor=#5382a1|bgColor=#ffffff}
*Participate*
Have a best practice to share? Questions? Suggestions? Comments?
* [Add a page] to the Expert Advice section
* [Ask the community] a question
* Send the writing team an [email|mailto:gridengine-writers@sun.com]
* Leave a comment below
{panel}
{column}

{column:width=50%}
{panel:borderStyle=solid|borderColor=#5382a1|titleBGColor=#5382a1|bgColor=#ffffff}
*Learn More*
For more on this topic, check out the following resources:
* Expert Advice -- [Video: Introduction to Grid Engine|http://www.youtube.com/watch?v=0JBsMitNnQ8]
* Expert Advice -- [White Paper: Beginner's Guide to Sun Grid Engine|http://www.sun.com/offers/details/Sun_Grid_Engine_62_install_and_config.html]
(If you are not already registered with sun.com, you must fill out a
quick registration form to gain access to this white paper.)
* Expert Advice -- [Podcast: Towards Cloud Computing with Sun Grid Engine 6.2|http://blogs.sun.com/HPC/entry/podcast_towards_cloud_computing_with]
{panel}
{column}
{section}

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