sdmadm Manual

Add a new system bootstrap configuration

This command adds the entries for a hedeby system bootstrap configuration into the user or system preferences. This command requires the global -s and -p options.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Add a new complex mapping for Grid Engine services

Grid Engine services needs a mapping for building the resource properties of autodiscovered exec daemons. With this command a new mapping for complex values can be added.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Modify the Component configuration

This command opens the Component configurationin an editor.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Modify a complex mapping for Grid Engine services

Grid Engine services needs a mapping for building the resource properties of autodiscovered exec daemons. With this command a existing mapping for complex values can be modified.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Modify the global configuration

This command opens the global configurationin an editor.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Modify the logging Level of Jvm loggers

This command can change log level for loggers on the Jvms. With -l option you can specify loggers to change. For example format for this field it can look like this ALL:com.sun.grid=INFO. With -ca option you can set up logging level for all loggers in the system both global and subloggers. REPORTER logger is the the only exception. For setting up loggig level for Reporter component use -l switch. Example for this switch: -ca ALL. To set logging level for all the jvms on specific host you have to use sll -h hostname -all, to set all logging levels for all jvms with the same name on all hosts use sll -j jvm_name -all, to set logging level for a specific jvm use sll -j jvm_name -h foo, to set logging level for all jvms on all hosts use sll -all.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Remove installed system bootstrap configuration

This command removes a system bootstrap configuration from the java preferences of a system or a user. This command requiresthe global option -system.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Remove a complex mapping for Grid Engine services

Grid Engine services needs a mapping for building the resource properties of autodiscovered exec daemons. With this command a existing mapping for complex values can be removed.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Set property of bootstrap configuration

Supported properties are "auto_start" and "no_ssl".

If "auto_start" is set to "true", the system will be start at boot time.

If "no_ssl" is set to "true" ssl encryption and authentication of incoming request is disabled. Disabling security should only be done for test systems, hence every user with execute permissions on sdmadm can modify the system.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Set default bootstrap configuration

If a default bootstrap system configuration is set, the sdmadm command can be used without the -system options. All actions will be executed on the default system.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show the logging Level of Jvm loggers

This command can display active loggers and log levels of JVMs.

The -n option filters the name of the logger. If it is used all loggers where the name starts with the specified loggers_name will be printed out.

With the -all option the sll command can read the log level of the loggers of all JVMS. In combination with the -h option displays only the loggers of all JVMs of the specified host. The output can also be filtered with the -j option.

Examples:

Display all loggers of the host foo:

% sdmadm sll -all -h foo

Display all loggers of all running jvms of the system:

n% sdmadm ssl -all

Display all loggers of the JVM rp_vm running on host foo.bar where the name of the logger starts with com.sun.grid.grm:% sdmadm ssl -n "com.sun.grid.grm" -h foo.bar -j rp_vm

Show the loggers on all JVMs on hosts of the system that meet the following criteria:

- The log level is set to INFO

- The name of the logger starts with com.sun.grid

% sdmadm sll -l INFO -n com.sun.grid -all

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Unset the default bootstrap configuration

After unsetting the default system bootstrap configuration sdmadm needs the -system option to find a system. This command does not delete the system which is marked as default system. Use remove_system command to delete a system bootstrap configuration

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Shutdown component on a host

Stop components of the system

The -c option specifies the target component. With the -h option the target hostcan be specified. The -all option is required unless both -c and -h option are specified.

Examples:

Stop all components of the system:

% sdmadm sdc -all

Stop all components on host foo:

% sdmadm sdc -h foo -all

Stop all components with name executor:

% sdmadm sdc -c executor -all

Stop the executor component on host foo:

% sdmadm sdc -c executor -h foo

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Shutdown JVMs

The command stops JVMs of the system.

The -j option allows filtering of the jvms. With the -h option the targeted hostcan be specified. The -all option is required unless both -j and -h option are specified.

Examples:

