arif/xcat-core
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix cage id calculation and update man page

Browse Source 
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@7595 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
bp-sawyers 2010-09-23 17:57:35 +00:00
parent e2c2fef777
commit 3251d37c56
2 changed files with 39 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
xCAT-client/pods/man8/xcatsetup.8.pod
View File

@ -13,7 +13,39 @@ B<xcatsetup> [B<-?> | B<-h> | B<--help> | B<-v> | B<--version>]
The B<xcatsetup> command reads the specified config file that contains general information about the cluster being set up,
and naming conventions and IP addresses that you want to use. It then defines the basic objects in the xCAT database
representing this cluster configuration. The B<xcatsetup> command prepares the database for the step of discovering
the hardware that is connected to the service and cluster networks.
the hardware that is connected to the service and cluster networks. The typical steps of setting up a system p cluster are:
=over 3
=item *
Install the xCAT software on the management node
=item *
Create the cluster config file and run xcatsetup
=item *
Put hardware control passwords in the ppchcp or ppcdirect database table
=item *
Run the discovery commands (lsslp, mkhwconn, rspconfig) as described in the System P Hardware Management cookbook.
=item *
Configure and start the services using makehosts, makedns, makedhcp, mkconserver.cf, etc.
=item *
Create the images that should be installed or booted on the nodes
=item *
Run nodeset and rpower/rnetboot to boot up the nodes.
=back
The B<xcatsetup> command is intended as a quick way to fill out the database for a cluster that has very regular
naming patterns. The only thing is done is fill in database attributes. If your cluster does not follow consistent

8
xCAT-server/lib/xcat/plugins/setup.pm
View File

@ -219,6 +219,9 @@ sub writesite {
$tables{'site'}->setAttribs({key => 'nameservers'}, {value => $ref->{value} });
}
$tables{'site'}->close();
#todo: put dynamic range in networks table
#todo: set site.dhcpinterfaces
}
@ -365,7 +368,7 @@ sub writecec {
foreach my $k (sort keys %framesupers) {
my $f = $framesupers{$k}; # $f is a ptr to an array of super node numbers
if (!$f) { next; } # in case some frame nums did not get filled in by user
my $cageid = 0;
my $cageid = 1;
foreach my $s (@$f) { # loop thru the supernode nums in this frame
my $supernum = $s;
my $numnodes = 4;
@ -373,7 +376,8 @@ sub writecec {
for (my $j=0; $j<$numnodes; $j++) { # assign the next few nodes to this supernode num
my $nodename = $$nodes[$i++];
#print "Setting $nodename supernode attribute to $supernum,$j\n";
$nodehash{$nodename} = { supernode => "$supernum,$j", id => $cageid++, parent => $k };
$nodehash{$nodename} = { supernode => "$supernum,$j", id => $cageid, parent => $k };
$cageid += 2;
}
}
}