2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-05-25 21:22:05 +00:00

enhancement for hdwr_discovery doc

This commit is contained in:
ertaozh 2015-09-16 10:57:57 -04:00 committed by GONG Jie
parent 02919ea080
commit ab59d92c50
12 changed files with 103 additions and 120 deletions

View File

@ -1,2 +0,0 @@
Manually Define Nodes
=====================

View File

@ -1,2 +0,0 @@
MTMS-based Discovery
====================

View File

@ -5,59 +5,65 @@ configure network table
```````````````````````
Normally, there will be at least two entries for the two subnet on MN in "networks" table after xCAT is installed::
Normally, there will be at least two entries for the two subnet on MN in ``networks`` table after xCAT is installed::
#tabdump networks
#netname,net,mask,mgtifname,gateway,dhcpserver,tftpserver,nameservers,ntpservers,logservers,dynamicrange,staticrange,staticrangeincrement,nodehostname,ddnsdomain,vlanid,domain,comments,disable
"10_0_0_0-255_255_0_0","10.0.0.0","255.255.0.0","eth1","<xcatmaster>",,"10.0.1.1",,,,,,,,,,,,
"50_0_0_0-255_255_0_0","50.0.0.0","255.255.0.0","eth2","<xcatmaster>",,"50.0.1.1",,,,,,,,,,,,
Pls run the following command to add networks in "networks" table if no entry in "networks" table::
Pls run the following command to add networks in ``networks`` table if no entry in ``networks`` table::
#makenetworks
makenetworks
setup DHCP
``````````
Set the correct NIC from which DHCP server provide service::
#chdef -t site dhcpinterfaces=eth1,eth2
chdef -t site dhcpinterfaces=eth1,eth2
Add dynamic range in purpose of assigning temporary IP adddress for FSP/BMCs and hosts::
#chdef -t network 10_0_0_0-255_255_0_0 dynamicrange="10.0.100.1-10.0.100.100"
#chdef -t network 50_0_0_0-255_255_0_0 dynamicrange="50.0.100.1-50.0.100.100"
chdef -t network 10_0_0_0-255_255_0_0 dynamicrange="10.0.100.1-10.0.100.100"
chdef -t network 50_0_0_0-255_255_0_0 dynamicrange="50.0.100.1-50.0.100.100"
Update DHCP configuration file::
#makedhcp -n
#makedhcp -a
makedhcp -n
makedhcp -a
setup DNS
`````````
Set site.forwarders to your site-wide DNS servers that can resolve site or public hostnames. The DNS on the MN will forward any requests it can't answer to these servers::
#chdef -t site forwarders=8.8.8.8
chdef -t site forwarders=8.8.8.8
Run makedns to get the hostname/IP pairs copied from /etc/hosts to the DNS on the MN::
#makedns -n
makedns -n
Config passwd table
```````````````````
To configure default password for FSP/BMCs and Hosts::
Set required passwords for xCAT to do hardware management and/or OS provisioning by adding entries to the xCAT ``passwd`` table::
#tabedit passwd
#key,username,password,cryptmethod,authdomain,comments,disable
"system","root","cluster",,,,
"ipmi","ADMIN","admin",,,,
# tabedit passwd
# key,username,password,cryptmethod,authdomain,comments,disable
Check the genesis pkg
`````````````````````
For hardware management with ipmi, add the following line::
Genesis pkg can be used to creates a network boot root image, it must be installed before do hardware discovery.
"ipmi","ADMIN","admin",,,,
For OS provisioning, add the following line::
"system","root","cluster",,,,
Verify the genesis pkg
``````````````````````
Genesis pkg is used to **create the root image for network boot** and it **MUST** be installed before doing hardware discovery.
* **[RH]**::
@ -71,6 +77,4 @@ Genesis pkg can be used to creates a network boot root image, it must be install
ii xcat-genesis-base-ppc64 2.10-snap201505172314 all xCAT Genesis netboot image
ii xcat-genesis-scripts 2.10-snap201507240105 ppc64el xCAT genesis
**Note:** If the two pkgs haven't installed yet, pls installed them first and then run the following command to create the network boot root image::
#mknb ppc64
**Note:** If the two pkgs are not installed, pls installed them first and then run ``mknb ppc64`` to create the network boot root image.

View File