Stop all JVMs of the system:

% sdmadm sdj -all

Stop all JVMs on host foo:

% sdmadm sdj -h foo -all

Stop all JVMs with name executor_vm:

% sdmadm sdj -j executor_vm -all

Stop the executor JVM on host foo:

% sdmadm sdj -j executor_vm -h foo

Security:

If the executing user has not the ADMINISTRATOR privilege but the SUPER_USER privilege and all target jvms are on the local host this commands reads the pid files from the local spool directory and kills corresponding processes.

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Start hedeby component on a host

The command will start the specified component on a specified host.

If only the "component" is not specified, the command will start all components that are configured for the specified host.

If only the "host" is not specified, the command will start the specified component on all hosts where it should be running.

If both the "component" and the "host" are not specified, the command will start all components on all hosts where they should be running.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Start a JVM on a localhost

The command will start the specified JVM on a local host.

If -j option is not specified, the command will start all JVMs that are configured for the localhost.

By specifying the -d parameter the targeted JVM starts in debug mode. A Java Platform Debugger Architecture (JPDA) compatible debugger can connect to the jvm on the specified port. The jvm will be suspened until the debugger has been connected. For more information about JPDA please have a look at http://java.sun.com/j2se/1.5.0/docs/guide/jpda.

Please note that the -d opton can only be used for a single jvm (-j parameters is in this case mandatory).

Examples:

- start all JVMs on the localhost:

% sdmadm -s <system_name> suj

- force the startup all JVMs on the local host (even if the pid files exists):

% sdmadm -s <system_name> suj -f

- start the jvm with name JVM1 on the local host:

% sdmadm -s <system_name> suj -j JVM1

- starts JVM1 on the localhost in debug mode. The JDPA debugger can

contact this jvm at port 33445:

% sdmadm -s <system_name> suj -j JVM1 -dp 33445

Security:

If the executing user has the SUPER_USER privilege this command will start the jvm under the user account specified in the definition of the jvm in the global configuration. Otherwise the target jvms will be started under the user account of the executing user.

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Update component configuration by reloading

The command will reload the specified component configuration on a specified host.

If only the "component" is not specified, the command will reload configuration of all components that are configured for the specified host.

If only the "host" is not specified, the command will reload configuration of the specified component on all hosts where it should be running.

If both the "component" and the "host" are not specified, the command will reload configuration of all components on all hosts where they should be running.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Performs the necessary step to install a managed host.

This command is used to install the managed host components on the local host. The manage host installation includes the following steps:

- create the local spool directory

- create the bootstrap configuration

- create the default configuration for a managed host

- initialize the security infrastructure (keystores and ca certificate)

Security:

For the security bootstraping the installing user must have the necessary credentials for the authentication as administrative user (ADMINISTRATOR privilege).

If the -p parameter is set to SYSTEM the executing user must have the SUPER_USER privilege. The ownership of the keystores will be set to the corresponding users. If the -p parameter is set to USER the SUPER_USER privileges is not necessary. Owner of all keystores will be the executing user.

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Install hedeby master host

This command is used to install the master host components on the local host. This include the following steps:

- create the boostrap configuration

- create the local spool directory

- create the default configuration

- initialize the Certificate Authority

- create the certificate, private keys and keystore for

all jvms and for the admin user

Security:

If the -p parameter is set to SYSTEM the executing user must have the SUPER_USER privilege. In this case the boostrap 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 bootstap 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 privilege, hence the WRITE_KEYSTORE privilege is not necessary for this command.

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Uninstall the system from the local host

If the local host is the master host, the uninstallation will cause that system will not be available anymore. If current host is managed host and it does not have running jvms, the uninstallation will remove from configuration all componentsthat are running on this host. Preferences and localspool directory will be cleaned up.To remove host even when CS can not be contacted use option -force.

Security:

