xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-05-29 09:13:08 +00:00
Code Issues Releases Wiki Activity

Remove trailing spaces in file xCAT-client/pods/man1/rollupdate.1.pod

Browse Source
This commit is contained in:
GONG Jie 2017-12-31 23:59:59 +00:00
parent 5ac037b213
commit 4e9aca603b
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
xCAT-client/pods/man1/rollupdate.1.pod
View File

@ -14,10 +14,10 @@ B<rollupdate> [B<-?> | B<-h> | B<--help> | B<-v> | B<--version>]
The B<rollupdate> command creates and submits scheduler reservation jobs that will notify xCAT to shutdown a group of nodes, run optional out-of-band commands from the xCAT management node, and reboot the nodes. Currently, only LoadLeveler is supported as a job scheduler with B<rollupdate>.
Input to the B<rollupdate> command is passed in as stanza data through STDIN. Information such as the sets of nodes that will be updated, the name of the job scheduler, a template for generating job command files, and other control data are required. See
/opt/xcat/share/xcat/rollupdate/rollupdate.input.sample
Input to the B<rollupdate> command is passed in as stanza data through STDIN. Information such as the sets of nodes that will be updated, the name of the job scheduler, a template for generating job command files, and other control data are required. See
/opt/xcat/share/xcat/rollupdate/rollupdate.input.sample
and
/opt/xcat/share/xcat/rollupdate/rollupdate_all.input.sample
/opt/xcat/share/xcat/rollupdate/rollupdate_all.input.sample
for stanza keywords, usage, and examples.
The B<rollupdate> command will use the input data to determine each set of nodes that will be managed together as an update group. For each update group, a job scheduler command file is created and a reservation request is submitted. When the group of nodes becomes available and the scheduler activates the reservation, the xcatd daemon on the management node will be notified to begin the update process for all the nodes in the update group. If specified, prescripts will be run, an operating system shutdown command will be sent to each node, out-of-band operations can be run on the management node, and the nodes are powered back on.
@ -67,7 +67,7 @@ An error has occurred.
=item 1.
To run a cluster rolling update based on the information you have created in the file
To run a cluster rolling update based on the information you have created in the file
/u/admin/rolling_updates/update_all.stanza
enter: