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

update man-pages for profiled nodes releated commands

Browse Source 
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@14956 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
leiaibj 2013-01-23 07:20:41 +00:00
parent a32033c27c
commit 37f35f731a
10 changed files with 172 additions and 151 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
xCAT-client/pods/man1/nodeaddunmged.1.pod
View File

@ -1,16 +1,16 @@
=head1 NAME
B<nodeaddunmged> - Create a un-managed node with hostname and ip address specified.
B<nodeaddunmged> - Create a unmanaged node.
=head1 SYNOPSIS
B<nodeaddunmged> [-h| --help │ -v │ --version]
B<nodeaddunmged> [-h| --help | -v | --version]
B<nodeaddunmged> hostname=<hostname> ip=<ip>
B<nodeaddunmged> hostname=<node-name> ip=<ip-address>
=head1 DESCRIPTION
The B<nodeaddunmged> command will add nodes into group __Unmanaged. And we just need to specify hostname and IP for this node.
The B<nodeaddunmged> command adds an unmanaged node to the __Unmanaged group. You can specify the node name and IP address of the node.
=head1 OPTIONS
@ -22,13 +22,13 @@ B<-v|--version>
Command Version.
B<hostname=<hostname>>
B<hostname=<node-name>>
The hostname of the unmanaged node.
Sets the name of the new unmanaged node, where <node-name> is the name of the node.
B<ip=<ip>>
B<ip=<ip-address>>
The IP address of the unmanaged node.
Sets the IP address of the unmanaged node, where <ip-address> is the IP address of the new node in the form xxx.xxx.xxx.xxx
=head1 RETURN VALUE
@ -38,6 +38,7 @@ The IP address of the unmanaged node.
=head1 EXAMPLES
To add an unmanaged node, use the following command:
nodeaddunmged hostname=unmanaged01 ip=192.168.1.100
=head1 SEE ALSO

19
xCAT-client/pods/man1/nodechmac.1.pod
View File

@ -1,18 +1,18 @@
=head1 NAME
B<nodechmac> - Update a profiled node's provisioning NIC's MAC address.
B<nodechmac> - Updates the MAC address for a node.
=head1 SYNOPSIS
B<nodechmac> [-h| --help │ -v │ --version]
B<nodechmac> [-h| --help | -v | --version]
B<nodechmac> <node> mac=<mac>
B<nodechmac> <node-name> mac=<mac-address>
=head1 DESCRIPTION
The B<nodechmac> command is for changing a node's provisioning NIC's MAC.
The B<nodechmac> command changes the MAC address for provisioned node’s network interface.
This command can be used for following use case: The hardware of a node has some problems and this node will be replaced with a new one. However, Admin wants to apply the old node's configurations to the new one. For example: keep the old hostname, network settings...etc.
You can use this command to keep an existing node configuration. For example, if an existing node has hardware problems, the replacement node can use the old configurations. By using the nodechmac command, the node name and network settings of the old node can be used by the new node.
=head1 OPTIONS
@ -24,13 +24,13 @@ B<-v|--version>
Command Version.
B<node>
B<node-name>
The node name.
Specifies the name of the node you want to update, where <node-name> is the node that is updated.
B<mac=<mac>>
B<mac=<mac-address>
The provisioning NIC's MAC address of the new node.
Sets the new MAC address for the NIC used by the provisioning node, where <mac-address> is the NICs new MAC address.
=head1 RETURN VALUE
@ -40,6 +40,7 @@ The provisioning NIC's MAC address of the new node.
=head1 EXAMPLES
You can update the MAC address for a node, by using the following command:
nodechmac compute-000 mac=2F:3C:88:98:7E:01
=head1 SEE ALSO

34
xCAT-client/pods/man1/nodechprofile.1.pod
View File

