Table of Contents
{{:Design Warning}}
Overview
To allow kits deployment on the Management Node to the Management node an osimage must be defined for the Management Node in the database.
Required Reviewers
- Norman Nott
- Linda Mellor
- Kerry Bosworth
Required Approvers
- Bruce Potter
copycds
copycds will be modified to recognize that if the ISO matches what is on the Management node, it will also define a default osimage for the Management node in the database, if not already there. This osimage name will be well-defined, so the xCAT code can recognize it as the osimage for the management node. The osimage attributes will be filled in with the correct defaults for the management node.
The name of the osimage for the MN should match what would be generated by PCM. (Open to discussion).
**rhels6.X-ppc64-stateful-mgmtnode**
Here is the PCM generated Management Node entry:
[root@x3650m2n01 ~]# lsdef __mgmtnode
Object name: x3650m2n01
arch=x86_64
groups=__mgmtnode,__ImageProfile_rhels6.3-x86_64-stateful-mgmtnode
ip=10.1.0.205
nicips=eth0!10.1.0.205,eth1!9.114.34.205
os=rhels6.3
postbootscripts=syncfiles,ospkgs,otherpkgs
postscripts=syslog,remoteshell,syncfiles
profile=compute
**provmethod=rhels6.3-x86_64-stateful-mgmtnode**
status=booted
statustime=26-02-2013 14:10:57
updatestatus=synced
updatestatustime=02-26-2013 14:14:02
If copycds creates a MN osimage definition for the currently running os/distro/version on the MN, and if the provmethod attr for __mgmtnode (group def) is not set, do the equiv of "chdef -t group -o __mgmtnode provmethod=<MN_osimage>
Covered by [defect 3370]
without copycds
If the customer wants to deploy kits on the Management node without running copycds, they will be responsible for manually creating the osimage for the Management Node.
Management node pkglist, otherpkgs, tmpl
After discussion, it was decided we would not ship new files for the management node, we will use the current service node files. If the admin needs to taylor one of these files for the Management Node, they can just change the default in the Management Node osimage.
copycds, will create an image for the Management node, with the same default attributes filled in as if it was for a service node, but with a new unique name for the Management node.
For example, the osimage would have the same attributes set by default as the following osimage, if the MN was rehels6.1 on x86_64.
rhels6.1-x86_64-install-service
Other Design Considerations
- Required reviewers: Bruce Potter
- Required approvers: Bruce Potter
- Database schema changes: N/A
- Affect on other components: N/A
- External interface changes, documentation, and usability issues: N/A
- 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.