arif/xcat-core
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

minor change for nodeset man page

Browse Source 
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@14622 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
linggao 2012-12-11 21:16:35 +00:00
parent 1e8061270b
commit 3fd2b30450
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xCAT-client/pods/man8/nodeset.8.pod
View File

@ -4,7 +4,7 @@ B<nodeset> - set the boot state for a noderange
=head1 B<Synopsis>
B<nodeset> [I<noderange>] [I<boot>|I<install>|I<stat>|I<iscsiboot>|I<netboot>|I<statelite>|I<offline>|I<runcmd=bmcsetup>|I<osimage[=<imagename>]>]
B<nodeset> [I<noderange>] [I<boot>|I<install>|I<stat>|I<iscsiboot>|I<netboot>|I<statelite>|I<offline>|I<runcmd=bmcsetup>|I<osimage[=<imagename>>]]
B<nodeset> [I<-h>|I<--help>|I<-v>|I<--version>]
@ -41,17 +41,17 @@ User can supply their own scripts to be run on the mn or on the service node (if
Instruct network boot loader to be skipped, generally meaning boot to hard disk
=item B<install>|B<install=profilename>|B<install=<os-architecture-profilename>
=item B<install>|B<install=profilename>|B<install=<os-architecture-profilename>>
Prepare server for installing a node according to the table configuration. This will
typically mean an unattended install file is created (i.e. kickstart or autoyast),
install resources will be verified in tftp and the bulk transfer method (http, ftp, or nfs for example), and the boot loader configuration file will be written.
=item B<netboot>|B<netboot=profilename>|B<netboot=<os-architecture-profilename>
=item B<netboot>|B<netboot=profilename>|B<netboot=<os-architecture-profilename>>
Prepare server for deploying diskless nodes. With the diskless solution, the os image will reside in the RAM of the node.
=item B<statelite>|B<statelite=profilename>|B<statelite=<os-architecture-profilename>
=item B<statelite>|B<statelite=profilename>|B<statelite=<os-architecture-profilename>>
Prepare server for deploying statelite nodes. Statelite provides an efficient and flexible diskless solution because most of the OS image is NFS mounted read-only, but a configurable list of directories and files can be read-write. The read-write files can either be persistent across reboots, or volatile (restoring to pristine state after reboot). The configuration can be done through B<litefile>, B<litetree> and B<statelite> tables.
@ -61,7 +61,7 @@ Cleanup the current pxe/tftp boot configuration files for the nodes requested
=item B<osimage>|B<osimage=<imagename>>
Prepare server for installing a node using the sepcified os image. The os image is defined in the I<osimage> table and I<linuximage> table. If the <imagename> is omitted, the image name will be obtained from I<nodetype.provmethod> for the node.
Prepare server for installing a node using the sepcified os image. The os image is defined in the I<osimage> table and I<linuximage> table. If the <imagename> is omitted, the os image name will be obtained from I<nodetype.provmethod> for the node.
=item B<stat>