From d1ba70da2bed0c890b6fc33989cfd466dae792a2 Mon Sep 17 00:00:00 2001 From: ertaozh Date: Tue, 1 Sep 2015 23:24:09 -0400 Subject: [PATCH 1/3] p8le hardware discovery document --- .../ppc64le/discovery/config_environment.rst | 76 +++++++++++++ .../ppc64le/discovery/index.rst | 2 + .../ppc64le/discovery/manually_define.rst | 35 ++++++ .../ppc64le/discovery/manually_discovery.rst | 26 +++++ .../ppc64le/discovery/mtms_discovery.rst | 70 ++++++++++++ .../ppc64le/discovery/pbmc_discovery.rst | 39 +++++++ .../discovery/schedule_environment.rst | 24 ++++ .../ppc64le/discovery/seq_discovery.rst | 50 +++++++++ .../discovery/standard_cn_definition.rst | 25 +++++ .../ppc64le/discovery/switch_discovery.rst | 104 ++++++++++++++++++ 10 files changed, 451 insertions(+) create mode 100644 docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst create mode 100644 docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst create mode 100644 docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst create mode 100644 docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst new file mode 100644 index 000000000..6e2e6d43c --- /dev/null +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst @@ -0,0 +1,76 @@ +Configure xCAT +-------------- + +configure network table +^^^^^^^^^^^^^^^^^^^^^^^ + + +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_1_0_0-255_255_0_0","10.1.0.0","255.255.0.0","eth1","",,"10.1.1.1",,,,,,,,,,,, + "10_2_0_0-255_255_0_0","10.2.0.0","255.255.0.0","eth2","",,"10.2.1.1",,,,,,,,,,,, + +Pls run the following command to add networks in "networks" table if no entry in "networks" table:: + + #makenetworks + +setup DHCP +^^^^^^^^^^ + +Set the correct NIC from which DHCP server provide service:: + +#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_1_0_0-255_255_0_0 dynamicrange="10.1.100.1-10.1.100.100" +#chdef -t network 10_2_0_0-255_255_0_0 dynamicrange="10.2.100.1-10.2.100.100" + +Update DHCP configuration file:: + +#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 + +Run makedns to get the hostname/IP pairs copied from /etc/hosts to the DNS on the MN:: + +#makedns -n + +Config passwd table +^^^^^^^^^^^^^^^^^^^ + +To configure default password for FSP/BMCs and Hosts:: + + #tabedit passwd + #key,username,password,cryptmethod,authdomain,comments,disable + "system","root","cluster",,,, + "ipmi","ADMIN","admin",,,, + +Check the genesis pkg +^^^^^^^^^^^^^^^^^^^^^ + +Genesis pkg can be used to creates a network boot root image, it must be installed before do hardware discovery. + +``RH``:: + + # rpm -qa |grep -i genesis + xCAT-genesis-scripts-ppc64-2.10-snap201507240527.noarch + xCAT-genesis-base-ppc64-2.10-snap201505172314.noarch + +``ubuntu``:: + + # dpkg -l | grep genesis + 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 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst index 37f3fe278..3feeb7777 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst @@ -1,6 +1,8 @@ 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. + .. toctree:: :maxdepth: 2 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst index c0b822a66..e89d1b036 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst @@ -1 +1,36 @@ .. include:: ../../common/discover/manually_define.rst + +Manually define node means the admin know detailed information of the physical server. Then define it into xCAT database with commands. + +.. include:: schedule_environment.rst + +Manually define node +-------------------- + +To add a node object:: + + #nodeadd cn1 groups=pkvm,all + +To change node attributes:: + + #chdef cn1 mgt=ipmi cons=ipmi ip=10.1.101.1 netboot=petitboot + #chdef cn1 bmc=10.2.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:: + + # lsdef cn1 + Object name: cn1 + bmc=10.2.101.1 + bmcpassword=admin + bmcusername=ADMIN + cons=ipmi + groups=pkvm,all + installnic=mac + ip=10.1.101.1 + mac=6c:ae:8b:6a:d4:e4 + mgt=ipmi + netboot=petitboot + postbootscripts=otherpkgs + postscripts=syslog,remoteshell,syncfiles + primarynic=mac diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst index f36c7d7fe..a5e7207a7 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst @@ -1 +1,27 @@ .. 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. + +Display the undefined nodes with the nodediscoverls command:: + + #nodediscoverls -t undef + UUID NODE METHOD MTM SERIAL + fa2cec8a-b724-4840-82c7-3313811788cd undef undef 8247-22L 10112CA + +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:: + + #nodeadd cn1 groups=pkvm,all + #chdef cn1 mgt=ipmi cons=ipmi ip=10.1.101.1 bmc=10.2.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:: + + #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:: + + #nodediscoverls + UUID NODE METHOD MTM SERIAL + fa2cec8a-b724-4840-82c7-3313811788cd cn1 manual 8247-22L 10112CA + diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst index 88eb9606f..2c2ab2637 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst @@ -1 +1,71 @@ .. include:: ../../common/discover/mtms_discovery.rst + +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. + +.. include:: schedule_environment.rst +.. include:: config_environment.rst + +Discover server and define +-------------------------- + +After environment is ready, and the server is powered, we can start server discovery process. The first thing to do is discovering the FSP/BMC of the server. It is automatically powered on when the physical server is powered. + +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 10.2.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:: + + # cat pbmc.stanza + cn1: + objtype=node + bmc=10.2.100.1 + nodetype=mp + mtm=8247-42L + serial=10112CA + groups=pbmc,all + mgt=ipmi + hidden=0 + +Then, define it into xCATdb:: + + # cat pbmc.stanza | mkdef -z + 1 object definitions have been created or modified. + +The server definition will be like this:: + + # lsdef cn1 + Object name: cn1 + bmc=10.2.100.1 + groups=pbmc,all + hidden=0 + mgt=ipmi + mtm=8247-42L + nodetype=mp + postbootscripts=otherpkgs + postscripts=syslog,remoteshell,syncfiles + serial=10112CA + +After the physical server is defined into xCATdb, the next thing is update the node definition with the scheduled node info like this:: + + # chdef cn1 ip=10.1.101.1 cons=ipmi + 1 object definitions have been created or modified. + +Then, add node info into /etc/hosts and DNS:: + + # 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 + +**[Optional]** If you'd like to monitor the discovery process, you can use:: + + #makeconsercf + #rcons cn1 + +.. include:: standard_cn_definition.rst diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst new file mode 100644 index 000000000..48dcd52a6 --- /dev/null +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst @@ -0,0 +1,39 @@ +Discover server and define +-------------------------- + +After environment is ready, and the server is powered, we can start server discovery process. The first thing to do is discovering the FSP/BMC of the server. It is automatically powered on when the physical server is powered. + +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 10.2.100.1-100 -w + +The discovered PBMC node will be like this:: + + # lsdef Server-8247-22L-SN01112CA + Object name: Server-8247-22L-SN01112CA + bmc=10.2.100.1 + groups=pbmc,all + hidden=0 + hwtype=pbmc + mgt=ipmi + mtm=8247-22L + nodetype=mp + postbootscripts=otherpkgs + postscripts=syslog,remoteshell,syncfiles + serial=10112CA + +**Note**: Pls note that the PBMC node is just used to control the physical during hardware discovery process, it will be deleted after the correct server node object is found. + +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-SN01112CA on + +**[Optional]** If you'd like to monitor the discovery process, you can use:: + + #chdef Server-8247-22L-SN01112CA cons=ipmi + #makeconsercf + #rcons Server-8247-22L-SN01112CA + diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst new file mode 100644 index 000000000..a2f5497f1 --- /dev/null +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst @@ -0,0 +1,24 @@ +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.1.1.1/16 + MN NIC info for FSP/BMC network: eth2, 10.2.1.1/16 + Dynamic IP range for Hosts: 10.1.100.1-10.1.100.100 + Dynamic IP range for FSP/BMC: 10.2.100.1-10.2.100.100 + +CN info:: + + CN Hostname: cn1 + Machine type/model: 8247-22L + Serial: 10112CA + Host IP Address: 10.1.101.1 + Host Root Password: cluster + Desired FSP/BMC IP Address: 10.2.101.1 + DHCP assigned FSP/BMC IP Address: 10.2.100.1 + FSP/BMC username: ADMIN + FSP/BMC Password: admin diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst index 91d65af17..988d3182b 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst @@ -1 +1,51 @@ .. include:: ../../common/discover/seq_discovery.rst + +When the physical location of the server is not so important, sequential base hardware discovery can be used to simplify the discovery work. The idea is: providing a node pool, each node in the pool will be assigned an IP address for host and an IP address for FSP/BMC, then match first came physical server discovery request to the first free node in the node pool and configure the assigned IP address for host and FSP/BMC onto that pysical server. + +.. include:: schedule_environment.rst +.. include:: config_environment.rst + +Prepare node pool +----------------- + +To prepare the node pool, shall predefine nodes first, then initialize the discovery process with the predefined nodes. + +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.1.101.1 bmc=10.2.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 + +Pls see "nodediscoverstart man page" for more details. + +Display information about the discovery process +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +There are additional nodediscover commands you can run during the discovery process. See their man pages for more details. + + +Verify the status of discovery:: + + nodediscoverstatus + +Show the nodes that have been discovered so far:: + + nodediscoverls -t seq -l + +Stop the current sequential discovery process:: + + nodediscoverstop + +Note: The sequential discovery process will be stopped automatically when all of the node names in the node pool are used up. + +.. include:: pbmc_discovery.rst +.. include:: standard_cn_definition.rst diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst new file mode 100644 index 000000000..365285d36 --- /dev/null +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst @@ -0,0 +1,25 @@ +The discovered node definition +------------------------------ + +The server node definition will be like this after hardware discovery process:: + + #lsdef cn1 + Object name: cn1 + arch=ppc64 + bmc=10.2.100.1 + cons=ipmi + cpucount=192 + cputype=POWER8E (raw), altivec supported + groups=pkvm,all + installnic=mac + ip=10.1.101.1 + mac=6c:ae:8b:02:12:50 + memory=65118MB + mgt=ipmi + mtm=8247-22L + netboot=petitboot + postbootscripts=otherpkgs + postscripts=syslog,remoteshell,syncfiles + primarynic=mac + serial=10112CA + supportedarchs=ppc64 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst index 0b83eca00..a7a4f21f7 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst @@ -1 +1,105 @@ .. include:: ../../common/discover/switch_discovery.rst + +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.1.1.1/16 + MN NIC info for FSP/BMC network: eth2, 10.2.1.1/16 + Dynamic IP range for Hosts: 10.1.100.1-10.1.100.100 + Dynamic IP range for FSP/BMC: 10.2.100.1-10.2.100.100 + +Switch info:: + + Switch name: switch1 + Switch username: xcat + Switch password: passw0rd + Switch IP Address: 10.1.201.1 + +CN info:: + + CN Hostname: cn1 + Machine type/model: 8247-22L + Serial: 10112CA + Host IP Address: 10.1.101.1 + Host Root Password: cluster + Desired FSP/BMC IP Address: 10.2.101.1 + DHCP assigned FSP/BMC IP Address: 10.2.100.1 + FSP/BMC username: ADMIN + FSP/BMC Password: admin + Switch info: switch1, port0 + +.. include:: config_environment.rst + +Predefine 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. + +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. + +Then, define switch info into xCAT:: + + #nodeadd switch1 groups=switch,all + #chdef switch1 ip=10.1.201.1 + #tabch switch=switch1 switches.snmpversion=3 switches.username=xcat switches.password=passw0rd switches.auth=sha + +After that, add switch into DNS:: + + #makehosts switch1 + #makedns -n + +Predefine Server node +^^^^^^^^^^^^^^^^^^^^^ + +After switches are defined, the server node can be predefined as network scheduled:: + + #nodeadd cn1 groups=pkvm,all + #chdef cn1 mgt=ipmi cons=ipmi ip=10.1.101.1 bmc=10.2.101.1 netboot=petitboot installnic=mac primarynic=mac + #chdef cn1 switch=switch1 switchport=0 + +Add cn1 into DNS:: + + #makehosts cn1 + #maekdns -n + +.. include:: pbmc_discovery.rst + +The discovered node definition +------------------------------ + +The server node definition will be like this after hardware discovery process:: + + #lsdef cn1 + Object name: cn1 + arch=ppc64 + bmc=10.2.101.1 + cons=ipmi + cpucount=192 + cputype=POWER8E (raw), altivec supported + groups=pkvm,all + installnic=mac + ip=10.1.101.1 + mac=6c:ae:8b:02:12:50 + memory=65118MB + mgt=ipmi + mtm=8247-22L + netboot=petitboot + postbootscripts=otherpkgs + postscripts=syslog,remoteshell,syncfiles + primarynic=mac + serial=10112CA + supportedarchs=ppc64 + switch=switch1 + switchport=0 From fe88d403f3bf0d6da1dcd0d4fc60d17f037c8e8d Mon Sep 17 00:00:00 2001 From: ertaozh Date: Fri, 11 Sep 2015 04:02:07 -0400 Subject: [PATCH 2/3] update title format, node and BMC/FSP ip address format --- .../ppc64le/discovery/config_environment.rst | 34 +++++++++---------- .../ppc64le/discovery/manually_define.rst | 8 ++--- .../ppc64le/discovery/manually_discovery.rst | 2 +- .../ppc64le/discovery/mtms_discovery.rst | 23 +++++++------ .../ppc64le/discovery/pbmc_discovery.rst | 14 ++++---- .../discovery/schedule_environment.rst | 14 ++++---- .../ppc64le/discovery/seq_discovery.rst | 8 ++--- .../discovery/standard_cn_definition.rst | 4 +-- .../ppc64le/discovery/switch_discovery.rst | 28 +++++++-------- 9 files changed, 68 insertions(+), 67 deletions(-) diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst index 6e2e6d43c..ccf99323f 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst @@ -2,22 +2,22 @@ Configure xCAT -------------- configure network table -^^^^^^^^^^^^^^^^^^^^^^^ +``````````````````````` 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_1_0_0-255_255_0_0","10.1.0.0","255.255.0.0","eth1","",,"10.1.1.1",,,,,,,,,,,, - "10_2_0_0-255_255_0_0","10.2.0.0","255.255.0.0","eth2","",,"10.2.1.1",,,,,,,,,,,, + "10_0_0_0-255_255_0_0","10.0.0.0","255.255.0.0","eth1","",,"10.0.1.1",,,,,,,,,,,, + "50_0_0_0-255_255_0_0","50.0.0.0","255.255.0.0","eth2","",,"50.0.1.1",,,,,,,,,,,, Pls run the following command to add networks in "networks" table if no entry in "networks" table:: #makenetworks setup DHCP -^^^^^^^^^^ +`````````` Set the correct NIC from which DHCP server provide service:: @@ -25,8 +25,8 @@ Set the correct NIC from which DHCP server provide service:: Add dynamic range in purpose of assigning temporary IP adddress for FSP/BMCs and hosts:: -#chdef -t network 10_1_0_0-255_255_0_0 dynamicrange="10.1.100.1-10.1.100.100" -#chdef -t network 10_2_0_0-255_255_0_0 dynamicrange="10.2.100.1-10.2.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:: @@ -34,7 +34,7 @@ Update DHCP configuration file:: #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:: @@ -45,7 +45,7 @@ Run makedns to get the hostname/IP pairs copied from /etc/hosts to the DNS on th #makedns -n Config passwd table -^^^^^^^^^^^^^^^^^^^ +``````````````````` To configure default password for FSP/BMCs and Hosts:: @@ -55,21 +55,21 @@ To configure default password for FSP/BMCs and Hosts:: "ipmi","ADMIN","admin",,,, Check the genesis pkg -^^^^^^^^^^^^^^^^^^^^^ +````````````````````` Genesis pkg can be used to creates a network boot root image, it must be installed before do hardware discovery. -``RH``:: +* **[RH]**:: - # rpm -qa |grep -i genesis - xCAT-genesis-scripts-ppc64-2.10-snap201507240527.noarch - xCAT-genesis-base-ppc64-2.10-snap201505172314.noarch + # rpm -qa |grep -i genesis + xCAT-genesis-scripts-ppc64-2.10-snap201507240527.noarch + xCAT-genesis-base-ppc64-2.10-snap201505172314.noarch -``ubuntu``:: +* **[ubuntu]**:: - # dpkg -l | grep genesis - ii xcat-genesis-base-ppc64 2.10-snap201505172314 all xCAT Genesis netboot image - ii xcat-genesis-scripts 2.10-snap201507240105 ppc64el xCAT genesis + # dpkg -l | grep genesis + 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:: diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst index e89d1b036..df2a89580 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst @@ -13,21 +13,21 @@ To add a node object:: To change node attributes:: - #chdef cn1 mgt=ipmi cons=ipmi ip=10.1.101.1 netboot=petitboot - #chdef cn1 bmc=10.2.101.1 bmcusername=ADMIN bmcpassword=admin + #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:: # lsdef cn1 Object name: cn1 - bmc=10.2.101.1 + bmc=50.0.101.1 bmcpassword=admin bmcusername=ADMIN cons=ipmi groups=pkvm,all installnic=mac - ip=10.1.101.1 + ip=10.0.101.1 mac=6c:ae:8b:6a:d4:e4 mgt=ipmi netboot=petitboot diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst index a5e7207a7..025473d7d 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst @@ -13,7 +13,7 @@ If you want to manually define an 'undefined' node to a specific free node name, Before doing that, a node with desired IP address for hsot and FSP/BMC shall be defined first:: #nodeadd cn1 groups=pkvm,all - #chdef cn1 mgt=ipmi cons=ipmi ip=10.1.101.1 bmc=10.2.101.1 netboot=petitboot installnic=mac primarynic=mac + #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:: diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst index 2c2ab2637..1af52de02 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst @@ -12,20 +12,20 @@ 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 10.2.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:: # cat pbmc.stanza cn1: - objtype=node - bmc=10.2.100.1 - nodetype=mp - mtm=8247-42L - serial=10112CA - groups=pbmc,all - mgt=ipmi - hidden=0 + objtype=node + bmc=50.0.100.1 + nodetype=mp + mtm=8247-42L + serial=10112CA + groups=pbmc,all + mgt=ipmi + hidden=0 Then, define it into xCATdb:: @@ -36,7 +36,7 @@ The server definition will be like this:: # lsdef cn1 Object name: cn1 - bmc=10.2.100.1 + bmc=50.0.100.1 groups=pbmc,all hidden=0 mgt=ipmi @@ -48,7 +48,7 @@ The server definition will be like this:: After the physical server is defined into xCATdb, the next thing is update the node definition with the scheduled node info like this:: - # chdef cn1 ip=10.1.101.1 cons=ipmi + # chdef cn1 ip=10.0.101.1 1 object definitions have been created or modified. Then, add node info into /etc/hosts and DNS:: @@ -65,6 +65,7 @@ To start discovery process, just need to power on the host remotely with the fol **[Optional]** If you'd like to monitor the discovery process, you can use:: + #chdef cn1 cons=ipmi #makeconsercf #rcons cn1 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst index 48dcd52a6..2e3df1fd3 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst @@ -5,13 +5,13 @@ 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 10.2.100.1-100 -w +# lsslp -s PBMC -u --range 50.0.100.1-100 -w The discovered PBMC node will be like this:: - # lsdef Server-8247-22L-SN01112CA - Object name: Server-8247-22L-SN01112CA - bmc=10.2.100.1 + # lsdef Server-8247-22L-SN10112CA + Object name: Server-8247-22L-SN10112CA + bmc=50.0.100.1 groups=pbmc,all hidden=0 hwtype=pbmc @@ -29,11 +29,11 @@ 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-SN01112CA on +#rpower Server-8247-22L-SN10112CA on **[Optional]** If you'd like to monitor the discovery process, you can use:: - #chdef Server-8247-22L-SN01112CA cons=ipmi + #chdef Server-8247-22L-SN10112CA cons=ipmi #makeconsercf - #rcons Server-8247-22L-SN01112CA + #rcons Server-8247-22L-SN10112CA diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst index a2f5497f1..186313f82 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst @@ -6,19 +6,19 @@ In this document, we use the following configuration as the example MN info:: MN Hostname: xcat1 - MN NIC info for Host network: eth1, 10.1.1.1/16 - MN NIC info for FSP/BMC network: eth2, 10.2.1.1/16 - Dynamic IP range for Hosts: 10.1.100.1-10.1.100.100 - Dynamic IP range for FSP/BMC: 10.2.100.1-10.2.100.100 + 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 CN info:: CN Hostname: cn1 Machine type/model: 8247-22L Serial: 10112CA - Host IP Address: 10.1.101.1 + Host IP Address: 10.0.101.1 Host Root Password: cluster - Desired FSP/BMC IP Address: 10.2.101.1 - DHCP assigned FSP/BMC IP Address: 10.2.100.1 + 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 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst index 988d3182b..ebeb29fbc 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst @@ -11,15 +11,15 @@ Prepare node pool To prepare the node pool, shall predefine nodes first, then initialize the discovery process with the predefined nodes. 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.1.101.1 bmc=10.2.101.1 netboot=petitboot installnic=mac primarynic=mac + #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:: @@ -28,7 +28,7 @@ Specify the predefined nodes to the nodediscoverstart command to initialize the Pls see "nodediscoverstart man page" for more details. Display information about the discovery process -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +``````````````````````````````````````````````` There are additional nodediscover commands you can run during the discovery process. See their man pages for more details. diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst index 365285d36..1329b1e36 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst @@ -6,13 +6,13 @@ The server node definition will be like this after hardware discovery process:: #lsdef cn1 Object name: cn1 arch=ppc64 - bmc=10.2.100.1 + bmc=50.0.100.1 cons=ipmi cpucount=192 cputype=POWER8E (raw), altivec supported groups=pkvm,all installnic=mac - ip=10.1.101.1 + ip=10.0.101.1 mac=6c:ae:8b:02:12:50 memory=65118MB mgt=ipmi diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst index a7a4f21f7..889467e99 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst @@ -10,27 +10,27 @@ In this document, we use the following configuration as the example MN info:: MN Hostname: xcat1 - MN NIC info for Host network: eth1, 10.1.1.1/16 - MN NIC info for FSP/BMC network: eth2, 10.2.1.1/16 - Dynamic IP range for Hosts: 10.1.100.1-10.1.100.100 - Dynamic IP range for FSP/BMC: 10.2.100.1-10.2.100.100 + 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 Switch info:: Switch name: switch1 Switch username: xcat Switch password: passw0rd - Switch IP Address: 10.1.201.1 + Switch IP Address: 10.0.201.1 CN info:: CN Hostname: cn1 Machine type/model: 8247-22L Serial: 10112CA - Host IP Address: 10.1.101.1 + Host IP Address: 10.0.101.1 Host Root Password: cluster - Desired FSP/BMC IP Address: 10.2.101.1 - DHCP assigned FSP/BMC IP Address: 10.2.100.1 + 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 @@ -43,7 +43,7 @@ Predefine 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. 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. @@ -52,7 +52,7 @@ So the admin need to make sure those switches are configured correctly with SNMP Then, define switch info into xCAT:: #nodeadd switch1 groups=switch,all - #chdef switch1 ip=10.1.201.1 + #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:: @@ -61,12 +61,12 @@ After that, add switch into DNS:: #makedns -n Predefine Server node -^^^^^^^^^^^^^^^^^^^^^ +````````````````````` After switches are defined, the server node can be predefined as network scheduled:: #nodeadd cn1 groups=pkvm,all - #chdef cn1 mgt=ipmi cons=ipmi ip=10.1.101.1 bmc=10.2.101.1 netboot=petitboot installnic=mac primarynic=mac + #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:: @@ -84,13 +84,13 @@ The server node definition will be like this after hardware discovery process:: #lsdef cn1 Object name: cn1 arch=ppc64 - bmc=10.2.101.1 + bmc=50.0.101.1 cons=ipmi cpucount=192 cputype=POWER8E (raw), altivec supported groups=pkvm,all installnic=mac - ip=10.1.101.1 + ip=10.0.101.1 mac=6c:ae:8b:02:12:50 memory=65118MB mgt=ipmi From 60de48e1d6d9f437af620ae9ccdf8ec45ad0b0b8 Mon Sep 17 00:00:00 2001 From: ertaozh Date: Wed, 16 Sep 2015 10:57:57 -0400 Subject: [PATCH 3/3] enhancement for hdwr_discovery doc --- .../common/discover/manually_define.rst | 2 - .../common/discover/mtms_discovery.rst | 2 - .../ppc64le/discovery/config_environment.rst | 46 ++++++----- .../ppc64le/discovery/index.rst | 2 +- .../ppc64le/discovery/manually_define.rst | 17 +++-- .../ppc64le/discovery/manually_discovery.rst | 16 ++-- .../ppc64le/discovery/mtms_discovery.rst | 19 ++--- .../ppc64le/discovery/pbmc_discovery.rst | 11 ++- .../discovery/schedule_environment.rst | 16 ++-- .../ppc64le/discovery/seq_discovery.rst | 6 +- .../discovery/standard_cn_definition.rst | 10 +-- .../ppc64le/discovery/switch_discovery.rst | 76 ++++++++----------- 12 files changed, 103 insertions(+), 120 deletions(-) delete mode 100644 docs/source/guides/admin-guides/manage_clusters/common/discover/manually_define.rst delete mode 100644 docs/source/guides/admin-guides/manage_clusters/common/discover/mtms_discovery.rst diff --git a/docs/source/guides/admin-guides/manage_clusters/common/discover/manually_define.rst b/docs/source/guides/admin-guides/manage_clusters/common/discover/manually_define.rst deleted file mode 100644 index 8d70d1942..000000000 --- a/docs/source/guides/admin-guides/manage_clusters/common/discover/manually_define.rst +++ /dev/null @@ -1,2 +0,0 @@ -Manually Define Nodes -===================== diff --git a/docs/source/guides/admin-guides/manage_clusters/common/discover/mtms_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/common/discover/mtms_discovery.rst deleted file mode 100644 index 9239eb9e7..000000000 --- a/docs/source/guides/admin-guides/manage_clusters/common/discover/mtms_discovery.rst +++ /dev/null @@ -1,2 +0,0 @@ -MTMS-based Discovery -==================== diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst index ccf99323f..8034595cb 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/config_environment.rst @@ -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","",,"10.0.1.1",,,,,,,,,,,, "50_0_0_0-255_255_0_0","50.0.0.0","255.255.0.0","eth2","",,"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. diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst index 3feeb7777..f5698ebaf 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst @@ -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 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst index df2a89580..531805dd6 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_define.rst @@ -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 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst index 025473d7d..e29d77069 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/manually_discovery.rst @@ -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 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst index 1af52de02..68e907ee0 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms_discovery.rst @@ -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 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst index 2e3df1fd3..65d2f63af 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/pbmc_discovery.rst @@ -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 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst index 186313f82..a1a0eb8f6 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/schedule_environment.rst @@ -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 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst index ebeb29fbc..f87ee1df0 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst @@ -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" for more details. diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst index 1329b1e36..6230e8488 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/standard_cn_definition.rst @@ -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 diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst index 889467e99..6c972df7b 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst @@ -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. +So the admin need to make sure those switches are configured correctly with SNMP v3 enabled. 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