186 lines
8.3 KiB
HTML
186 lines
8.3 KiB
HTML
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
|
||
|
|
<title>Family Resource Group APIs</title>
|
||
|
|
<!-- Begin Header Records ========================================== -->
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<!-- 031106 JETAYLOR replaced API and/or Exit listings with -->
|
||
|
|
<!-- pagegenerator output from javascript array -->
|
||
|
|
<!-- End Header Records -->
|
||
|
|
<!-- -->
|
||
|
|
<!-- -->
|
||
|
|
<!-- -->
|
||
|
|
<!-- Begin Developer Note ========================================== -->
|
||
|
|
<!-- NOTE: If you are adding, changing, or removing ANY requirements -->
|
||
|
|
<!-- for this API chance are good that the GUI code need to change -->
|
||
|
|
<!-- also. The Cluster GUI code is built on top of this API and it -->
|
||
|
|
<!-- does a certain amount of explicit and implicit validation -->
|
||
|
|
<!-- checking of user data prior to the API call being made. Please -->
|
||
|
|
<!-- have the Cluster GUI developer check the -->
|
||
|
|
<!--/as400/v5r4m0.guix/cur/cmvc/java.pgm/ugcl.guix/com/ibm/as400/opnav/ugcl/ClGuiActionsManager.java/ClGuiActionsManager.java -->
|
||
|
|
<!-- part to determine if any Cluster GUI code changes are needed. -->
|
||
|
|
<!-- End Developer Note -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<!--Java sync-link-->
|
||
|
|
<script type="text/javascript" language="Javascript" src="../rzahg/synch.js">
|
||
|
|
</script>
|
||
|
|
|
||
|
|
<a name="Top_Of_Page"></a>
|
||
|
|
<img src="delta.gif" alt="Start of change">
|
||
|
|
<h2>Administrative Domain</h2>
|
||
|
|
|
||
|
|
<p>The information provided here includes:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><a href="#header_50">Administrative Domain--Introduction</a></li>
|
||
|
|
|
||
|
|
<li><a href="#header_51">Fpad API List</a></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
|
||
|
|
|
||
|
|
<h3><a name="header_50">Administrative Domain--Introduction</a></h3>
|
||
|
|
|
||
|
|
<p>Cluster Administrative Domain will allow a cluster administrator to maintain a consistent opertational environment across the cluster or a subset of the cluster. A cluster node can only belong to a single administrative domain. Within this domain, the user can specify objects or attributes of the operational environment which will be maintained (replicated) synchronously across the nodes in the domain. Examples of objects/attributes which will be replicated in V5R4 (minimal set) include:</p>
|
||
|
|
<ul>
|
||
|
|
<li>Class</li>
|
||
|
|
<li>Device descriptions</li>
|
||
|
|
<li>Environment variables</li>
|
||
|
|
<li>Job description</li>
|
||
|
|
<li>Network attributes</li>
|
||
|
|
<li>Subsystem description</li>
|
||
|
|
<li>System values</li>
|
||
|
|
<li>TCP attributes</li>
|
||
|
|
<li>User profiles</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
|
||
|
|
<p>Any family resource group API may be called on any node in the cluster which has the System Automation Manager installed with a valid license key.</p>
|
||
|
|
|
||
|
|
<p>All family resource group APIs require:
|
||
|
|
<ul>
|
||
|
|
<li>Cluster Resource Services must be active on the node processing the
|
||
|
|
request.</li>
|
||
|
|
<li>BOSS option 44, System Automation Manager, must be installed and have a valid license key. </li>
|
||
|
|
<li>Resource Monitoring and Control(RMC) job, QCSTRMC, must be active.</li>
|
||
|
|
<li>System Automation Manager job, QSAMSAM, must be active.</li>
|
||
|
|
<li>Cluster Resource Group (CRG) Recovery Manager (RM) job, QSAMCRGRM, must be active.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<h3><a name="Header_59">Terminology</a></h3>
|
||
|
|
|
||
|
|
<p><strong>Quorum.</strong> is a mechanism used to determine when functions are allowed. There are two types of quorum: configuration and operational.
|
||
|
|
<p><strong>Configuration quorum.</strong> determines when configuration changes can be done on a resource
|
||
|
|
<p><strong>Operational quorum.</strong> determines when operational changes (ie online and offline) can be done on a resource.
|
||
|
|
<p><strong>Resource Monitoring and Control (RMC).</strong> provides global access for configuring, monitoring and controlling resources in a cluster.
|
||
|
|
<p><strong>System Automation Manager (SAM).</strong> provides relationships management between cluster resource groups. SAM will manage the relationships of the cluster resource group by starting, stopping, switching and failing over them in the defined order.
|
||
|
|
<p><strong>RMC resource or resource.</strong> is a name for an instance created by a resource class
|
||
|
|
<p><strong>resource class.</strong> An abstract representation of a physical or logical entity which defines a set of attributes and provides a common set of operations. For example IBM.ClusterResourceGroupData is a class the represents a data cluster resource group. This concept is not equivalent to a C++ class. </p>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<h3>Authority to cluster resource groups added to a family resource group.</h3>
|
||
|
|
<p>There will be no authority checking to the cluster resource group when using the Family Resource Group APIs. The authority is managed by authorizing users to the resource classes as specified in each Family Resource Group API.
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<h3><a name="Header_56">Miscellaneous Placeholder</a></h3>
|
||
|
|
|
||
|
|
<P>Document how Admin Domain and Fpad play together.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<!-- Integrated Operating Environments APIs
|
||
|
|
nlkryka@us.ibm.... In ss1b.htm -->
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<h3><a name="header_57">Partition Rules</a></h3>
|
||
|
|
<p>Talk about CRG quorum
|
||
|
|
<p>When a partition is detected, each partition is designated as a primary or
|
||
|
|
secondary partition for each family resource group defined in the cluster. The
|
||
|
|
primary partition contains the node that has the current node role of primary.
|
||
|
|
All other partitions are secondary. The primary partition may not be the same
|
||
|
|
for all family resource groups. The restrictions for each API when in a
|
||
|
|
partition state are:</p>
|
||
|
|
<p>Need to update based on operational and configuration quorum. SAMs primary and secondary partition are the same between these quorum. At least not yet. Operational quorum is based on CRGs and which node is the primary. Op quorum is based on resource in the rg. If all resources in rg have quorum the rg has quorum. COnf quorum is based on RM (on number of nodes in cluster etc...). This will have to change. When it does update this section to be correct.
|
||
|
|
<dl>
|
||
|
|
|
||
|
|
<dt><strong>Create Family Resource Group</strong></dt>
|
||
|
|
|
||
|
|
<dd>Not allowed in any partition.</dd>
|
||
|
|
|
||
|
|
<dt><strong>Delete Family Restore Group</strong></dt>
|
||
|
|
|
||
|
|
<dd>Allowed in any partition, but only affects partition running the API.</dd>
|
||
|
|
|
||
|
|
<dt><strong>End Family Resource Group</strong></dt>
|
||
|
|
|
||
|
|
<dd>Allowed only in a primary partition.</dd>
|
||
|
|
|
||
|
|
<dt><strong>Switch Family Resource Group</strong></dt>
|
||
|
|
|
||
|
|
<dd>Allowed only in a primary partition (need operational quorum for CRGS).</dd>
|
||
|
|
|
||
|
|
<dt><strong>List Family Resource Groups Information</strong></dt>
|
||
|
|
|
||
|
|
<dd>Allowed in any partition.</dd>
|
||
|
|
|
||
|
|
<dt><strong>Modify Family Resource Group</strong></dt>
|
||
|
|
|
||
|
|
<dd>Allowed only in a primary partition (need configuration quorum for SAM).</dd>
|
||
|
|
|
||
|
|
<dt><strong>Start Cluster Resource Group.</strong></dt>
|
||
|
|
|
||
|
|
<dd>Allowed only in a primary partition ( need configuation quorum for SAM and operational for CRG).</dd>
|
||
|
|
</dl>
|
||
|
|
|
||
|
|
|
||
|
|
<p>By applying these restrictions, family resource groups can be
|
||
|
|
resynchronized when the cluster is no longer partitioned. As nodes rejoin the
|
||
|
|
cluster from a partitioned status, the version of the family resource group in
|
||
|
|
the primary partition will be copied to nodes in a secondary partition.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<h3><a name="header_51">Integrated Operating Environments API List</a></h3>
|
||
|
|
|
||
|
|
<p>The Integrated Operating Environments APIs are:</p>
|
||
|
|
<!-- ***** NOTE ***** Do not manually update text or links in this section. -->
|
||
|
|
<!-- Updates made in this section *will* be overlaid by automated tools -->
|
||
|
|
<!-- Notify User Technologies of needed updates to be made in XML for API finder.-->
|
||
|
|
<!--***************API BEGIN PASTE***************-->
|
||
|
|
<ul>
|
||
|
|
|
||
|
|
<li><A HREF="clrgcrtfamrg.htm">Create Family Resource Group</A> (QsamCreateFamilyResourceGroup) establishes a relationship between cluster resource group objects.</li>
|
||
|
|
|
||
|
|
</ul>
|
||
|
|
<!--***************API END PASTE***************-->
|
||
|
|
|
||
|
|
<br>
|
||
|
|
|
||
|
|
|
||
|
|
<hr>
|
||
|
|
<table align="center" cellpadding="2" cellspacing="2">
|
||
|
|
<tr align="center">
|
||
|
|
<td valign="middle" align="center"><a href="#Top_Of_Page">Top</a> | <a href=
|
||
|
|
"clust1a1.htm">Cluster APIs</a> | <a href="aplist.htm">APIs by
|
||
|
|
category</a></td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<img src="deltaend.gif" alt="End of change">
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|