Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux

Technical white paper | Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux
SG/LX also enables you to define the capacities for a node and corresponding weight for a package. The capacity of a node
determines how much weight of packages it can accommodate. For example, you can define a capacity called memory,
which has value 1000 for a node. This means that node can accommodate a package or multiple packages having weight
less than or equal to 1000. If you have defined package A with weight 1000, package B with weight 500, and package C with
weight 500, then that node can either accommodate only package A, or both package B and package C. In SG/LX, you can
use following parameters to define capacity of nodes and weight of packages. You can define multiple capacities and
weights if required.
capacity_name: It provides the name of the capacity. This is a node attribute.
capacity_value: It provides the value of the capacity. This is a node attribute.
weight_name: It provides the name of the weight. It should be the same as one of the capacity names. This is a
package attribute.
weight_value: It provides the value of the weight. This attribute is associated with the package. The value of weight gets
subtracted from the nodes capacity value where it is running.
SG/LX uses first fit policy when capacities and weights are configured. Based on the failover policy of a package, SG/LX
creates a list of adoptive nodes for failing over that package. If capacities and weight are configured, SG/LX chooses the first
adoptive node which can accommodate the package weight for failover.
Table 4. VCS service group attributes and SG/LX package attributes
VCS service group
attributes, which can be
editable by users
Corresponding SG/LX package attributes
(equivalent to some extent) present in
package ASCII file, which can be editable
by users
Descriptions
1 AdministratorGroups,
Administrators
user_name, user_host, and user_role In VCS, the “AdministratorGroups” and “Administratorsattributes
are used to provide administrative privileges on the service group
to list of OS user account groups and users.
Serviceguard provides access control policy parameters to provide
Administrator access to multiple OS users. Administrator access
to multiple users is provided by listing multiple users with
“FULL_ADMIN” as USER_ROLE.
2 AutoFailOver auto_run In VCS, the “AutoFailOver” attribute indicates whether VCS initiates
an automatic failover if the service group faults.
In Serviceguard, the “auto_run” attribute is enabled to initiate an
automatic failover of a package if that package fails.
3 AutoRestart service_restart In VCS, the “AutoRestart” attribute is used to restart a service
group after a faulted persistent resource becomes online.
In Serviceguard, the “service_restart” attribute is used to
determine whether a service of package can be restarted or not.
4 AutoStart auto_run In VCS, the “AutoStart” attribute designates whether a service
group is automatically started when VCS is started.
In Serviceguard, the “auto_run” attribute determines whether a
service_group is automatically started when VCS is started or not.
5 AutoStartList node_name In VCS, the “AutoStartList” attribute is used to specify the list of
systems on which, under specific conditions, the service group can
be started with VCS (usually at system boot).
In Serviceguard, the “node_name” attribute is used to specify the
order of nodes in which package can start.
13