@ -1,22 +1,26 @@
=head1 NAME
B<nodechprofile> - Update node profiles for profiled nodes.
B<nodechprofile> - updates a profile used by a node
=head1 SYNOPSIS
B<nodechprofile> [-h| --help │ -v │ --version]
B<nodechprofile> [-h| --help | -v | --version]
B<nodechprofile> <noderange> [imageprofile=<imageprofile>] [networkprofile=<networkprofile>] [hardwareprofile=<hardwareprofile>]
B<nodechprofile> <noderange> [imageprofile=<image-profile>] [networkprofile=<network-profile>] [hardwareprofile=<hardware-profile>]
=head1 DESCRIPTION
The B<nodechprofile> command update following profiles for nodes: imageprofile, networkprofile and hardwareprofile. After profiles for nodes changed, the node's status will be changed to "defined", which means we must reinstall them.
The B<nodechprofile> command updates the profiles used by a node, including: the image profile, network profile, and hardware management profile.
Changing imageprofile will change node's os or provisioning related settings.
If you update the image profile for a node, the operating system and provisioning settings for the node are updated.
Changing networkprofile will change node's network settings. And, B<nodechprofile> will be able to update node's IP address automatically.
If you update the network profile, the IP address and network settings for the node are updated.
Changing hardwareprofile will change node's hardware settings: BMC, FSP...etc.
If you update the hardware management profile, the hardware settings for the node are updated.
After nodes' hardware profile or image profile are updated, the status for each node is changed to "defined". A node with a "defined" status must be reinstalled
After nodes' network profile updated, the status for nodes is not changed. You'll need to run B<noderegenips> to re-generate the nodes' IP address and nodes' status may also be updated at this stage.
=head1 OPTIONS
@ -32,17 +36,17 @@ B<noderange>
The nodes to be removed.
B<imageprofile=<imageprofile>>
B<imageprofile=<image-profile>>
The new image profile name. If there is a group named "__ImageProfile_imgprofile", then "imgprofile" is the image profile name. A image profile defines provisioning method, os info, kit info, provisioning params...etc for nodes.
Sets the new image profile name used by the node, where <image-profile> is the new image profile. An image profile defines the provisioning method, OS information, kit information, and provisioning parameters for a node. If the "__ImageProfile_imgprofile" group already exists in the nodehm table, then "imgprofile" is used as the image profile name.
B<networkprofile=<networkprofile>>
B<networkprofile=<network-profile>>
The network profile name. If there is a group named "__NetworkProfile_netprofile", then "netprofile" is the network profile name. A network profile defines networks, nics, routes...etc for nodes.
Sets the new network profile name used by the node, where <network-profile> is the new network profile. A network profile defines the network, NIC, and routes for a node. If the "__NetworkProfile_netprofile" group already exists in the nodehm table, then "netprofile" is used as the network profile name.
B<hardwareprofile=<hardwareprofile>>
B<hardwareprofile=<hardware-profile>>
The hardware profile name. If there is a group named "__HardwareProfile_hwprofile", then "hwprofile" is the hardware profile name. A harddware profile defines hardware management related info like: IPMI, HMC, CEC, CMM...etc for nodes.
Sets the new hardware profile name used by the node, where <hardware-profile> is the new hardware management profile used by the node. If a "__HardwareProfile_hwprofile" group exists, then "hwprofile" is the hardware profile name. A hardware profile defines hardware management related information for imported nodes, including: IPMI, HMC, CEC, CMM.
=head1 RETURN VALUE
@ -52,8 +56,12 @@ The hardware profile name. If there is a group named "__HardwareProfile_hwprofil
=head1 EXAMPLES
To change the image profile to rhels6.3_packaged for compute nodes compute-000 and compute-001, use the following command:
nodechprofile compute-000,compute-001 imageprofile=rhels6.3_packaged
To change all of the profiles for compute node compute-000, enter the following command:
nodechprofile compute-000 imageprofile=rhels6.3_packaged networkprofile=default_cn hardwareprofile=default_ipmi
=head1 SEE ALSO

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