If the system has been installed with SUPER_USER privilege the uninstall_host command requires also the SUPER_USER privilege. Otherwise the executing user will not have the permissions to delete all files from the local spool directory.

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show resource ids of resources that are ignored by a service

This command allows to monitor resource ids that are ignored by a service(s). It can be specified whether the list of such resource ids is shown for a specified service or for each service service. If blacklist for specified service only should be shown, use -s option and specify service name.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show all installed bootstrap configurations

The command will show the bootstrap configurations of the systems that are defined. The command is looking for bootstrap configurations defined in system and/or user preferences depending on the -prefs switch.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show status of all system components

The command will show status of all system components.

The output is grouped by system, host and jvm.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show complex mapping for Grid Engine services

This command prints out the available complex mapping for Grid Engine services

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show the data stored by reporter component.

Use the {{sdmadm show_history}} command to see the information that the reporter stores. If you do not specify any parameters, this command displays all messages that the reporter has. You can limit the information that is displayed in several ways:

- Specify the exact resource or service name for which you want information

- Specify an event type for which you want information

- Combine a resource name, service name, and event type

- Define a filter using the {{-f}} switch

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show running Jvms in Hedeby System.

Show runninng Jvms in system, even those which do not have running components

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show all available modules in the system

SDM can be extended by adding additional modules. This command prints out the installed modules, with vendor and version.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show resource(s) state(s) in the system.

This command allows to monitor resource(s) state(s) in the system. You can specify the exact resource name that you want to check the status. By specifying service name you will see all resource states for the given service. Additionally you can define a resource filter expression with the -rf switch. If you don't specify anything all resources in the system will be printed. If you want to see full description of resource like type, annotation and its properties use -f option. If you want to see information about the cached resources, use -c option. If you want only a list of resource ids use -o res_ids.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show registered resource requests at resource provider

This command displays the resource requests produced by the SLOs of the services by sending a resource request to the resource provider.

Queued requests are waiting to be processed. Pending requests have already been processed, however the resource provider could not find enough appropriate resources to fully satisfy the need. If the -all option is specified the table will print also the quantity and the request filter of the resource request.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show all known resource types

Shows all known resource types and its predefined resource property type in a table.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show services managed by system

The command will show services managed by system.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show SLOs

The command print information about SLOs of services.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Show all installed smf services for this system. If no services installed, command will print message if SMF is not supported on host.

Command will print message if SMF is not supported on host.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Add a new resource of a specified type to Hedeby system

This command allows user to add a new resource to an existing Hedeby system.

If the -f parameter is specified the complete definintion of the resource is read from the rpFile. It is a regular property file (<name=value>) that describes the characteristics of a resource.

Without -f parameter the resource is constructed out of the resource type definition. If a resource id if specified (-r parameter) all resource properties which can be derivedfrom the resource id are automatically set (e.g for a host resource type the resourceHostnameproperty is set). If there are missing mandatory paramater the resource definition is openedin an editor.

It is not allowed to use -f parameter together with the -r parameter.

The other optional parameter is a type of a resource which is by default set to ''host'' (means host resource). Service name parameter specifies the service that we want to assign resource to. This paramater is optional - if it is not set a resource provider will try to find target service for resource. If there is no service willing to consume the resource, resource is refused. ID of a resource is an optional parameter as well because resource ID can be generated from resource properties file.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Add resource(s) to service's blacklist.

This command allows to add resource or resources (their ids) to a service's resource blacklist. It is possible to specify just one or more resources at once. Specifying at least one is necessary. The service name is mandatory.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Modify an existing resource

This command allows user to modify an existing resource. The two required parameters are a file name of resource.properties file and a resource id. The resource.properties file is a regular property file (<name=value>) that specifies the properties of a resource that has to be changed.

Security:

A detailed description of the privileges can be found in the section called “SECURITY PRIVILEGES”.

Move resource(s) to a service.

This command allows to move resources to a specific service. A list of resource id is needed as well as target service name is required. There is no guarantee that the resources will be moved from one service to another.