mirror of
https://github.com/xcat2/xcat-core.git
synced 2025-08-02 09:37:35 +00:00
update statefull and diskfull to stateful and diskful
for consistency in the documentaion and code
This commit is contained in:
Victor Hu
@@ -219,11 +219,7 @@ automatically mount the ``/tftpboot`` directory from the management node:
|
||||
|
||||
chdef -t site clustersite sharedtftp=0
|
||||
|
||||
For statefull (full-disk) node installs, you will need to use a local
|
||||
``/install`` directory on each service node. The ``/install/autoinst/node``
|
||||
files generated by nodeset will contain values specific to that service node
|
||||
for correctly installing the nodes.
|
||||
::
|
||||
For stateful (diskful) installs, you will need to use a local ``/install`` directory on each service node. The ``/install/autoinst/node`` files generated by nodeset will contain values specific to that service node for correctly installing the nodes. ::
|
||||
|
||||
chdef -t site clustersite installloc=""
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ Overview
|
||||
|
||||
xCAT supports a unique software bundling concept called kits. A software kit combines all of the required product packages with configuration information, scripts, and other files to easily install a software product onto an xCAT node or in an xCAT OS image based on the role that node performs in the cluster. A software kit is made up of a collection of kit components, each of which is tailored to one specific environment for that particular version of the product.
|
||||
|
||||
A software kit is available as a tar file that is downloaded and added to your xCAT management node. The kit components resident in that kit can then be added to an existing xCAT OS image definition and then either be installed on a statefull node during node deployment, added to an active statefull node with the updatenode command, or built into a diskless OS image with the genimage command.
|
||||
A software kit is available as a tar file that is downloaded and added to your xCAT management node. The kit components resident in that kit can then be added to an existing xCAT OS image definition and then either be installed on a stateful node during node deployment, added to an active stateful node with the updatenode command, or built into a diskless OS image with the genimage command.
|
||||
|
||||
Typically, a software kit will contain all of the product package files. However, in some instances, software kits may be delivered as partial or incomplete kits, and not be bundled with all of the product packages. You will then need to obtain your product packages through your reqular distribution channels, download them to a server along with the partial kit, and run the buildkit addpkgs command to build a complete kit that can be used by xCAT.
|
||||
|
||||
@@ -46,7 +46,7 @@ Software Kits are deployed to xCAT nodes through the standard xCAT OS image depl
|
||||
|
||||
When a kitcomponent is added to an OS image definition, these attributes are automatically updated.
|
||||
|
||||
User can then use the genimage command to install the kitcomponents into the diskless OS image, the standard node deployment process for statefull nodes, or the xCAT updatenode command to update the OS on an active compute node. Since the kitcomponent meta package defines the product packages as dependencies, the OS package manager (yum, zypper, apt-get) automatically installs all the required product packages during the xCAT otherpkgs install process.
|
||||
User can then use the genimage command to install the kitcomponents into the diskless OS image, the standard node deployment process for stateful nodes, or the xCAT updatenode command to update the OS on an active compute node. Since the kitcomponent meta package defines the product packages as dependencies, the OS package manager (yum, zypper, apt-get) automatically installs all the required product packages during the xCAT otherpkgs install process.
|
||||
|
||||
Kit Frameworks
|
||||
--------------
|
||||
|
||||
@@ -15,7 +15,7 @@ Or, if know the basename of the kitcomponent, simply: ::
|
||||
|
||||
rmkitcomp -i <image> <kitcompent basename>
|
||||
|
||||
Note that this ONLY removes the kitcomponent from the image definition in the xCAT database, and it will NOT remove any product packages from the actual OS image. To set up for an uninstall of the kitcomponent from the diskless image or the statefull node, specify the uninstall option: ::
|
||||
Note that this ONLY removes the kitcomponent from the image definition in the xCAT database, and it will NOT remove any product packages from the actual OS image. To set up for an uninstall of the kitcomponent from the diskless image or the stateful node, specify the uninstall option: ::
|
||||
|
||||
rmkitcomp -u -i <image> <kitcomponent>
|
||||
|
||||
|
||||
@@ -80,7 +80,7 @@ Note: the trailing **"#"** character at the end of the line. It is important to
|
||||
Group/Pattern Names
|
||||
'''''''''''''''''''
|
||||
|
||||
It is only supported for statefull deployment.
|
||||
It is only supported for stateful deployment.
|
||||
|
||||
In Linux, a groups of rpms can be packaged together into one package. It is called a group on RedHat, CentOS, Fedora and Scientific Linux. To get the a list of available groups, run
|
||||
|
||||
@@ -99,7 +99,7 @@ You can specify in this file the group/pattern names by adding a **'@'** and a s
|
||||
Remove RPMs After Installing
|
||||
''''''''''''''''''''''''''''
|
||||
|
||||
It is only supported for statefull deployment.
|
||||
It is only supported for stateful deployment.
|
||||
|
||||
You can specify in this file that certain rpms to be removed after installing the new software. This is done by adding **'-'** before the rpm names you want to remove. For example: ::
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ NAME
|
||||
****
|
||||
|
||||
|
||||
\ **geninitrd**\ - Generate an initrd (initial ramfs) which to be used for statefull install or stateless netboot.
|
||||
\ **geninitrd**\ - Generate an initrd (initial ramfs) which to be used for stateful install or stateless netboot.
|
||||
|
||||
|
||||
********
|
||||
@@ -34,7 +34,7 @@ Generate the initrd for the osimage: \ **imagename**\ which is an xCAT object o
|
||||
\ **Diskfull Osimage**\
|
||||
|
||||
|
||||
If the \ **imagename**\ is a statefull one (The provmethod attribute for the osimage is 'install'),
|
||||
If the \ **imagename**\ is a stateful one (The provmethod attribute for the osimage is 'install'),
|
||||
this command is used to rebuild the initrd to inject the new drivers from driver rpms or
|
||||
'update distro' and copy the rebuilt initrd and new kernel (If there's new kernel in 'update
|
||||
distro') to the directory \ */tftpboot/xcat/<imagename*\ >.
|
||||
|
||||
@@ -29,9 +29,9 @@ DESCRIPTION
|
||||
***********
|
||||
|
||||
|
||||
The imgexport command will export an image that is being used by xCAT. To export images, you must have the images defined in the \ *osimage*\ table. All the columns in the \ *osimage*\ and \ *linuximage*\ tables will be exported. If kits are used in statefull or stateless images, \ *kit*\ , \ *kitcomponent*\ and \ *kitrepo*\ tables will be exported. In addition, the following files will also be exported.
|
||||
The imgexport command will export an image that is being used by xCAT. To export images, you must have the images defined in the \ *osimage*\ table. All the columns in the \ *osimage*\ and \ *linuximage*\ tables will be exported. If kits are used in stateful or stateless images, \ *kit*\ , \ *kitcomponent*\ and \ *kitrepo*\ tables will be exported. In addition, the following files will also be exported.
|
||||
|
||||
For statefull:
|
||||
For stateful:
|
||||
x.pkglist
|
||||
x.otherpkgs.pkglist
|
||||
x.tmpl
|
||||
|
||||
@@ -31,7 +31,7 @@ DESCRIPTION
|
||||
|
||||
The imgimport command will import an image that has been exported by \ *imgexport*\ from xCAT. This is the easiest way to transfer/backup/, change or share images created by xCAT whether they be stateless or stateful. The bundle file will be unpacked in the current working directory. The xCAT configuration such as \ *osimage*\ and \ *linuximage*\ tables will then be updated.
|
||||
|
||||
For statefull, the following files will be copied to the appropriate directories.
|
||||
For stateful, the following files will be copied to the appropriate directories.
|
||||
x.pkglist
|
||||
x.otherpkgs.pkglist
|
||||
x.tmpl
|
||||
@@ -71,7 +71,7 @@ If -f flag is not specified, all the files will be copied to the same directorie
|
||||
|
||||
After this command, you can run the \ *nodeset*\ command and then start deploying the nodes. You can also choose to modify the files and run the following commands before the node depolyment.
|
||||
|
||||
For statefull:
|
||||
For stateful:
|
||||
nodeset
|
||||
|
||||
For stateless:
|
||||
|
||||
@@ -120,7 +120,7 @@ Output is similar to:
|
||||
|
||||
kitcomponents comp-test1-1.0-1-rhels-6.2-ppc64 were removed from osimage rhels6.2-ppc64-netboot-compute successfully
|
||||
|
||||
3. To remove a kit component from osimage and also remove the kit component meta RPM and package RPM. So in next genimage for statelss image and updatenode for statefull nodes, the kit component meta RPM and package RPM will be uninstalled.
|
||||
3. To remove a kit component from osimage and also remove the kit component meta RPM and package RPM. So in next genimage for statelss image and updatenode for stateful nodes, the kit component meta RPM and package RPM will be uninstalled.
|
||||
|
||||
rmkitcomp -u -i rhels6.2-ppc64-netboot-compute comp-test1-1.0-1-rhels-6.2-ppc64
|
||||
|
||||
|
||||
@@ -49,7 +49,7 @@ to perform the following node updates:
|
||||
|
||||
2
|
||||
|
||||
Install or update software on diskfull nodes.
|
||||
Install or update software on diskful nodes.
|
||||
|
||||
|
||||
|
||||
@@ -114,7 +114,7 @@ The basic process for distributing and synchronizing nodes is:
|
||||
|
||||
|
||||
Files may be distributed and synchronized for both diskless and
|
||||
diskfull nodes. Syncing files to NFS-based statelite nodes is not supported.
|
||||
diskful nodes. Syncing files to NFS-based statelite nodes is not supported.
|
||||
|
||||
More information on using the synchronization file function is in
|
||||
the following doc: Using_Updatenode.
|
||||
@@ -180,7 +180,7 @@ updatenode noderange -P "ospkgs --keeprepo,otherpkgs"
|
||||
|
||||
\ **For AIX systems:**\
|
||||
|
||||
Note: The updatenode command is used to update AIX diskfull nodes only. For updating diskless AIX nodes refer to the xCAT for AIX update documentation and use the xCAT mknimimage command.
|
||||
Note: The updatenode command is used to update AIX diskful nodes only. For updating diskless AIX nodes refer to the xCAT for AIX update documentation and use the xCAT mknimimage command.
|
||||
For information on updating software on AIX cluster:
|
||||
For diskful installs, read:
|
||||
XCAT_AIX_RTE_Diskfull_Nodes
|
||||
@@ -215,7 +215,7 @@ executed on the nodes. The order of the scripts in the list
|
||||
determines the order in which they will be run. You can use the
|
||||
lsdef command to check the postscript order.
|
||||
|
||||
Scripts can be run on both diskless and diskfull nodes.
|
||||
Scripts can be run on both diskless and diskful nodes.
|
||||
|
||||
To run all the customization scripts that have been designated
|
||||
for the nodes, (in the "postscripts and postbootscripts" attributes), type:
|
||||
|
||||
@@ -744,8 +744,8 @@ osimage => {
|
||||
osvers => 'The Linux operating system deployed on this node. Valid values: rhels*,rhelc*, rhas*,centos*,SL*, fedora*, sles* (where * is the version #).',
|
||||
osarch => 'The hardware architecture of this node. Valid values: x86_64, ppc64, x86, ia64.',
|
||||
synclists => 'The fully qualified name of a file containing a list of files to synchronize on the nodes. Can be a comma separated list of multiple synclist files. The synclist generated by PCM named /install/osimages/<imagename>/synclist.cfm is reserved for use only by PCM and should not be edited by the admin.',
|
||||
postscripts => 'Comma separated list of scripts that should be run on this image after diskfull installation or diskless boot. For installation of RedHat, CentOS, Fedora, the scripts will be run before the reboot. For installation of SLES, the scripts will be run after the reboot but before the init.d process. For diskless deployment, the scripts will be run at the init.d time, and xCAT will automatically add the list of scripts from the postbootscripts attribute to run after postscripts list. For installation of AIX, the scripts will run after the reboot and acts the same as the postbootscripts attribute. For AIX, use the postbootscripts attribute. See the site table runbootscripts attribute. Support will be added in the future for the postscripts attribute to run the scripts before the reboot in AIX. ',
|
||||
postbootscripts => 'Comma separated list of scripts that should be run on this after diskfull installation or diskless boot. On AIX these scripts are run during the processing of /etc/inittab. On Linux they are run at the init.d time. xCAT automatically adds the scripts in the xcatdefaults.postbootscripts attribute to run first in the list. See the site table runbootscripts attribute.',
|
||||
postscripts => 'Comma separated list of scripts that should be run on this image after diskful installation or diskless boot. For installation of RedHat, CentOS, Fedora, the scripts will be run before the reboot. For installation of SLES, the scripts will be run after the reboot but before the init.d process. For diskless deployment, the scripts will be run at the init.d time, and xCAT will automatically add the list of scripts from the postbootscripts attribute to run after postscripts list. For installation of AIX, the scripts will run after the reboot and acts the same as the postbootscripts attribute. For AIX, use the postbootscripts attribute. See the site table runbootscripts attribute. Support will be added in the future for the postscripts attribute to run the scripts before the reboot in AIX. ',
|
||||
postbootscripts => 'Comma separated list of scripts that should be run on this after diskful installation or diskless boot. On AIX these scripts are run during the processing of /etc/inittab. On Linux they are run at the init.d time. xCAT automatically adds the scripts in the xcatdefaults.postbootscripts attribute to run first in the list. See the site table runbootscripts attribute.',
|
||||
serverrole => 'The role of the server created by this osimage. Default roles: mgtnode, servicenode, compute, login, storage, utility.',
|
||||
isdeletable => 'A flag to indicate whether this image profile can be deleted. This attribute is only used by PCM.',
|
||||
kitcomponents => 'List of Kit Component IDs assigned to this OS Image definition.',
|
||||
@@ -838,8 +838,8 @@ postscripts => {
|
||||
table_desc => 'The scripts that should be run on each node after installation or diskless boot.',
|
||||
descriptions => {
|
||||
node => 'The node name or group name.',
|
||||
postscripts => 'Comma separated list of scripts that should be run on this node after diskfull installation or diskless boot. Each script can take zero or more parameters. For example: "script1 p1 p2,script2,...". xCAT automatically adds the postscripts from the xcatdefaults.postscripts attribute of the table to run first on the nodes after install or diskless boot. For installation of RedHat, CentOS, Fedora, the scripts will be run before the reboot. For installation of SLES, the scripts will be run after the reboot but before the init.d process. For diskless deployment, the scripts will be run at the init.d time, and xCAT will automatically add the list of scripts from the postbootscripts attribute to run after postscripts list. For installation of AIX, the scripts will run after the reboot and acts the same as the postbootscripts attribute. For AIX, use the postbootscripts attribute. Support will be added in the future for the postscripts attribute to run the scripts before the reboot in AIX. ',
|
||||
postbootscripts => 'Comma separated list of scripts that should be run on this node after diskfull installation or diskless boot. Each script can take zero or more parameters. For example: "script1 p1 p2,script2,...". On AIX these scripts are run during the processing of /etc/inittab. On Linux they are run at the init.d time. xCAT automatically adds the scripts in the xcatdefaults.postbootscripts attribute to run first in the list.',
|
||||
postscripts => 'Comma separated list of scripts that should be run on this node after diskful installation or diskless boot. Each script can take zero or more parameters. For example: "script1 p1 p2,script2,...". xCAT automatically adds the postscripts from the xcatdefaults.postscripts attribute of the table to run first on the nodes after install or diskless boot. For installation of RedHat, CentOS, Fedora, the scripts will be run before the reboot. For installation of SLES, the scripts will be run after the reboot but before the init.d process. For diskless deployment, the scripts will be run at the init.d time, and xCAT will automatically add the list of scripts from the postbootscripts attribute to run after postscripts list. For installation of AIX, the scripts will run after the reboot and acts the same as the postbootscripts attribute. For AIX, use the postbootscripts attribute. Support will be added in the future for the postscripts attribute to run the scripts before the reboot in AIX. ',
|
||||
postbootscripts => 'Comma separated list of scripts that should be run on this node after diskful installation or diskless boot. Each script can take zero or more parameters. For example: "script1 p1 p2,script2,...". On AIX these scripts are run during the processing of /etc/inittab. On Linux they are run at the init.d time. xCAT automatically adds the scripts in the xcatdefaults.postbootscripts attribute to run first in the list.',
|
||||
comments => 'Any user-written notes.',
|
||||
disable => "Set to 'yes' or '1' to comment out this row.",
|
||||
},
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
# AIX:
|
||||
# TBD
|
||||
#
|
||||
# Linux: for statefull (full-disk install) and stateless/statelite nodes
|
||||
# For statefull nodes: run as part of IBMhpc.postbootscript.
|
||||
# Linux: for stateful (full-disk install) and stateless/statelite nodes
|
||||
# For stateful nodes: run as part of IBMhpc.postbootscript.
|
||||
# For stateless/statelite nodes: run as postscript, you will need to
|
||||
# copy this script to /install/postscripts and specify it to nodes'
|
||||
# postscripts attribute.
|
||||
@@ -12,5 +12,5 @@
|
||||
|
||||
|
||||
# BSR configuration on Power 775 cluster. More BSR configuration should
|
||||
# be done by PE postinstall in genimage or postbootscript in statefull install
|
||||
# be done by PE postinstall in genimage or postbootscript in stateful install
|
||||
#chown root:bsr /dev/bsr*
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
#!/bin/sh
|
||||
# Sample Linux postbootscript script for installing and configuring HPC software
|
||||
# for statefull (full-disk install) nodes
|
||||
# Sample Linux postbootscript script for installing and configuring
|
||||
# HPC software for stateful (full-disk install) nodes
|
||||
#
|
||||
# Make sure this runs after the otherpkgs postbootscript
|
||||
#
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
# AIX:
|
||||
# set network tunables
|
||||
#
|
||||
# Linux: for statefull (full-disk install) nodes
|
||||
# Linux: for stateful (full-disk install) nodes
|
||||
# Make sure this runs before the node reboots after initial install
|
||||
# for services to be activated
|
||||
#
|
||||
|
||||
@@ -1,9 +1,7 @@
|
||||
#!/bin/sh
|
||||
|
||||
# Run this script as a postscript on any node (stateless, statefull,
|
||||
# full-disk install, AIX, Linux) to start the GPFS daemon
|
||||
#
|
||||
# Run this script as a postscript on any node to start the GPFS daemon
|
||||
#
|
||||
|
||||
# If you have any special network dependencies, you may want to add code
|
||||
# to check them first
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
=head1 NAME
|
||||
|
||||
B<geninitrd> - Generate an initrd (initial ramfs) which to be used for statefull install or stateless netboot.
|
||||
B<geninitrd> - Generate an initrd (initial ramfs) which to be used for stateful install or stateless netboot.
|
||||
|
||||
=head1 SYNOPSIS
|
||||
|
||||
@@ -17,7 +17,7 @@ B<Diskfull Osimage>
|
||||
|
||||
=over 2
|
||||
|
||||
If the B<imagename> is a statefull one (The provmethod attribute for the osimage is 'install'),
|
||||
If the B<imagename> is a stateful one (The provmethod attribute for the osimage is 'install'),
|
||||
this command is used to rebuild the initrd to inject the new drivers from driver rpms or
|
||||
'update distro' and copy the rebuilt initrd and new kernel (If there's new kernel in 'update
|
||||
distro') to the directory I</tftpboot/xcat/<imagename>>.
|
||||
|
||||
@@ -11,9 +11,9 @@ B<imgexport image_name [destination] [[-e|--extra file:dir] ... ] [-p|--postscri
|
||||
|
||||
=head1 DESCRIPTION
|
||||
|
||||
The imgexport command will export an image that is being used by xCAT. To export images, you must have the images defined in the I<osimage> table. All the columns in the I<osimage> and I<linuximage> tables will be exported. If kits are used in statefull or stateless images, I<kit>, I<kitcomponent> and I<kitrepo> tables will be exported. In addition, the following files will also be exported.
|
||||
The imgexport command will export an image that is being used by xCAT. To export images, you must have the images defined in the I<osimage> table. All the columns in the I<osimage> and I<linuximage> tables will be exported. If kits are used in stateful or stateless images, I<kit>, I<kitcomponent> and I<kitrepo> tables will be exported. In addition, the following files will also be exported.
|
||||
|
||||
For statefull:
|
||||
For stateful:
|
||||
x.pkglist
|
||||
x.otherpkgs.pkglist
|
||||
x.tmpl
|
||||
|
||||
@@ -12,7 +12,7 @@ B<imgimport> bundle_file_name [-p|--postscripts nodelist] [-f|--profile new_prof
|
||||
|
||||
The imgimport command will import an image that has been exported by I<imgexport> from xCAT. This is the easiest way to transfer/backup/, change or share images created by xCAT whether they be stateless or stateful. The bundle file will be unpacked in the current working directory. The xCAT configuration such as I<osimage> and I<linuximage> tables will then be updated.
|
||||
|
||||
For statefull, the following files will be copied to the appropriate directories.
|
||||
For stateful, the following files will be copied to the appropriate directories.
|
||||
x.pkglist
|
||||
x.otherpkgs.pkglist
|
||||
x.tmpl
|
||||
@@ -52,7 +52,7 @@ If -f flag is not specified, all the files will be copied to the same directorie
|
||||
|
||||
After this command, you can run the I<nodeset> command and then start deploying the nodes. You can also choose to modify the files and run the following commands before the node depolyment.
|
||||
|
||||
For statefull:
|
||||
For stateful:
|
||||
nodeset
|
||||
|
||||
For stateless:
|
||||
|
||||
@@ -76,7 +76,7 @@ Output is similar to:
|
||||
|
||||
kitcomponents comp-test1-1.0-1-rhels-6.2-ppc64 were removed from osimage rhels6.2-ppc64-netboot-compute successfully
|
||||
|
||||
3. To remove a kit component from osimage and also remove the kit component meta RPM and package RPM. So in next genimage for statelss image and updatenode for statefull nodes, the kit component meta RPM and package RPM will be uninstalled.
|
||||
3. To remove a kit component from osimage and also remove the kit component meta RPM and package RPM. So in next genimage for statelss image and updatenode for stateful nodes, the kit component meta RPM and package RPM will be uninstalled.
|
||||
|
||||
rmkitcomp -u -i rhels6.2-ppc64-netboot-compute comp-test1-1.0-1-rhels-6.2-ppc64
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ Distribute and synchronize files.
|
||||
|
||||
=item 2
|
||||
|
||||
Install or update software on diskfull nodes.
|
||||
Install or update software on diskful nodes.
|
||||
|
||||
=item 3
|
||||
|
||||
@@ -86,7 +86,7 @@ Run the updatenode command to update the nodes.
|
||||
=back
|
||||
|
||||
Files may be distributed and synchronized for both diskless and
|
||||
diskfull nodes. Syncing files to NFS-based statelite nodes is not supported.
|
||||
diskful nodes. Syncing files to NFS-based statelite nodes is not supported.
|
||||
|
||||
More information on using the synchronization file function is in
|
||||
the following doc: Using_Updatenode.
|
||||
@@ -133,7 +133,7 @@ updatenode noderange -P "ospkgs --keeprepo,otherpkgs"
|
||||
|
||||
B<For AIX systems:>
|
||||
|
||||
Note: The updatenode command is used to update AIX diskfull nodes only. For updating diskless AIX nodes refer to the xCAT for AIX update documentation and use the xCAT mknimimage command.
|
||||
Note: The updatenode command is used to update AIX diskful nodes only. For updating diskless AIX nodes refer to the xCAT for AIX update documentation and use the xCAT mknimimage command.
|
||||
For information on updating software on AIX cluster:
|
||||
For diskful installs, read:
|
||||
XCAT_AIX_RTE_Diskfull_Nodes
|
||||
@@ -161,7 +161,7 @@ executed on the nodes. The order of the scripts in the list
|
||||
determines the order in which they will be run. You can use the
|
||||
lsdef command to check the postscript order.
|
||||
|
||||
Scripts can be run on both diskless and diskfull nodes.
|
||||
Scripts can be run on both diskless and diskful nodes.
|
||||
|
||||
To run all the customization scripts that have been designated
|
||||
for the nodes, (in the "postscripts and postbootscripts" attributes), type:
|
||||
|
||||
Reference in New Issue
Block a user