updated man pages of genimage and nodeset for statelite support
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@5245 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
parent
8899c71a17
commit
adf24c3d6d
@ -4,9 +4,9 @@ B<genimage> - Generates a stateless image to be used for a diskless install.
|
||||
|
||||
=head1 SYNOPSIS
|
||||
|
||||
B<genimage> B<-i> I<nodebootif> B<-n> I<nodenetdrivers> B<-o> I<OS> B<-p> I<profile> [B<-l> I<rootlimit>] [B<-r> I<additional_nics>] [B<-k> I<kernel_version>]
|
||||
B<genimage> B<-i> I<nodebootif> B<-n> I<nodenetdrivers> B<-o> I<OS> B<-p> I<profile> [B<-l> I<rootlimit>] [B<-r> I<additional_nics>] [B<-k> I<kernel_version>] [B<-m> I<mode>]
|
||||
|
||||
B<genimage> B<-i> I<nodebootif> B<-n> I<nodenetdrivers> B<-o> [B<-l> I<rootlimit>] [B<-r> I<additional_nics>] [B<-k> I<kernel_version>] imagename
|
||||
B<genimage> B<-i> I<nodebootif> B<-n> I<nodenetdrivers> [B<-o> I<OS>] [B<-l> I<rootlimit>] [B<-r> I<additional_nics>] [B<-k> I<kernel_version>] imagename
|
||||
|
||||
B<genimage> [B<-h> | B<--help> | B<-v> | B<--version>]
|
||||
|
||||
@ -55,6 +55,10 @@ the nodes' nodetype.profile attribute must be set to this same value.
|
||||
|
||||
The network interface the diskless node will boot over (e.g. eth0).
|
||||
|
||||
=item B<-m> I<mode>
|
||||
|
||||
The mode of diskless image, the valid value is statelite. 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. If this option is not specified, regular non-statelite diskless image will be generated.
|
||||
|
||||
=item B<-n> I<nodenetdrivers>
|
||||
|
||||
The driver modules needed for the network interface. Note: the order that the drivers are specified in
|
||||
|
@ -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<runcmd=bmcsetup>|I<osimage=<imagename>>]
|
||||
B<nodeset> [I<noderange>] [I<boot>|I<install>|I<stat>|I<iscsiboot>|I<netboot>|I<statelite>|I<runcmd=bmcsetup>|I<osimage=<imagename>>]
|
||||
|
||||
B<nodeset> [I<-h>|I<--help>|I<-v>|I<--version>]
|
||||
|
||||
@ -46,6 +46,14 @@ Prepare server for installing a node according to the table configuration. This
|
||||
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>
|
||||
|
||||
Prepare server for deploying diskless nodes. With the diskless solution, the os image will reside in the RAM of the node.
|
||||
|
||||
=item B<statelite>
|
||||
|
||||
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.
|
||||
|
||||
=item 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.
|
||||
|
Loading…
Reference in New Issue
Block a user