{{:Design Warning}}
Several enhancements are being made to the xcatsetup command and the cluster config for xCAT 2.6. See the xcatsetup man page for the current documentation of the command and the cluster config file.
The enhancements being worked on are:
-
Allow all ranges to start at something other than 1. E.g. your frame range could be frame[05-20]. Unit test all cases. (Yin Le)
-
Allow chars after the number range. Combine the attach and non-attach code. Now the range formats supported are: (Yin Le)
- f[1-2]c[01-10]p[1-8]a
- f[1-2]c[01-10]p[1-8]
- f[1-2]c[01-10]a
- f[1-2]c[01-10]
- n[01-20]a
- n[01-20]
- n01a-n20a
- n01-n20
-
Support the new attribute for which hmc monitors a frame (ppc.sfp) using the xcat-frames:num-frames-per-hmc setting (Yin Le) - done
-
Support sevice node pools and the routes table to automatically set up routes between MN and CNs thru the SNs: (Bruce)
- set noderes.servicenode for all nodes to a comma separated list of the 2 service nodes in the BB - done
- set the servicenode.ipforwarding attribute to 1 for all servicenodes - done
- populate the routes table with routes through the 2 SNs in each BB, both ways (from MN to CN and from CN to MN)
- set the new node attribute noderes.routenames (being added by Ling) to the routes being put in the routes table for this node - done
- set the new attribute site.mnroutenames to all of the routes for the MN - done
- (Ling will be updating makeroutes and adding a postcript to support routes from the nodes back to the MN.)
-
Support redundant fsps/bpas. (Yin Le)
- Change the bpa/fsa objects into frame/cec objects (done)
- Create bpa and fsp objects (with IP addresses as their nodenames) that are children of the frames and cecs
- Don't assign IP addresses to the frames/cecs
- Add additional variables in the config file for the ranges of all 4 bpas and fsps
-
Make it easy to use xcatsetup to create a single range of objects (Bruce)
- Includes supporting a new setting xcat-cecs:num-cecs-per-frame which avoids having to specify the supernode-list.
-
Support a new setting xcat-service-lan:dhcp-dynamic-range and use it to fill in the networks.dynamicrange attribute, which will cause makedhcp to populate the DHCP config with it. It will also fill in site.dhcpinterfaces. (Yin Le)
-
Support a new range format d001c01, where d is a sequential numbering of the drawers (cecs) for the whole cluster, and c is a simple numbering (1-8) of the compute nodes within the drawer. (Yin Le)
- For now, only support this for the xcat-compute-nodes stanza. For the SNs and storage nodes, support a format like bb01sn1.
-
Add an option for xcatsetup to not change/overwrite objects that are already defined in the db. This allows the user to slightly expand the ranges in the cluster config file (e.g. if they got new hw) and rerun xcatsetup w/o losing modifications they have already made to existing objects in the db. (Yin Le)
- For the regular expressions that are used, nothing has to be done, because they won't override specific node entries
- For all the code that generates hashes of specific node entries, the code should first query the list of existing nodes and put it in a hash so it can quickly look up if a node exists and if so not write the values into the new hash.
-
Write a new command called nodepos which will give all possible position info for a command: (bruce)
- if nodepos table is filled out, show that
- if system p, follow parent for lpar and display name/location of cec and frame
- show hfi location info (supernode #, lpar id, octant #, cec mtms, etc.)
- support going backwards, e.g. if they specify a cage # and lpar id, show the cec hostname and lpar hostname
-
Support reading the cluster config file from stdin (Yin Le)
- the xcatclientnnr already reads stdin, so in setup.pm if they don't pass in a filename in the arg list, try reading from $request->{stdin} before returning an error.
- BTW, while you are testing this, could you change the code in both xcatclient and xcatclientnnr that reads stdin to a more efficient method. Change it from:
if (-p STDIN) { my $data; while ( <STDIN> ) { $data.=$_; } $cmdref->{stdin}->[0]=$data; }
to:
if (-p STDIN) {
my @data = <STDIN>;
$cmdref->{stdin}->[0]=join(_,@data);_
}
News
- Apr 22, 2016: xCAT 2.11.1 released.
- Mar 11, 2016: xCAT 2.9.3 (AIX only) released.
- Dec 11, 2015: xCAT 2.11 released.
- Nov 11, 2015: xCAT 2.9.2 (AIX only) released.
- Jul 30, 2015: xCAT 2.10 released.
- Jul 30, 2015: xCAT migrates from sourceforge to github
- Jun 26, 2015: xCAT 2.7.9 released.
- Mar 20, 2015: xCAT 2.9.1 released.
- Dec 12, 2014: xCAT 2.9 released.
- Sep 5, 2014: xCAT 2.8.5 released.
- May 23, 2014: xCAT 2.8.4 released.
- Jan 24, 2014: xCAT 2.7.8 released.
- Nov 15, 2013: xCAT 2.8.3 released.
- Jun 26, 2013: xCAT 2.8.2 released.
- May 17, 2013: xCAT 2.7.7 released.
- May 10, 2013: xCAT 2.8.1 released.
- Feb 28, 2013: xCAT 2.8 released.
- Nov 30, 2012: xCAT 2.7.6 released.
- Oct 29, 2012: xCAT 2.7.5 released.
- Aug 27, 2012: xCAT 2.7.4 released.
- Jun 22, 2012: xCAT 2.7.3 released.
- May 25, 2012: xCAT 2.7.2 released.
- Apr 20, 2012: xCAT 2.7.1 released.
- Mar 19, 2012: xCAT 2.7 released.
- Mar 15, 2012: xCAT 2.6.11 released.
- Jan 23, 2012: xCAT 2.6.10 released.
- Nov 15, 2011: xCAT 2.6.9 released.
- Sep 30, 2011: xCAT 2.6.8 released.
- Aug 26, 2011: xCAT 2.6.6 released.
- May 20, 2011: xCAT 2.6 released.
- Feb 14, 2011: Watson plays on Jeopardy and is managed by xCAT!
- xCAT Release Notes Summary
- xCAT OS And Hw Support Matrix
- xCAT Test Environment Summary
History
- Oct 22, 2010: xCAT 2.5 released.
- Apr 30, 2010: xCAT 2.4 is released.
- Oct 31, 2009: xCAT 2.3 released.
xCAT's 10 year anniversary! - Apr 16, 2009: xCAT 2.2 released.
- Oct 31, 2008: xCAT 2.1 released.
- Sep 12, 2008: Support for xCAT 2
can now be purchased! - June 9, 2008: xCAT breaths life into
(at the time) the fastest
supercomputer on the planet - May 30, 2008: xCAT 2.0 for Linux
officially released! - Oct 31, 2007: IBM open sources
xCAT 2.0 to allow collaboration
among all of the xCAT users. - Oct 31, 1999: xCAT 1.0 is born!
xCAT started out as a project in
IBM developed by Egan Ford. It
was quickly adopted by customers
and IBM manufacturing sites to
rapidly deploy clusters.