HP XC System Software Administration Guide Version 3.2

3
The $assignment_flags are used to determine the pattern of the client-to-server
assignments. The default is a server may be assigned to itself as a client.
The following service attributes control a client's assignment to itself as a server and are
valid for client and server assignments:
sa_do_not_assign_to_self
sa_must_assign_to_self
sa_may_assign_to_self
This is the default, which is the same as the double quote character ().
The following service attributes are valid for client and server assignment patterns:
sa_block
Assigns equal (as equal as practical) contiguous blocks of client nodes to each server
subject to the additional assign to self specification.
sa_block_cyclic.N - (for example, sa_block_cyclic.8)
Assigns a contiguous block of N client nodes to each server in round-robin style, subject
to the additional assign to self specification.
sa_cyclic
Is the same as sa_block_cyclic with N = 1, assigning round-robin one client at a
time, subject to the additional assign to self specification.
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
70 Managing and Customizing System Services