@ -1,16 +1,16 @@
=head1 NAME
B<nodediscoverls> - List all discovered profiled nodes
B<nodediscoverls> - List all discovered nodes
=head1 SYNOPSIS
B<nodediscoverls> [-h| --help │ -v │ --version]
B<nodediscoverls> [-h| --help | -v | --version]
B<nodediscoverls>
=head1 DESCRIPTION
The B<nodediscoverls> List all discovered profiled nodes at current discover period.
The B<nodediscoverls> command lists all discovered nodes that use a profile in the current node discovery process
=head1 OPTIONS
@ -30,6 +30,8 @@ Command Version.
=head1 EXAMPLES
You can get a list of all discovered nodes, by using the following command:
nodediscoverls
=head1 SEE ALSO

67
xCAT-client/pods/man1/nodediscoverstart.1.pod
View File

@ -1,20 +1,20 @@
=head1 NAME
B<nodediscoverstart> - Start profiled nodes discovery.
B<nodediscoverstart> - starts the node discovery process
=head1 SYNOPSIS
B<nodediscoverstart> [-h| --help │ -v │ --version]
B<nodediscoverstart> [-h| --help | -v | --version]
B<nodediscoverstart> networkprofile=<networkprofile> imageprofile=<imageprofile> hostnameformat=<hostnameformat> [hardwareprofile=<hardwareprofile>] [groups=<groups>] [rack=<rack>] [chassis=<chassis>] [height=<height>] [unit=<unit>] [rank=rank]
B<nodediscoverstart> networkprofile=<network-profile> imageprofile=<image-profile> hostnameformat=<nost-name-format> [hardwareprofile=<hardware-profile>] [groups=<node-groups>] [rack=<rack-name>] [chassis=<chassis-name>] [height=<rack-server-height>] [unit=<rack-server-unit-location>] [rank=rank-num]
=head1 DESCRIPTION
The B<nodediscoverstart> command starts profiled nodes discovery.
The B<nodediscoverstart> command starts the node discovery process. All nodes discovered by this process will be associated with specified profiles and rack/chassis/unit locations.
Once profiled nodes discovery started, admin can bootup nodes which want to be provisioned with PXE. These nodes will be able to discovered automatically. The nodes' settings like hostname and IP address will be assigned automatically according to specified profiles.
You can PXE boot nodes that you want to provision. PXE booting nodes launches the node discovery process. During the node discovery process, nodes are discovered automatically. Node settings are assigned automatically according to the specified profiles
After nodes discovered, the configuration files related with these nodes will be updated automatically. For example: /etc/hosts, dns configuration, dhcp configuration. And the kits node plugins will also be triggered automatically to update kit related configuration/services.
After the nodes are discovered, their configuration files are updated automatically. Configuration files include the /etc/hosts service file, DNS configuration, and DHCP configuration. Kit plug-ins are automatically triggered to update kit related configurations and services.
=head1 OPTIONS
@ -26,58 +26,49 @@ B<-v|--version>
Command Version.
B<networkprofile=<networkprofile>>
B<imageprofile=<image-profile>>
The network profile name. If there is a group named "__NetworkProfile_netprofile", then "netprofile" is the network profile name. A network profile defines networks, nics, routes...etc for imported nodes.
Sets the new image profile name used by the node, where <image-profile> is the new image profile. An image profile defines the provisioning method, OS information, kit information, and provisioning parameters for a node. If the "__ImageProfile_imgprofile" group already exists in the nodehm table, then "imgprofile" is used as the image profile name.
B<imageprofile=<imageprofile>>
B<networkprofile=<network-profile>>
The image profile name. If there is a group named "__ImageProfile_imgprofile", then "imgprofile" is the image profile name. A image profile defines provisioning method, os info, kit info, provisioning params...etc for imported nodes.
Sets the new network profile name used by the node, where <network-profile> is the new network profile. A network profile defines the network, NIC, and routes for a node. If the "__NetworkProfile_netprofile" group already exists in the nodehm table, then "netprofile" is used as the network profile name.
B<hardwareprofile=<hardwareprofile>>
B<hardwareprofile=<hardware-profile>>
The hardware profile name. If there is a group named "__HardwareProfile_hwprofile", then "hwprofile" is the hardware profile name. A harddware profile defines hardware management related info like: IPMI, HMC, CEC, CMM...etc for imported nodes.
Sets the new hardware profile name used by the node, where <hardware-profile> is the new hardware management profile used by the node. If a "__HardwareProfile_hwprofile" group exists, then "hwprofile" is the hardware profile name. A hardware profile defines hardware management related information for imported nodes, including: IPMI, HMC, CEC, CMM.
B<hostnameformat=<hostnameformat>>
B<hostnameformat=<nost-name-format>>
The hostname format for generating hostnames for nodes if the hostname for a node is specified as "__hostname__" in hostinfo file.
Following hostname format types are supported:
Sets the node name format for all nodes discovered, where <node-name-format> is a supported format. The two types of formats supported are prefix#NNNappendix and prefix#RRand#NNappendix, where wildcard #NNN and #NN are replaced by a system generated number that is based on the provisioning order. Wildcard #RR represents the rack number and stays constant.
B<prefix#NNNappendix>
For example, if the node name format is compute-#NN, the node name is generated as: compute-00, compute-01, ..., compute-99. If the node name format is blade#NNN-x64, the node name is generated as: blade001-x64, blade002-x64, ..., blade999-x64
For example:
If hostname format is compute-#NN, then node's hostname will be generated automatically like: compute-00, compute-01, ...compute-99
If hostname format is blade#NNN-x64, then node's hostname will be generated automatically like: blade001-x64, blade002-x64, ..., blade999-x64
For example, if the node name format is compute-#RR-#NN and the rack number is 2, the node name is generated as: compute-02-00, compute-02-01, ..., compute-02-99. If node name format is node-#NN-in-#RR and rack number is 1, the node name is generated as: node-00-in-01, node-01-in-01, ..., node-99-in-01
B<prefix#RRand#NNappendix>
B<groups=<node-groups>>
For example:
If hostname format is compute-#RR-#NN, then nodes which placed in a rack which rack number is 2 will be generated with hostnames like: compute-02-00, compute-02-01, ..., compute-02-99. And nodes which placed in another rack wich rack number is 5 will be generated with hostnames like: compute-05-00, compute-05-01, ..., compute-05-99.
If hostname format is node-#NN-in-#RR, then hostnames for nodes in rack with rack number 1 will be: node-00-in-01, node-01-in-01, ..., node-99-in-01. And hostnames for nodes in rack with rack number 2 will be: node-00-in-02, node-01-in-02, ..., node-99-in-02.
Sets the node groups that the imported node belongs to, where <node-group> is a comma-separated list of node groups.
B<groups=<groups>>
B<rack=<rack-name>>
The groups which the imported nodes will belong to.
B<rack=<rack name>>
node location info. Specify the rack name which this node will be placed into.
Sets the rack name, where <rack-name> is the rack the node is located on or placed into.
B<chasiss=<chassis name>>
B<chasiss=<chassis-name>>
node location info, for blade(or PureFlex) only. Specify the chasiss name which this blade will be placed into. This item can not be specified together with rack.
Sets the chassis name, where <chassis-name> is the chassis that the Blade server or PureFlex sysstem is located. This option is used for the Blade server and PureFlex system only. You cannot specify this option with the rack option.
B<height=<chassis name>>
B<height=<rack-server-height>>
node location info, for rack server only. Specify the server height number, in U. This item must be specified together with rack. If not specified, the default value is 1.
Sets the height of a rack server, where <rack-server-height> is the server height. You must specify the this option with the rack option. If the rack option is not specified, the default value is 1.
B<unit=<unit name>>
B<unit=<rack-server-unit-location>>
node location info, for rack server only. Specify the node's start unit number in rack, in U. This item must be specified together with rack. If not specified, the default value is 1.
Sets the start unit value for the node, where <rack-server-unit-location> is the location of the starting rack. This option is for a rack server only. You must specify this option with the rack option. If the unit option is not specified, the default value is 1
B<rank=<rank>>
B<rank=<rank-num>>
Defines the start number in hostname format. If hostname format specified like "compute#NNN" and rank is set to 5, then hostnames of discovered nodes will be named as: "compute005, compute006, ..."
Specifies the starting rank number that is used in the node name format, where <rack-num> is a valid integer between 0 and 254. This option must be specified with nodenameformat option. For example, if your node name format is compute-#RR-#NN. The rack's number is 2 and rank is specified as 5, the node name is generated as follows: compute-02-05, compute-02-06, ..., compute-02-99.
=head1 RETURN VALUE
@ -87,6 +78,8 @@ Defines the start number in hostname format. If hostname format specified like "
=head1 EXAMPLES
To discover nodes using the default_cn network profile and the rhels6.3_packaged image profile, use the following command:
nodediscoverstart networkprofile=default_cn imageprofile=rhels6.3_packaged hostnameformat=compute#NNN
=head1 SEE ALSO

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