@ -1,7 +1,7 @@
Hardware Discovery & Define Node
================================
Hardware discovery is used to configure the FSP/BMC and get the hardware configuration information for the physical server. The physical server can be defined into xCAT database manually, or though our hardware discovery process which include mtms based, switch based and sequential based hardware discovery progress.
Hardware discovery is used to configure the FSP/BMC to get the hardware configuration information for the physical servers. The physical servers can be defined into xCAT database manually, or though our hardware discovery process. The available options for hardware discovery are MTMS based, switch based and sequential based.
.. toctree::
:maxdepth: 2

View File

@ -1,6 +1,7 @@
.. include:: ../../common/discover/manually_define.rst
Manually Define Nodes
=====================
Manually define node means the admin know detailed information of the physical server. Then define it into xCAT database with commands.
Manually define node means the admin know detailed information of the physical server and defines it into xCAT database with commands.
.. include:: schedule_environment.rst
@ -9,13 +10,13 @@ Manually define node
To add a node object::
#nodeadd cn1 groups=pkvm,all
nodeadd cn1 groups=powerLE,all
To change node attributes::
Use the ``chdef`` command to add and change node attributes: ::
#chdef cn1 mgt=ipmi cons=ipmi ip=10.0.101.1 netboot=petitboot
#chdef cn1 bmc=50.0.101.1 bmcusername=ADMIN bmcpassword=admin
#chdef cn1 installnic=mac primarynic=mac mac=6c:ae:8b:6a:d4:e4
chdef cn1 mgt=ipmi cons=ipmi ip=10.0.101.1 netboot=petitboot
chdef cn1 bmc=50.0.101.1 bmcusername=ADMIN bmcpassword=admin
chdef cn1 installnic=mac primarynic=mac mac=6c:ae:8b:6a:d4:e4
The manually defined node will be like this::
@ -25,7 +26,7 @@ The manually defined node will be like this::
bmcpassword=admin
bmcusername=ADMIN
cons=ipmi
groups=pkvm,all
groups=powerLE,all
installnic=mac
ip=10.0.101.1
mac=6c:ae:8b:6a:d4:e4

View File

@ -1,8 +1,8 @@
.. include:: ../../common/discover/manually_discovery.rst
If you have a few nodes which were not discovered by automated hardware discovery progress, you could find them in discoverydata table using the nodediscoverls. The undiscovered nodes are those that have a discovery method value of 'undef' in the discoverydata table.
If you have a few nodes which were not discovered by automated hardware discovery process, you could find them in ``discoverydata`` table using the nodediscoverls. The undiscovered nodes are those that have a discovery method value of 'undef' in the ``discoverydata`` table.
Display the undefined nodes with the nodediscoverls command::
Display the undefined nodes with the ``nodediscoverls`` command::
#nodediscoverls -t undef
UUID NODE METHOD MTM SERIAL
@ -10,16 +10,16 @@ Display the undefined nodes with the nodediscoverls command::
If you want to manually define an 'undefined' node to a specific free node name, use the nodediscoverdef(TODO) command.
Before doing that, a node with desired IP address for hsot and FSP/BMC shall be defined first::
Before doing that, a node with desired IP address for host and FSP/BMC must be defined first::
#nodeadd cn1 groups=pkvm,all
#chdef cn1 mgt=ipmi cons=ipmi ip=10.0.101.1 bmc=50.0.101.1 netboot=petitboot installnic=mac primarynic=mac
nodeadd cn1 groups=powerLE,all
chdef cn1 mgt=ipmi cons=ipmi ip=10.0.101.1 bmc=50.0.101.1 netboot=petitboot installnic=mac primarynic=mac
For example, if you want to assign the undefined node whose uuid is 'fa2cec8a-b724-4840-82c7-3313811788cd' to cn1, run::
For example, if you want to assign the undefined node whose uuid is ``fa2cec8a-b724-4840-82c7-3313811788cd`` to cn1, run::
#nodediscoverdef -u fa2cec8a-b724-4840-82c7-3313811788cd -n cn1
nodediscoverdef -u fa2cec8a-b724-4840-82c7-3313811788cd -n cn1
After manually defining it, the 'node name' and 'discovery method' attributes of the node will be changed. You can display the changed attributes using the nodediscoverls command::
After manually defining it, the 'node name' and 'discovery method' attributes of the node will be changed. You can display the changed attributes using the ``nodediscoverls`` command::
#nodediscoverls
UUID NODE METHOD MTM SERIAL

View File

