Using Easy Deployment in Serviceguard and Metrocluster environments on HP-UX 11i v3

31
The following workflow diagram in Figure 20 illustrates the details of the Site Controller Easy
Deployment process:
Figure 20: Workflow diagram for Site Controller Easy Deployment
Parameter discovery and default parameters
By way of automatic package parameter discovery by the Site Controller Easy Deployment script,
most of the package attributes are automatically populated in the Site Controller and managed
packages’ configuration files. The rest are set to recommended default values. The following table
explains more about how each Site Controller package parameter is generated:
Parameter What it means Value
How is it
generated?
failover_policy Indicates the preference for
package failover
site_preferred(default)
Other possible value: site_preferred_manual
(The user needs to manually edit the
generated configuration file in this case)
Recommended
package_name Name of the Site Controller
package
Auto-created but
editable by user
critical_package Indicates the name of a
package upon whose failure
the entire complex workload
set is halted by Site Controller
Any package name that is already configured
in the cluster
User input