@ -1,16 +1,16 @@
=head1 NAME
B<nodediscoverstatus> - Detect whether Profiled nodes discovery is running or not.
B<nodediscoverstatus> - gets the node discovery process status
=head1 SYNOPSIS
B<nodediscoverstatus> [-h| --help │ -v │ --version]
B<nodediscoverstatus> [-h| --help | -v | --version]
B<nodediscoverstatus>
=head1 DESCRIPTION
The B<nodediscoverstatus> Detect whether Profiled nodes discovery is running or not.
The B<nodediscoverstatus> command detects if the node discovery process is running.
=head1 OPTIONS
@ -30,6 +30,8 @@ Command Version.
=head1 EXAMPLES
To determine if there are some nodes discovered and the discovered nodes' status, enter the following command:
nodediscoverstatus
=head1 SEE ALSO

6
xCAT-client/pods/man1/nodediscoverstop.1.pod
View File

@ -1,16 +1,16 @@
=head1 NAME
B<nodediscoverstop> - Stop profiled nodes auto discover.
B<nodediscoverstop> - stops the node discovery process.
=head1 SYNOPSIS
B<nodediscoverstop> [-h| --help │ -v │ --version]
B<nodediscoverstop> [-h| --help | -v | --version]
B<nodediscoverstop>
=head1 DESCRIPTION
The B<nodediscoverstop> command stops profiled nodes discover and the new booted nodes will not be discovered as profiled nodes any more.
The B<nodediscoverstop> stops the node discovery process. The node discovery process can discover nodes automatically. If this command is issued, any newly booted nodes can not be discovered any more.
=head1 OPTIONS

