This section contains the information you need to plan your Sun Cluster HA for N1 Service Provisioning System installation and configuration.
This paragraph provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for N1 Service Provisioning System only.
For restrictions that apply to all data services, see the Sun Cluster Release Notes.
Sun Cluster HA for N1 Service Provisioning System can only be configured as a failover data service — Each component of N1 Grid Service Provisioning System can operate as a failover data service only. Therefore, all the components of the Sun Cluster HA for N1 Service Provisioning System can only be configured to run as failover data services.
Install the N1 Grid Service Provisioning System components on shared storage — The Master Server and the Local Distributor have to be installed on the shared storage. The remote agents which are configured to bind on the logical host have to be installed on the shared storage as well.
Configure a Sun Cluster resource for the N1 Grid Service Provisioning System Remote Agent for raw and ssl communication only —The Master Server will start and stop the Remote Agent on every connection, as long as the Remote agent is configured for ssh communication. In this case, there is no Sun Cluster resource needed. In the ssh scenario, you have to install the N1 Grid Service Provisioning System Remote Agent on the shared storage and copy the ssh keys from one node to the remaining nodes of the cluster. This assures that all the cluster nodes have the same ssh personality.
Your data service configuration might not be supported if you do not adhere to these restrictions.
These requirements apply to Sun Cluster HA for N1 Service Provisioning System only. You must meet these requirements before you proceed with your Sun Cluster HA for N1 Service Provisioning System installation and configuration.
Your data service configuration might not be supported if you do not adhere to these requirements.
Configure the N1 Grid Service Provisioning System base directory on shared storage on a failover file system – Create the N1 Grid Service Provisioning System base directory on the shared storage. The location for the base directory can reside on a Global File System (GFS) or it can reside on a Failover File System (FFS) with an HAStoragePlus resource. It is best practice to store it on a FFS.
The FFS is required because the Master Server uses the directory structure to store its configuration, logs, deployed applications, database and so on. The Remote agent and the Local Distributor store their caches below the base directory. It is not recommended to store the binaries on the local storage and the dynamic parts of the data on the shared storage.
It is best practice to mount Global File Systems with the /global prefix and to mount Failover File Systems with the /local prefix.
N1 Grid Service Provisioning System components and dependencies – You can configure the Sun Cluster HA for N1 Service Provisioning System data service to protect one or more N1 Grid Service Provisioning System instances or components. Each instance or component needs to be covered by one Sun Cluster HA for N1 Service Provisioning System resource. The dependencies between the Sun Cluster HA for N1 Service Provisioning System resource and other necessary resources are described in Table 1–5.
Table 1–5 Sun Cluster HA for N1 Service Provisioning System components and its dependencies for a failover configuration (via -> symbol)
Component |
Description |
---|---|
Storage Resource |
This resource can be a SUNW.HAStoragePlus or a SUNW.HAStorage resource type. |
N1 Grid Service Provisioning System component(Mandatory) |
-> SUNW.HAStoragePlus / SUNW.HAStorage resource The Storage resource manages the N1 Grid Service Provisioning System File System mount points and ensures that N1 Grid Service Provisioning System component resource is not started until necessary file systems are mounted. The N1 Grid Service Provisioning System component resource can be the Master Server, the Remote Agent, or the Local Distributor. |
Logical Host(Mandatory) |
The N1 Grid Service Provisioning System has an implicit dependency on the logical hosts of the resource group, because it is based on the generic data service. Therefore, a logical host is required, but no explicit dependency is necessary. |
For more detailed information about N1 Grid Service Provisioning System, refer to the product documentation on the docs.sun.com webpage or the documentation delivered with the product.
Each component of Sun Cluster HA for N1 Service Provisioning System has configuration and registration files in the directory /opt/SUNWscsps/component-dir/util — The term component-dir stands for the directory names master, localdist or remoteagent. These files let you register the N1 Grid Service Provisioning System component with Sun Cluster.
Within these files, you apply the appropriate dependencies.
# cd /opt/SUNWscsps/master # # ls -l util total 6 -rwxr-xr-x 1 root other 730 Nov 26 10:49 db_prep_postgres -rwxr-xr-x 1 root other 674 Nov 26 09:44 spsma_config -rwxr-xr-x 1 root other 579 Nov 26 11:06 spsma_register # more util/spsma_config # # Copyright 2003 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # This file will be sourced in by spsma_register and the parameters # listed below will be used. # # These parameters can be customized in (key=value) form # # RS - name of the resource for the application # RG - name of the resource group containing RS # PORT - name of the port number # LH - name of the LogicalHostname SC resource # PFILE - name of the parameter file for additional variables # HAS_RS - name of the HAStoragePlus SC resource # RS= RG= PORT=8080 LH= PFILE= HAS_RS= |
The spsma_register script validates the variables of the spsma_config script and registers the resource for the master server.
The master server component has an additional script db_prep_postgres. The purpose of this script is to prepare the PostgreSql database of the Master Server for monitoring.
# cd /opt/SUNWscsps/remoteagent # # ls -l util total 4 -rwxr-xr-x 1 root other 777 Dec 2 12:48 spsra_config -rwxr-xr-x 1 root other 568 Jan 7 16:56 spsra_register # more util/spsra_config # Copyright 2003 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # This file will be sourced in by xxx_register and the parameters # listed below will be used. # # These parameters can be customized in (key=value) form # # RS - name of the resource for the application # RG - name of the resource group containing RS # PORT - name of the Remote Agents port number # LH - name of the LogicalHostname SC resource # USER - name of the owner of the remote agent # BASE - name of the directry where the N1 Service Provisioning Server # is installed # HAS_RS - name of the HAStoragePlus SC resource # RS= RG= PORT=22 LH= USER= BASE= HAS_RS= |
The spsra_register script validates the variables of the spsra_config script and registers the resource for the remote agent.
# cd /opt/SUNWscsps/localdist # # ls -l util total 4 -rwxr-xr-x 1 root other 757 Dec 3 17:45 spsld_config -rwxr-xr-x 1 root other 609 Jan 7 16:56 spsld_register # more util/spsld_config # # Copyright 2003 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # This file will be sourced in by spsld_register and the parameters # listed below will be used. # # These parameters can be customized in (key=value) form # # RS - name of the resource for the application # RG - name of the resource group containing RS # PORT - name of the port number # LH - name of the LogicalHostname SC resource # USER - name of the owner of the local distributor # BASE - name of the directry where the N1 Service Provisioning Server # is installed # HAS_RS - name of the HAStoragePlus SC resource # RS= RG= PORT=22 LH= USER= BASE= HAS_RS= |
The spsld_register script validates the variables of the spsld_config script and registers the resource for the local distributor.