@ -1,6 +1,7 @@
.. include:: ../../common/discover/mtms_discovery.rst
MTMS-based Discovery
====================
The idea of mtms based hardware discovery is that the admin know the physical location information of the server with specified MTMS. Then the admin can assign nodename, host ip address for the physical server.
MTMS is short for Machine Type/Model and Serial which is unique for a physical server. The idea of MTMS based hardware discovery is that the admin know the physical location information of the server with specified MTMS. Then the admin can assign nodename and host ip address for the physical server.
.. include:: schedule_environment.rst
.. include:: config_environment.rst
@ -12,7 +13,7 @@ After environment is ready, and the server is powered, we can start server disco
The following command can be used to discovery FSP/BMC within an IP range and write the discovered node definition into a stanza file::
# lsslp -s PBMC -u --range 50.0.100.1-100 -z > ./pbmc.stanza
lsslp -s PBMC -u --range 50.0.100.1-100 -z > ./pbmc.stanza
You need to modify the node definition in stanza file before using them, the stanza file will be like this::
@ -53,20 +54,20 @@ After the physical server is defined into xCATdb, the next thing is update the n
Then, add node info into /etc/hosts and DNS::
# makehosts cn1
# makedns -n
makehosts cn1
makedns -n
Start discovery process
-----------------------
To start discovery process, just need to power on the host remotely with the following command, and the discovery process will start automatically after the host is powered on::
#rpower cn1 on
rpower cn1 on
**[Optional]** If you'd like to monitor the discovery process, you can use::
#chdef cn1 cons=ipmi
#makeconsercf
#rcons cn1
chdef cn1 cons=ipmi
makeconsercf
rcons cn1
.. include:: standard_cn_definition.rst

View File

@ -5,7 +5,7 @@ After environment is ready, and the server is powered, we can start server disco
The following command can be used to discovery FSP/BMC within an IP range and write the discovered node definition into xCAT database::
# lsslp -s PBMC -u --range 50.0.100.1-100 -w
lsslp -s PBMC -u --range 50.0.100.1-100 -w
The discovered PBMC node will be like this::
@ -29,11 +29,10 @@ Start discovery process
To start discovery process, just need to power on the PBMC node remotely with the following command, and the discovery process will start automatically after the host is powered on::
#rpower Server-8247-22L-SN10112CA on
rpower Server-8247-22L-SN10112CA on
**[Optional]** If you'd like to monitor the discovery process, you can use::
#chdef Server-8247-22L-SN10112CA cons=ipmi
#makeconsercf
#rcons Server-8247-22L-SN10112CA
chdef Server-8247-22L-SN10112CA cons=ipmi
makeconsercf
rcons Server-8247-22L-SN10112CA

View File

@ -1,23 +1,21 @@
The environment scheduling
--------------------------
In this document, we use the following configuration as the example
In this document, the following configuration is used in the example
MN info::
Management Node info::
MN Hostname: xcat1
MN NIC info for Host network: eth1, 10.0.1.1/16
MN NIC info for FSP/BMC network: eth2, 50.0.1.1/16
MN NIC info for Management Network(Host network): eth1, 10.0.1.1/16
MN NIC info for Service Network(FSP/BMC nework): eth2, 50.0.1.1/16
Dynamic IP range for Hosts: 10.0.100.1-10.0.100.100
Dynamic IP range for FSP/BMC: 50.0.100.1-50.0.100.100
CN info::
Compute Node info::
CN Hostname: cn1
Machine type/model: 8247-22L
Serial: 10112CA
Host IP Address: 10.0.101.1
Host Root Password: cluster
IP Address: 10.0.101.1
Root Password: cluster
Desired FSP/BMC IP Address: 50.0.101.1
DHCP assigned FSP/BMC IP Address: 50.0.100.1
FSP/BMC username: ADMIN

View File

@ -15,15 +15,15 @@ Predefine nodes
Predefine a group of node with desired IP address for host and IP address for FSP/BMC::
#nodeadd cn1 groups=pkvm,all
#chdef cn1 mgt=ipmi cons=ipmi ip=10.0.101.1 bmc=50.0.101.1 netboot=petitboot installnic=mac primarynic=mac
nodeadd cn1 groups=powerLE,all
chdef cn1 mgt=ipmi cons=ipmi ip=10.0.101.1 bmc=50.0.101.1 netboot=petitboot installnic=mac primarynic=mac
Initialize the discovery process
````````````````````````````````
Specify the predefined nodes to the nodediscoverstart command to initialize the discovery process::
#nodediscoverstart noderange=cn1
nodediscoverstart noderange=cn1
Pls see "nodediscoverstart man page<TBD>" for more details.

View File