148
xCAT-client/pods/man1/nodeimport.1.pod
View File

@ -4,9 +4,9 @@ B<nodeimport> - Create profiled nodes by importing hostinfo file.
=head1 SYNOPSIS
B<nodeimport> [-h| --help │ -v │ --version]
B<nodeimport> [-h| --help | -v | --version]
B<nodeimport> file=<hostinfo file> networkprofile=<networkprofile> imageprofile=<imageprofile> hostnameformat=<hostnameformat> [hardwareprofile=<hardwareprofile>] [groups=<groups>]
B<nodeimport> file=<nostinfo-filename> networkprofile=<network-profile> imageprofile=<image-profile> hostnameformat=<node-name-format> [hardwareprofile=<hardware-profile>] [groups=<node-groups>]
=head1 DESCRIPTION
@ -24,43 +24,33 @@ B<-v|--version>
Command Version.
B<file=<hostinfo file>>
B<file=<nodeinfo-filename>>
The full path of the hostinfo file.
Specifies the node information file, where <nodeinfo-filename> is the full path and file name of the node information file.
B<networkprofile=<networkprofile>>
B<imageprofile=<image-profile>>
The network profile name. If there is a group named "__NetworkProfile_netprofile", then "netprofile" is the network profile name. A network profile defines networks, nics, routes...etc for imported nodes.
Sets the new image profile name used by the node, where <image-profile> is the new image profile. An image profile defines the provisioning method, OS information, kit information, and provisioning parameters for a node. If the "__ImageProfile_imgprofile" group already exists in the nodehm table, then "imgprofile" is used as the image profile name.
B<imageprofile=<imageprofile>>
B<networkprofile=<network-profile>>
The image profile name. If there is a group named "__ImageProfile_imgprofile", then "imgprofile" is the image profile name. A image profile defines provisioning method, os info, kit info, provisioning params...etc for imported nodes.
Sets the new network profile name used by the node, where <network-profile> is the new network profile. A network profile defines the network, NIC, and routes for a node. If the "__NetworkProfile_netprofile" group already exists in the nodehm table, then "netprofile" is used as the network profile name.
B<hardwareprofile=<hardwareprofile>>
B<hardwareprofile=<hardware-profile>>
The hardware profile name. If there is a group named "__HardwareProfile_hwprofile", then "hwprofile" is the hardware profile name. A harddware profile defines hardware management related info like: IPMI, HMC, CEC, CMM...etc for imported nodes.
Sets the new hardware profile name used by the node, where <hardware-profile> is the new hardware management profile used by the node. If a "__HardwareProfile_hwprofile" group exists, then "hwprofile" is the hardware profile name. A hardware profile defines hardware management related information for imported nodes, including: IPMI, HMC, CEC, CMM.
B<hostnameformat=<hostnameformat>>
B<hostnameformat=<nost-name-format>>
The hostname format for generating hostnames for nodes if the hostname for a node is specified as "__hostname__" in hostinfo file.
Following hostname format types are supported:
Sets the node name format for all nodes discovered, where <node-name-format> is a supported format. The two types of formats supported are prefix#NNNappendix and prefix#RRand#NNappendix, where wildcard #NNN and #NN are replaced by a system generated number that is based on the provisioning order. Wildcard #RR represents the rack number and stays constant.
B<prefix#NNNappendix>
For example, if the node name format is compute-#NN, the node name is generated as: compute-00, compute-01, ... , compute-99. If the node name format is blade#NNN-x64, the node name is generated as: blade001-x64, blade002-x64, ... , blade999-x64
For example:
If hostname format is compute-#NN, then node's hostname will be generated automatically like: compute-00, compute-01, ...compute-99
If hostname format is blade#NNN-x64, then node's hostname will be generated automatically like: blade001-x64, blade002-x64, ..., blade999-x64
For example, if the node name format is compute-#RR-#NN and the rack number is 2, the node name is generated as: compute-02-00, compute-02-01, ..., compute-02-99. If node name format is node-#NN-in-#RR and rack number is 1, the node name is generated as: node-00-in-01, node-01-in-01, ... , node-99-in-01
B<prefix#RRand#NNappendix>
For example:
If hostname format is compute-#RR-#NN, then nodes which placed in a rack which rack number is 2 will be generated with hostnames like: compute-02-00, compute-02-01, ..., compute-02-99. And nodes which placed in another rack wich rack number is 5 will be generated with hostnames like: compute-05-00, compute-05-01, ..., compute-05-99.
If hostname format is node-#NN-in-#RR, then hostnames for nodes in rack with rack number 1 will be: node-00-in-01, node-01-in-01, ..., node-99-in-01. And hostnames for nodes in rack with rack number 2 will be: node-00-in-02, node-01-in-02, ..., node-99-in-02.
B<groups=<groups>>
The groups which the imported nodes will belong to.
B<groups=<node-groups>>
Sets the node groups that the imported node belongs to, where <node-group> is a comma-separated list of node groups.
=head1 RETURN VALUE
@ -73,8 +63,10 @@ The groups which the imported nodes will belong to.
=head1 EXAMPLES
An example for importing profiled nodes.
1. Run "tabdump nodegroups" to get all groups and find out which ones are avaiable profiles. Then run "lsdef -t group <groupname>" to get the detailed info for these profiles. like:
To import nodes using a profile, follow the following steps:
1. Find all node groups and profiles, run the following command "tabdump nodegroups". For detailed profile information run "lsdef -t group <groupname>". Example of detailed profile information:
# tabdump nodegroup
#groupname,grouptype,members,membergroups,wherevals,comments,disable
"compute","static",,,,,
@ -94,60 +86,80 @@ An example for importing profiled nodes.
nictypes=eth0:Ethernet
primarynic=eth0
2. Prepare a hostinfo file looks like:
2. Prepare a node information file.
# hostinfo begin
Example of a node information file, a blade and a rack server defined:
# hostinfo begin
# This entry defines a blade.
__hostname__:
mac=b8:ac:6f:37:59:24
ip=192.168.1.20
chassis=chassis01
__hostname__:
mac=b8:ac:6f:37:59:24
ip=192.168.1.20
chassis=chassis01
# This entry defines a rack server.
__hostname__:
mac=b8:ac:6f:37:59:25
ip=192.168.1.20
rack=rack01
height=1
unit=2
__hostname__:
mac=b8:ac:6f:37:59:25
ip=192.168.1.20
rack=rack01
height=1
unit=2
# hostinfo end.
# hostinfo end.
Another example of a node infomation file, a PureFlex X/P node defined:
# hostinfo begin
# To define a PureFlex P/X node, chassis and slot id must be specified.
# The chassis must be a PureFlex chassis.
__hostname__:
mac=b8:ac:6f:37:59:25
chassis=cmm01
slotid=1
# hostinfo end.
Here, we are going to import 2 nodes, and about each line of this file:
__hostname__: - Mandatory item
Description: The hostname for the node.
If you want to specify the hostname for this node, just write like: "compute-001:"
If you want the hostname auto generated from hostnameformat, just write like: "__hostname__:"
The node information file includes the following items:
mac=<mac str> - Mandatory item
Description: Specify the node's provisioning nic's MAC address
B<__hostname__:> This is a mandatory item.
ip=<ip str> - Optional item
Description: Specify the node's provisioing IP address.
If not specify this item, node's provisioning IP will be generated automatically according to NetworkProfile.
Description: The name of the node, where __hostname__ is automatically generated by the node name format. You can also input a fixed node name, for example “compute-node”.
rack=<rack name> - Optional item
Description: node location info. Specify the rack name which this node will be placed into.
If not specify this item, there will be no node location info set for this node.
this item must be specified together with height + unit.
chasiss=<chassis name> - Optional item
Description: node location info, for blade(or PureFlex) only. Specify the chasiss name which this blade will be placed into.
this item can not be specified together with rack.
B<mac=<mac-address>> This is a mandatory item.
height=<chassis name> - Optional item
Description: node location info, for rack server only. Specify the server height number, in U.
this item must be specified together with rack and unit.
Description: Specify the MAC address for the NIC used by the provisionging node, where <mac-address> is the NICs MAC address.
unit=<unit name> - Optional item
Description: node location info, for rack server only. Specify the node's start unit number in rack, in U.
this item must be specified together with rack and height.
B<slotid=<slot-id>> This is a mandatory item while define a PureFlex node.
3. Run nodeimport command:
Description: The node position in the PureFlex Chassis.
B<ip=<ip-address>> This is an optional item.
Description: Specify the IP address used for provisioning a node, where <ip-address> is in the form xxx.xxx.xxx.xxx. If this item is not included, the IP address used to provision the node is generated automatically according to the Network Profile used by the node.
B<rack=<rack-name>> This is an optional item.
Description: node location info. Specify the rack name which this node will be placed into. If not specify this item, there will be no node location info set for this node. this item must be specified together with height + unit.
B<rack=<rack-name>> This is an optional item.
Description: node location info. Specify the rack name which this node will be placed into. If not specify this item, there will be no node location info set for this node. this item must be specified together with height + unit.
B<chasiss=<chassis-name>> This is an optional item.
Description: node location info, for blade(or PureFlex) only. Specify the chasiss name which this blade will be placed into. this item can not be specified together with rack.
B<height=<chassis-height>> This is an optional item.
Description: node location info, for rack server only. Specify the server height number, in U. this item must be specified together with rack and unit.
B<unit=<rack-server-unit-location>> This is an optional item.
Description: node location info, for rack server only. Specify the node's start unit number in rack, in U. this item must be specified together with rack and height.
3. Import the nodes, by using the following commands. Note: If we want to import PureFlex X/P nodes, hardware profile must be set to a PureFlex hardware type.
nodeimport file=/root/hostinfo.txt networkprofile=default_cn imageprofile=rhels6.3_packaged hostnameformat=compute-#NNN
4. After node import succeeds, we'll get 2 nodes created, And node's configurations like dhcp, dns, /etc/hosts will be updated automatically too.
4. After importing the nodes, the nodes are created and all configuration files used by the nodes are updated, including: /etc/hosts, DNS, DHCP.
5. Reboot the nodes, they will be provisioned automatically.
5. Reboot the nodes. After the nodes are booted they are provisioned automatically.
=head1 SEE ALSO

