Table of Contents
Table of Contents
External Interface
1. Add a new flag "-n" to nodediscoverstart, to specify to run makedns <nodename> for any new discovered node. This is useful mainly for non-predefined configuration, before running the "nodediscoverstart -n", the user needs to run makedns -n to initialize the named setup on the management node.
2. Add a new argument osimage=xxx to nodediscoverstart, to specify the discovered nodes will be associated with the osimage and start the os provisioning automatically.
3. If the bmciprange is specified with nodediscoverstart, will setup the BMC for any new discovered nodes automatically during the sequential discovery process. A new flag "-s|--skipbmcsetup" is added to skip the bmcsetup, if the user does not want to run bmcsetup for whatever reason, could specify the "-s|--skipbmcsetup" with nodediscoverstart command to skip the bmcsetup.
Internal Design
1. If the -n is specified with nodediscoverstart command, will add a new element "dns=yes" in site.__SEQDiscover, then the subroutine findme could check whether the dns=yes is in site.__SEQDiscover, if yes, run makedns <nodename> for any new discovered node.
2. The osimage=xxx will be added to site.__SEQDiscover by the existing code logic, the subroutine findme will know if the osimage=xxx is specified. In general, the osimage should be the last element in the chain attribute, if the osimage is not already in the chain attribute, sequential discovery code will append the osimage at the end of chain attribute; if the osimage is already in the chain attribute, sequential discovery code will replace the existing osimage name with the new one specified with nodediscoverstart command.
3. If the bmciprange in site.__SEQDiscover, the findme subroutine will add the runcmd=bmcsetup to the node's chain attribute. If the runcmd=bmcsetup is not already in the chain attribute of the node, sequential discovery code will add the runcmd=bmcsetup at the beginning of the chain attribute automatically; if the bmcsetup is already in the chain attribute of the node, then sequential discovery code will not add multiple runcmd=bmcsetup in the chain attribute.
If the -s|--skipbmcsetup is specified with nodediscoverstart command, the nodediscoverstart subroutine will add the "skipbmcsetup=yes" to site.__SEQDiscover, the findme subroutine will check the skipbmcsetup and remove the runcmd=bmcsetup from the node's chain attribute.
Furture consideration
The current design of sequential discovery uses the groups=xxx with nodediscoverstart to inherit attributes from node groups, if the user needs to specify more node attributes for any new discovered node, the user could create node groups with the designated attributes, and specify the groups=xxx with nodediscoverstart the inherit the node attributes from the node group, this mechanism could work, but might be a little bit complex for the users, if we get customer requirements on simplifying this in the future, we could use the "free-form node attributes" with nodediscoverstart, like this:
nodediscoverstart <noderange> attr1=val1 attr2=val2 attr3=val3 ...
where the attr1,attr2,attr3,... are node attributes, the sequential discovery code will set the attributes for any new discovered nodes based on the arguments of nodediscoverstart.
Other Design Considerations
- Required reviewers: Bruce Potter, Jarrod Johnson
- Required approvers: Bruce Potter
- Database schema changes: N/A
- Affect on other components: profile disocvery
- External interface changes, documentation, and usability issues: update doc and manpage for nodediscover* command
- Packaging, installation, dependencies: N/A
- Portability and platforms (HW/SW) supported: N/A
- Performance and scaling considerations: N/A
- Migration and coexistence: N/A
- Serviceability: N/A
- Security: N/A
- NLS and accessibility: N/A
- Invention protection: N/A
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.