diff --git a/xCAT-client/pods/man1/genimage.1.pod b/xCAT-client/pods/man1/genimage.1.pod index 8c2d9f946..1103f6a57 100644 --- a/xCAT-client/pods/man1/genimage.1.pod +++ b/xCAT-client/pods/man1/genimage.1.pod @@ -4,9 +4,9 @@ B - Generates a stateless image to be used for a diskless install. =head1 SYNOPSIS -B B<-i> I B<-n> I B<-o> I B<-p> I [B<-l> I] [B<-r> I] [B<-k> I] +B B<-i> I B<-n> I B<-o> I B<-p> I [B<-l> I] [B<-r> I] [B<-k> I] [B<-m> I] -B B<-i> I B<-n> I B<-o> [B<-l> I] [B<-r> I] [B<-k> I] imagename +B B<-i> I B<-n> I [B<-o> I] [B<-l> I] [B<-r> I] [B<-k> I] imagename B [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 + +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, B and B tables. If this option is not specified, regular non-statelite diskless image will be generated. + =item B<-n> I The driver modules needed for the network interface. Note: the order that the drivers are specified in diff --git a/xCAT-client/pods/man8/nodeset.8.pod b/xCAT-client/pods/man8/nodeset.8.pod index d9545e4df..6ffe0992f 100644 --- a/xCAT-client/pods/man8/nodeset.8.pod +++ b/xCAT-client/pods/man8/nodeset.8.pod @@ -4,7 +4,7 @@ B - set the boot state for a noderange =head1 B -B [I] [I|I|I|I|I|I|I>] +B [I] [I|I|I|I|I|I|I|I>] B [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 + +Prepare server for deploying diskless nodes. With the diskless solution, the os image will reside in the RAM of the node. + +=item B + +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, B and B tables. + =item B> Prepare server for installing a node using the sepcified os image. The os image is defined in the I table and I table.