10
xCAT-client/pods/man1/nodepurge.1.pod
View File

@ -1,18 +1,18 @@
=head1 NAME
B<nodepurge> - Remove nodes from database, also remove them from system configuration.
B<nodepurge> - Removes nodes.
=head1 SYNOPSIS
B<nodepurge> [-h| --help │ -v │ --version]
B<nodepurge> [-h| --help | -v | --version]
B<nodepurge> <noderange>
=head1 DESCRIPTION
The B<nodepurge> command removes nodes records from database, and also remove relative configuration automatically.
The B<nodepurge> automatically removes all nodes from the database and any related configurations used by the node.
After nodes removed, the configuration files related with these nodes will be updated automatically. For example: /etc/hosts, dns configuration, dhcp configuration. And the kits node plugins will also be triggered automatically to update kit related configuration/services.
After the nodes are removed, the configuration files related to these nodes are automatically updated, including the following files: /etc/hosts, DNS, DHCP. Any kits that are used by the nodes are triggered to automatically update kit configuration and services.
=head1 OPTIONS
@ -36,6 +36,8 @@ The nodes to be removed.
=head1 EXAMPLES
To remove nodes compute-000 and compute-001, use the following command:
nodepurge compute-000,compute-001
=head1 SEE ALSO

6
xCAT-client/pods/man1/noderefresh.1.pod
View File

@ -1,16 +1,16 @@
=head1 NAME
B<noderefresh> - Re-Call kit plugins for profiled nodes
B<noderefresh> - Update nodes configurations by running associated kit plugins.
=head1 SYNOPSIS
B<noderefresh> [-h| --help │ -v │ --version]
B<noderefresh> [-h| --help | -v | --version]
B<noderefresh> <noderange>
=head1 DESCRIPTION
The B<noderefresh> command will just call kit plugins for profiled nodes, in-order to refresh node's related configurations/services.
The B<noderefresh> command will update nodes settings, it will call all associated kit plug-in configurations and also services
=head1 OPTIONS