Typical deployment scenario for a Hedeby system
Before installing Hedeby please answer the following questions.
Which host will be used as master host?
On the master host Hedeby will install three processes (Java processes). The cs_vm with configuration service component. The rp_vm with the Resource Provider, Reporter and Spare Pool component and executor_vm with the executor and the CA component. cs_vm and rp_vm will run as sdm_admin user, executor_vm is started as user root.
The CA component of Hedeby use Grid Engine's sge_ca script for managing the certificate authority. As consequence the Hedeby master host needs access to a Grid Engine 6.2 SGE_ROOT directory.
Which Grid Engine instances will be managed by Hedeby?
For each Grid Engine instance which should be managed by Hedeby a GE Service Adapter component must be installed. This component can live in any JVM of the Hedeby. However the host where the JVM is running must have access to the SGE_ROOT directory of the Grid Engine instance. We recommend that the GE Service Adapter is installed on the Grid Engines Qmaster host.
Hedeby can only manage Grid Engine instances 6.2 or higher. Qmaster's JMX server must be enabled.
The Grid Engine service adapter will automatically discover the existing execution hosts of the Grid Engine instance. However it can only manage this hosts of a executor component is running on it. If you plan to manage the existing execution daemons with Hedeby you have to perform a managed host installation on this hosts.
Which hosts will be managed resources for the Hedeby system?
Typically a Hedeby system will have a pool of hosts which are not assigned to any service. For each of this hosts a managed host installation is necessary.
Which user account is the Hedeby admin user?
This user account must exist on any host of the Hedeby system. This will be the owner of the Hedeby distribution files. During the installation of Hedeby the security setup will create the necessary files for passwordless authentication of this user.
Where can Hedeby spool files?
Each host of a Hedeby system needs a local spool directory. The default path is
/var/spool/sdm/<Hedeby system name>. Hedeby has the following space requirements for the local spool directory:Type of Host Space Requirements Master host 200MB Managed host with GEServiceAdapter 50MB Managed Host (Host Resource) 20MB Which port can be used for the configuration server?
Hedeby needs one static port for the JVM which runs the configuration service (CS port).
Before the installation of the Hedeby system can begin please ensure Java 5 or Java 6 is installed on all of your hosts. The Java binary must be in PATH of the users which invokes Hedeby binaries. We do not recommend different Java versions on the different hosts Please perform on each host the following steps:
% java -version
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)
Once Java is available on each host please install the Hedeby binaries.
Currently the distribution is only available as tar.gz.
Please go to each host and install unpack the distrubtion. Please ensure
the you have chooses the same path on each host. We recommend /opt/sdm.
% rlogin foo
% cd /opt
% su
# mkdir sdm
# cd sdm
# tar xzf <dist_dir>/sdm-1.0.tar.gz
Please ensure that the owner of all files of the distrubtion is the Hedeby admin user (e.g. sdm_admin).
# chown -R sdm_admin /opt/sdm
Please update your shell configuration files. Ensure that the bin directory of the distribution is in the path of the Hedeby admin user.
The first step for a Hedeby system installation is the installation of the master host. This step is performed with the sdmadm install_master_host command. It must be started as user root. The following tasks are performed by this command.
Print out the software license and ask user to accept it.
Create the bootstrap configuration for the system. The bootstrap configuration for master host should be always installed with the system bootstrap configurations. (-p SYSTEM, see also Section 2.2.1, “Managing bootstrap configuration”)
Create the necessary files and directories in the local spool directory. Please note that the parent directory of the local spool dir must exist. The user executing the master host installation must have write permission on this directory.
Initialize the certificate authority.
This step will create the certification and credentials for the Ceritifcate Authority, for the Hedeby processes (cs_vm, rp_vm and executor_vm) and for the Hedeby admin user.
Create the basic configuration for the master host (setup of three JVMs, setup of configuration service component, CA component, Resource Provider component, Spare Pool component and Executor component).
The sdmadm install_master_host command has the following options:
Option | Description |
|---|---|
-l <local spool dir> |
Path of the local spool directory. This parameter is optional (default /var/spool/sdm/<system name>) |
-d <dist dir> |
Path of the distribution directory. This parameter is optional. The default value is derived from the path to the sdmadm command. |
-cs_port <port> |
Port where the config service should run |
-au <admin user> |
Name of the admin user |
-ca_country <country> |
Country name used for the certificate authority information (exact two letters) |
-ca_state <state> |
State name used for the certificate authority information |
-ca_location <location> |
Location token used for the certificate authority information |
-ca_org <organisation> |
Organization name used for the certificate authority information |
-ca_org_unit <org unit> |
Organization unit name used for the certificate authority information |
-ca_admin_mail <admin email address> |
Administrator mail address used for the certificate authority information |
-sge_root <sge_root> |
Hedeby uses the Grid Engine Certificate Authority utils. For the installation we need SGE_ROOT. |
-autostart |
This parameter is optional. It specifies whether the autostart feature should be installed on this host. For more information about autostart feature Section 2.2.6, “Autostart Feature in Hedeby” |
-al |
Automatically accept license. This parameter is optional. If the user uses this option, this means that he agrees with license. The license text will be just printed and installation will proceed. |
Example 2.1. Example for a Master Host Installation
The "sdmadm inst_master" command is used to install the Hedeby master host on the local host "foo". After successfull execution the Hedeby system "hedeby1" has the bootstrap information stored in the system preferences. The CA component is using the specified "-ca_..." options for creating the CA certificate. The "cs_port" value specifies a free port on the master host used for the configuration service. All components will contact this service to get their configuration.
foo# mkdir /var/spool/sdm
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 \
-d /opt/sdm \
-cs_port 31118 \
-l /var/spool/sdm/hedeby1 \
-sge_root /opt/sge62
After installing the command sdmadm startup_jvm starts all processes on the master host
foo# sdmadm -s hedeby1 startup_jvm
jvm host result message
---------------------------------
cs_vm foo STARTED
executor_vm foo STARTED
rp_vm foo STARTED
After the the master host is has been installed and started the managed host installation must be performed. Go to each managed host and execute the sdmadm install_managed_host command. The following steps will be executed:
Print out the software license and ask user to accept it.
Create the bootstrap configuration for the system. The bootstrap configuration for managed host should be always installed in the system preferences. (-p SYSTEM).
Create the necessary files and directories in the local spool directory. Please note the the parent directory of the local spool directory must exist. The user who performs the managed host installation must have write permissions into this directory.
Create security certificates and credentials.
This step will create the certification and credentials the executor JVM and for the Hedeby admin user.
For this step the sdmadm install_managed_host command will contact the CA component on the master host. The user has to provide some credentials for authentication. Per default this command will prompt the username and password of the Hedeby admin user. For passwordless authentication it is possible to use the keystore of the admin user. This path to the keystore can be specified with the global option
-keystore. The keystore of the admin user is created during the master host installation. It is stored in the local spool directory undersecurity/users/<admin username>.keystoreDuring the connection establishment the sdmadm inst_managed_host command will ask the user if the certificate of the is trusted. The question can be avoided if the certificate of the ca certificate is specified with the global
-cacertoption. The ca certificate is stored in the master hosts local spool directory undersecurity/ca/ca_top/cacert.pem.Create the basic configuration for the managed host (setup of the executor_vm and the executor component).
The following table shows all possible command options. Global command options are described in Section 2.3.1, “Global Cli Commands”.
Option | Description |
|---|---|
-l <local spool dir> |
Path of the local spool directory. This parameter is optional
(default is |
-d <dist dir> |
Path of the distribution directory. This parameter is optional. The default value is derived from the path to the sdmadm command. |
-au <admin user> |
Name of the admin user |
-cs_url <master host>:<cs_port> |
Name of the master host and cs port |
-autostart |
This parameter is optional. It specifies whether the autostart feature should be installed on this host. For more information about autostart feature Section 2.2.6, “Autostart Feature in Hedeby” |
Example 2.2. Example Managed Host Installation
The sdmadm install_managed_host command is used to make host foo2 to a managed host. After successfull execution the Hedeby system "hedeby1" has the bootstrap information stored in the system preferences. The command uses the keystore of the sdm_admin user for authentication against the configuration service.
foo1# mkdir /var/spool/sdm
foo1# sdmadm -s hedeby1 -p system \
-keystore /net/foo/export/home/sdm_admin/tmp/sdm_admin.keystore \
-cacert /net/foo/export/home/sdm_admin/tmp/ca_cert.pem \
inst_managed_host \
-au sdm_admin \
-d /opt/sdm \
-l /var/spool/sdm/hedeby1 \
-cs_url foo:31118
After installing the command sdmadm startup_jvm is used to startup the Executor component on the managed host.
foo1# sdmadm -p system -s hedeby1 startup_jvm
jvm host result message
---------------------------------
cs_vm foo1 STARTED
The master host installation adds automatically the first service to the Hedeby system. It's the Spare Pool. After all managed hosts are installed additional services can be added. For now it is only Spare Pools and Grid Engine Services are possible.
Grid Engine Services are added with the sdmadm add_ge_service command. A detailed description of this command can be found at Section 2.2.3.2, “Add a Grid Engine Service”