@ -1,16 +1,16 @@
The discovered node definition
------------------------------
Verify node definition
----------------------
The server node definition will be like this after hardware discovery process::
The following is an example of the server node definition after hardware discovery::
#lsdef cn1
# lsdef cn1
Object name: cn1
arch=ppc64
bmc=50.0.100.1
cons=ipmi
cpucount=192
cputype=POWER8E (raw), altivec supported
groups=pkvm,all
groups=powerLE,all
installnic=mac
ip=10.0.101.1
mac=6c:ae:8b:02:12:50

View File

@ -2,18 +2,7 @@
For switch based hardware discovery, the server are identified though the switches and switchposts they directly connect to.
The environment scheduling
--------------------------
In this document, we use the following configuration as the example
MN info::
MN Hostname: xcat1
MN NIC info for Host network: eth1, 10.0.1.1/16
MN NIC info for FSP/BMC network: eth2, 50.0.1.1/16
Dynamic IP range for Hosts: 10.0.100.1-10.0.100.100
Dynamic IP range for FSP/BMC: 50.0.100.1-50.0.100.100
.. include:: schedule_environment.rst
Switch info::
@ -21,65 +10,60 @@ Switch info::
Switch username: xcat
Switch password: passw0rd
Switch IP Address: 10.0.201.1
CN info::
CN Hostname: cn1
Machine type/model: 8247-22L
Serial: 10112CA
Host IP Address: 10.0.101.1
Host Root Password: cluster
Desired FSP/BMC IP Address: 50.0.101.1
DHCP assigned FSP/BMC IP Address: 50.0.100.1
FSP/BMC username: ADMIN
FSP/BMC Password: admin
Switch info: switch1, port0
Switch port for Compute Node: port0
.. include:: config_environment.rst
Predefine Nodes
Predefined Nodes
---------------
In order to differentiate a node from the other, the admin need to predefine node in xCAT database based on the switches information. So, 2 parts included.
In order to differentiate one node from another, the admin needs to predefine node in xCAT database based on the switches information. This consists of two parts:
#. :ref:`predefined_switches_label`
#. :ref:`predefined_server_nodes_label`
.. _predefined_switches_label:
Predefine Switches
``````````````````
The predefined switches will represent devices that the physical servers are connected to. xCAT need to access those switches to get server related information through SNMP v3.
So the admin need to make sure those switches are configured correctly with SNMP v3 enabled. <TD: The document that Configure Ethernet Switches>
So the admin need to make sure those switches are configured correctly with SNMP v3 enabled. <TODO: The document that Configure Ethernet Switches>
Then, define switch info into xCAT::
#nodeadd switch1 groups=switch,all
#chdef switch1 ip=10.0.201.1
#tabch switch=switch1 switches.snmpversion=3 switches.username=xcat switches.password=passw0rd switches.auth=sha
nodeadd switch1 groups=switch,all
chdef switch1 ip=10.0.201.1
tabch switch=switch1 switches.snmpversion=3 switches.username=xcat switches.password=passw0rd switches.auth=sha
After that, add switch into DNS::
Add switch into DNS using the following commands::
#makehosts switch1
#makedns -n
makehosts switch1
makedns -n
.. _predefined_server_nodes_label:
Predefine Server node
`````````````````````
After switches are defined, the server node can be predefined as network scheduled::
After switches are defined, the server node can be predefined with the following commands::
#nodeadd cn1 groups=pkvm,all
#chdef cn1 mgt=ipmi cons=ipmi ip=10.0.101.1 bmc=50.0.101.1 netboot=petitboot installnic=mac primarynic=mac
#chdef cn1 switch=switch1 switchport=0
nodeadd cn1 groups=powerLE,all
chdef cn1 mgt=ipmi cons=ipmi ip=10.0.101.1 bmc=50.0.101.1 netboot=petitboot installnic=mac primarynic=mac
chdef cn1 switch=switch1 switchport=0
Add cn1 into DNS::
#makehosts cn1
#maekdns -n
makehosts cn1
maekdns -n
.. include:: pbmc_discovery.rst
The discovered node definition
------------------------------
Verify node definition
----------------------
The following is an example of the server node definition after hardware discovery::
The server node definition will be like this after hardware discovery process::
#lsdef cn1
Object name: cn1
@ -88,7 +72,7 @@ The server node definition will be like this after hardware discovery process::
cons=ipmi
cpucount=192
cputype=POWER8E (raw), altivec supported
groups=pkvm,all
groups=powerLE,all
installnic=mac
ip=10.0.101.1
mac=6c:ae:8b:02:12:50