Table of Contents
Table of Contents
1. Overview
xCAT must provide an automatic install and setup process for bringing up DB2 on the Linux and AIX Service Nodes (SN) during the service node install, so that it is configured to access the DB2 database running on the Management Node when the SN installation is complete.
2. Documentation
The following documentation will be modified to describe this process:
[Setting_Up_DB2_as_the_xCAT_DB]
3. Design
To setup DB2 on the Service Nodes:
1. The DB2 code must be installed from the db2 tarball
2. The perl-DBD-DB2 rpm must be installed from the xCAT deps package. Should be automatic.
3. The Service Node must be setup as a DB2 Client, using the db2sqlsetup script
To do this the following process will be followed:
The DB2 tarball will be extracted into a read/mountable directory on either the Management Node or some server that can be mounted by the Service Node after it is installed. The location will be put in a new site attribute called db2installloc. For example,
site.db2installloc = /mntdb2 , if on the Management Node
site.db2installloc = servername:/mntdb2 , if on some other server
In ether case, the db2 code will be extracted and placed in /mntdb2
The /mntdb2 directory will look something like this, where ese is the directory containing all the db2 install code.
ls /mntdb2
ese
For Linux, the appropriate vaccpp rte rpm tarball must be installed on the SN as it was done on the MN. This can either be done by adding to the image (diskless) or into the otherpkgs setup for the service node install.
http://www-01.ibm.com/support/docview.wss?uid=swg24023990
vacpp.rte.90.rhel5.jun2009.update.tar.gz
Finally, a new db2install postscript is to be written, and must be added to the postscripts table, before the servicenode postscript. Also an odbcsetup postscript can be added to set up the ODBC for DB2 applications accessing DB2 using C or C++ like LoadLeveler. It is not required for xCAT which only uses the Perl interface.
tabdump postscripts
node,postscripts,postbootscripts,comments,disable
"xcatdefaults","syslog,aixremoteshell,syncfiles",,,
"service","db2install,servicenode,odbcsetup",,,
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.