HP XC System Software Administration Guide Version 3.1

• sa_locality
Assigns clients to servers that have similar traffic patterns to limit the amount of network traffic.
• sa_default_assignment
Assigns the default assignment. The default assignment is the assignment policy HP decided is
the most useful for most of the services.
NOTE: If necessary, you can combine patterns using a pipe character (|). For example, the
following schedules clients to servers in blocks so that no server has itself as a client:
sa_block|sa_do_not_assign_to_self
4
This instruction converts the server list @servers to a set of servers; a transformation of the list to a
set for later use. Sets of nodes can be selected by their names or by node attributes (such as na_all
and na_compute).
5
This instruction returns the set of all client nodes of the service (across the entire system). Only the
client selection flags are required; the client and server assignment flags are not required.
6
This instruction assigns the clients across the server set and enters the server and client assignments
into the database. This API requires the client and server assignment and scheduling flags.
The API calls are intended to make typical cases as easy and uniform as possible; the API calls are not
intended to cover every possible scenario. Occasionally, you might have to resort to more basic Set::Node
(Set::Scalar) operations to get the set you want (such as all nodes except the head node).
Nothing precludes a gconfig script from creating its client list in a proprietary way when it is necessary
and appropriate to do so.
The API calls include the processing of the node attribute disable flags, such as:
• na_disable_server.service
• na_disable_client.service
Nodes with na_disable_server.service assigned for a service are excluded from the server list
passed into the gconfig script as servers. Nodes with na_disable_client.service assigned for a
service are not returned as potential clients of that service. In general, these flags are something the gconfig
script does not need to handle explicitly.
Nothing precludes each gconfig script from offering optimal choices to you through its user interface.
The APIs provided for server and client selection and mappings make no assertions regarding the
interrelationship of the servers that are configured.
4.6.5.3 The nconfigure Scripts
An nconfigure script in the /opt/hptc/etc/nconfig.d directory modifies individual server nodes
and sets up any server-specific configuration required for a particular service. An nconfigure script is
executed only on nodes that are servers of the service.
An nconfigure script is executed inside the cluster_config utility as follows:
script_path nconfigure server
script_path nunconfigure server
The server is the node name on which the script is running. The nconfigure action is performed only
on nodes that are servers of the service. The nconfigure scripts cannot have a user interface.
The nconfigure scripts return 0 (zero) on success and return a nonzero value on failure. Any failure
causes the node to be put into single-user mode so that the error can be investigated.
The nunconfigure action is not performed automatically, but it should be available to be performed
manually.
4.6.5.4 The cconfigure Scripts
A cconfigure script in the /opt/hptc/etc/cconfig.d directory sets up client-specific configuration
required for a particular service.
66 Managing and Customizing System Services