86 lines
6.4 KiB
HTML
86 lines
6.4 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Plan for a cluster administrative domain" />
|
||
|
|
<meta name="abstract" content="The cluster administrative domain requires planning to manage resources that are shared among nodes within a cluster administrative domain." />
|
||
|
|
<meta name="description" content="The cluster administrative domain requires planning to manage resources that are shared among nodes within a cluster administrative domain." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplan.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigadminchecklist.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaigplanadmindomain" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- 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. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Plan for a cluster administrative domain</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigplanadmindomain"><a name="rzaigplanadmindomain"><!-- --></a>
|
||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Plan for a cluster administrative domain</h1>
|
||
|
|
<div><p><span><img src="./delta.gif" alt="Start of change" />The cluster administrative domain requires planning
|
||
|
|
to manage resources that are shared among nodes within a cluster administrative
|
||
|
|
domain.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
||
|
|
<p>When you create a cluster administrative domain, a peer CRG is created
|
||
|
|
automatically to represent that domain. You can manage a cluster administrative
|
||
|
|
domain using APIs, CL commands and iSeries™ Navigator. </p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />A cluster administrator can create a cluster administrative
|
||
|
|
domain and then can add monitored resources that are shared among nodes.
|
||
|
|
The i5/OS™ Cluster
|
||
|
|
provides a list of system resources that can be shared among nodes within
|
||
|
|
a cluster administrative domain, represented by <dfn class="term">monitored resource entries
|
||
|
|
(MREs)</dfn>. See <a href="rzaigconceptsmre.htm">Monitored
|
||
|
|
resources</a> for a complete list of system resources that can be monitored.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<div class="p">When designing a cluster administrative domain, you should answer the following
|
||
|
|
questions:<dl><dt class="dlterm">What resources will be shared?</dt>
|
||
|
|
<dd>You will need to determine which system resources need to be shared. You
|
||
|
|
can select attributes for each of these resources to customize what is shared
|
||
|
|
amongst nodes. Applications that run on multiple nodes may need specific environment
|
||
|
|
variables to run properly. In addition data that spans several nodes may also
|
||
|
|
require certain user profiles to be accessed. You should be aware of the operational
|
||
|
|
requirements for your applications and data before you determine what resources
|
||
|
|
will be shared.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />What nodes will be included in the cluster administrative domain?<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />You should determine what nodes in a cluster are to be managed by the
|
||
|
|
cluster administrative domain. Nodes cannot be in multiple cluster
|
||
|
|
administrative domains. For example, if you have four nodes in a cluster (Node
|
||
|
|
A, Node B, Node C and Node D). Nodes A and B can be in one cluster administrative
|
||
|
|
domain and Nodes C and D can be in another. However you cannot have Node B
|
||
|
|
and C in another cluster administrative domain. <img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">What will be the naming convention for cluster administrative domains?</dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />Depending on the complexity and size of your clustered
|
||
|
|
environment, you may want to establish a standard naming convention for peer
|
||
|
|
CRGs and cluster administrative domains. Since a peer CRG is created to represent
|
||
|
|
a cluster administrative domain, you will want to differentiate a peer CRG
|
||
|
|
from those that are monitoring resources in your cluster. For example, peer
|
||
|
|
CRGs that represent a cluster administrative domains can be named <var class="varname">ADMDMN1</var>, <var class="varname">ADMDMN2</var>,
|
||
|
|
and so forth, while other peer CRGs can be named <var class="varname">PEER1</var>.
|
||
|
|
You can also use the <a href="../apis/clrglstcrgi.htm"><span class="apiname">List
|
||
|
|
Cluster Resource Group Information (QcstListClusterResourceGroupIn) API</span></a> to
|
||
|
|
determine whether the peer CRG is used as a cluster administrative domain. <img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzaigadminchecklist.htm">Cluster administrative domain checklist</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
Covers all the prerequisites that must be completed before creating a cluster administrative domain.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigplan.htm" title="Find out what you need to do before you can set up clusters on your iSeries servers. Find out the prerequisites for clusters as well as hints on designing your cluster. Finally, read tips for setting up your network and some performance hints for clusters.">Plan for clusters</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|