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

prescripts support on AIX

Browse Source 
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@6667 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
linggao 2010-07-07 18:34:36 +00:00
parent 99bf0c5e80
commit a05bbf506c
3 changed files with 17 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
perl-xCAT/xCAT/Schema.pm
View File

@ -854,23 +854,27 @@ auditlog => {
prescripts => {
cols => [qw(node begin end comments disable)],
keys => [qw(node)],
table_desc => 'The scripts that should be run at the beginning and the end of the nodeset command.',
table_desc => 'The scripts that will be run at the beginning and the end of the nodeset(Linux), nimnodeset(AIX) or mkdsklsnode(AIX) command.',
descriptions => {
node => 'The node name or group name.',
# Do not put description text past column 88, so it displays well in a 100 char wide window.
# ----------------------------------------------------------------------------------|
begin =>
"The scripts to be run at the beginning of the nodeset (Linux) command.\n".
"The scripts to be run at the beginning of the nodeset(Linux), nimnodeset(AIX)\n" .
" or mkdsklsnode(AIX) command.\n".
" The format is:\n".
" [action1:]s1,s2...[|action2:s3,s4,s5...]\n".
" where:\n".
" - action1 and action2 are the nodeset/nimnodeset actions specified in the command\n".
" - s1 and s2 are the scripts to run for action1 in order\n".
" - s3, s4, and s5 are the scripts to run for actions2\n".
" - action1 and action2 are the nodeset actions specified in the command. \n" .
" For AIX, the action is 'diskless' for mkdsklsnode command and 'standalone'\n" .
" for nimnodeset command. \n" .
" - s1 and s2 are the scripts to run for action1 in order.\n".
" - s3, s4, and s5 are the scripts to run for actions2.\n".
" If actions are omitted, the scripts apply to all actions.\n".
" Examples:\n".
" myscript1,myscript2\n".
" install:myscript1,myscript2|netboot:myscript3\n\n".
" diskless:myscript1,myscript2 (AIX)\n".
" install:myscript1,myscript2|netboot:myscript3 (Linux)\n\n".
" All the scripts should be copied to /install/prescripts directory.\n".
" The following two environment variables will be passed to each script: \n".
" NODES a coma separated list of node names that need to run the script for\n".
@ -879,7 +883,8 @@ prescripts => {
" will get invoked for each node in parallel, but no more than number of instances\n".
" will be invoked at at a time. If it is not sepcified, the script will be invoked\n".
" once for all the nodes.\n",
end => "The scripts to be run at the end of the nodeset (Linux) command. The format is the same as the 'begin' column.",
end => "The scripts to be run at the end of the nodeset(Linux), nimnodeset(AIX)\n" .
" or mkdsklsnode(AIX) command. The format is the same as the 'begin' column.",
comments => 'Any user-written notes.',
disable => "Set to 'yes' or '1' to comment out this row.",
},

3
xCAT-client/pods/man1/mkdsklsnode.1.pod
View File

@ -22,6 +22,9 @@ You can use the force option to reinitialize a node if it already has resources
After the mkdsklsnode command completes you can use the lsnim command to check the NIM node definition to see if it is ready for booting the node. ("lsnim -l <nim_node_name>").
You can supply your own scripts to be run on the mn or on the service node (if their is hierarchy) for a node during the mkdsklsnode command. Such scripts are called B<prescripts>. They should be copied to /install/prescripts dirctory. A table called I<prescripts> is used to specify the scripts and their associated actions. The scripts to be run at the beginning of the mkdsklsnode command are stored in the 'begin' column of I<prescripts> table. The scripts to be run at the end of the mkdsklsnode command are stored in the 'end' column of I<prescripts> table. Please run 'tabdump prescripts -d' command for details. An example for the 'begin' or the 'end' column is: I<diskless:myscript1,myscript2>. The following two environment variables will be passed to each script: NODES contains all the names of the nodes that need to run the script for and ACTION contains the current current nodeset action, in this case "diskless". If I<#xCAT setting:MAX_INSTANCE=number> is specified in the script, the script will get invoked for each node in parallel, but no more than I<number> of instances will be invoked at at a time. If it is not sepcified, the script will be invoked once for all the nodes.
=head1 OPTIONS
=over 10

2
xCAT-client/pods/man1/nimnodeset.1.pod
View File

@ -22,6 +22,8 @@ This command will also create a NIM script resource to enable the xCAT support f
After the nimnodeset command completes you can use the lsnim command to check the NIM node definition to see if it is ready for booting the node. ("lsnim -l <nim_node_name>").
You can supply your own scripts to be run on the mn or on the service node (if their is hierarchy) for a node during the nimnodeset command. Such scripts are called B<prescripts>. They should be copied to /install/prescripts dirctory. A table called I<prescripts> is used to specify the scripts and their associated actions. The scripts to be run at the beginning of the nimnodeset command are stored in the 'begin' column of I<prescripts> table. The scripts to be run at the end of the nimnodeset command are stored in the 'end' column of I<prescripts> table. Please run 'tabdump prescripts -d' command for details. An example for the 'begin' or the 'end' column is: I<standalone:myscript1,myscript2>. The following two environment variables will be passed to each script: NODES contains all the names of the nodes that need to run the script for and ACTION contains the current current nodeset action, in this case "standalone". If I<#xCAT setting:MAX_INSTANCE=number> is specified in the script, the script will get invoked for each node in parallel, but no more than I<number> of instances will be invoked at at a time. If it is not sepcified, the script will be invoked once for all the nodes.
=head1 OPTIONS
=over 10