Recent changes to XCAT_iDataPlex_Advanced_Setup

XCAT_iDataPlex_Advanced_Setup modified by XiaoPeng Wang

XiaoPeng Wang — Tue, 19 May 2015 05:00:25 -0000

--- v147
+++ v148
@@ -131,20 +131,20 @@

 During nodeset your request is put into the **currstate** attribute. The **chain** attribute is not used. The task in the **currstate** attribute will be passed to genesis and executed. If additional tasks are defined in the **currchain** attribute, these tasks will be run after the tasks in the **currstate** attribute are run.

-## Configure Raid Arraies 
-In many modern new compute machines, the disks in the machines have been formatted to RAID oriented format that you must create raid array for the disks manually before using them. Then how to configure raid unattendedly for hundreds of machines turns to be a problem. In xCAT, you can use the 'runimage' facility which introduced in the previous section to configure raid in the hardware discovery procedure or with separated manual steps.
-
-Following example shows how to use '''runimage''' facility to create raid0 array for each disk on a Power OPAL machine. You can customize the '''runme.sh' script to achieve your requirement. For the x86 machine, you can workout a similar runme.sh script for the corresponding machine.
-
-IBM has offerred the tool '''iprconfig' for raid configuratioin in IBM power machine. To leverage this tool, xCAT enabled it in xCAT genesis.ppc64 so that you admin can use genesis.ppc64 to configure raid.
-
-'''runimage''' is a facility which running in genesis to copy and run an image from xCAT management node. We add the code that configure raid into 'runme.sh', then execute the 'runimage' will perform the raid configuration steps which we added in 'runme.sh'.
+## Configure Raid Arrays 
+In many new compute machines, the disks in the machines have been formatted to RAID oriented format in manufactory that admin must create raid array for the disks manually before using them. Then how to configure raid in unattended way for hundreds of machines turns to be a problem. In xCAT, you can use the **runimage** facility which introduced in the previous section to configure raid in the hardware discovery procedure or with separated manual steps.
+
+Following example shows how to use **runimage** facility manually to create raid0 array for each disk in a Power OPAL machine. You can customize the **runme.sh** script to achieve your real requirement. For the x86 machine, you can workout a similar runme.sh script for your corresponding case.
+
+IBM has offered a tool **iprconfig** to configure raid for IBM power machine. To leverage this tool, xCAT enabled it in xCAT genesis.ppc64 so that admin can use genesis.ppc64 to configure raid.
+
+**runimage** is a facility which will be run in genesis to copy and run an image from xCAT management node. We add the code logic that configure raid into 'runme.sh', then leverage the 'runimage' mechanism to perform the raid configuration flow which we added in 'runme.sh'.

 ### Steps to Set Up Runimage 
 ~~~~
 mkdir -p /install/runimage
 cd /install/runimage
-edit ./runme.sh with following example script
+edit ./runme.sh with your raid configuration script
 chmod 755 runme.sh
 tar cvf setupipr.tar .
 nodeset <node> runimage=http://<MN IP="">/install/runimage/setupipr.tar,shell
@@ -152,7 +152,7 @@
 rpower <node> on
 ~~~~

-### The Example of runme.sh for ipr Raid Setup
+### The Example of runme.sh for IBM Power Raid Setup
 This example script will find out all disks, then format them to raid-oriented format and create raid0 array for each disk.

 ~~~~
@@ -164,9 +164,10 @@

 # Format all the jbod disk to 'Advanced Function' format
 for disk in $jbod_disks; do
-    echo "Format disk [$disk] for Advanced Function to be ready for raid array creating."
-    `iprconfig -c format-for-raid $disk`
+    disklist="$disklist $disk"
 done
+echo "Format disk [$disklist] for Advanced Function to be ready for raid array creating."
+`iprconfig -c format-for-raid $disklist`

 # Get all available IOAs
 ioas=`iprconfig -c show-ioas | grep "^sg[0-9]\+.*Operational" | awk '{print $1}' | sort`
@@ -192,6 +193,31 @@

 ~~~~

+### Monitor the Raid Configuration Process
+The process to format disk to 'Advanced Function' (raid-oriented format) will cost tens of minutes or hours. During this period, you can use xCAT **xdsh** command to monitor the progress of raid configuration.
+
+The output of running **iprconfig** command to display the raid configuration for node p8le-42l. You can parse the output to automitcally minitor the process.
+
+~~~~
+#xdsh p8le-42l iprconfig -c show-config
+p8le-42l: Name   PCI/SCSI Location         Description               Status
+p8le-42l: ------ ------------------------- ------------------------- -----------------
+p8le-42l:        0001:08:00.0/0:            PCI-E SAS RAID Adapter    Operational
+p8le-42l:        0001:08:00.0/0:0:0:0       Advanced Function Disk    Active
+p8le-42l: sda    0001:08:00.0/0:0:12:0      Physical Disk             5% Formatted
+p8le-42l: sdb    0001:08:00.0/0:0:13:0      Physical Disk             5% Formatted
+p8le-42l: sdc    0001:08:00.0/0:0:14:0      Physical Disk             5% Formatted
+p8le-42l:        0001:08:00.0/0:0:1:0       Advanced Function Disk    Active
+p8le-42l:        0001:08:00.0/0:0:2:0       Advanced Function Disk    Active
+p8le-42l:        0001:08:00.0/0:0:3:0       Advanced Function Disk    Active
+p8le-42l:        0001:08:00.0/0:0:4:0       Advanced Function Disk    Active
+p8le-42l:        0001:08:00.0/0:0:5:0       Advanced Function Disk    Active
+p8le-42l:        0001:08:00.0/0:0:6:0       Advanced Function Disk    Active
+p8le-42l:        0001:08:00.0/0:0:7:0       Advanced Function Disk    Active
+p8le-42l:        0001:08:00.0/0:0:8:0       Advanced Function Disk    Active
+p8le-42l:        0001:08:00.0/0:0:10:0      Enclosure                 Active
+p8le-42l:        0001:08:00.0/0:0:9:0       Enclosure                 Active
+~~~~

 ## Automatically Deploying Nodes After Discovery

XCAT_iDataPlex_Advanced_Setup modified by XiaoPeng Wang

XiaoPeng Wang — Mon, 18 May 2015 08:32:00 -0000

--- v146
+++ v147
@@ -63,17 +63,16 @@

 xCAT supports following types of task which could be set in the chain:

-~~~~
-
+#### runcmd
+~~~~
    runcmd=<cmd>
 ~~~~

 Currently only the 'bmcsetup' command is officially supplied by xCAT to run to configure the bmc of the compute node. You can find the 'bmcsetup' in /opt/xcat/share/xcat/netboot/genesis/x86_64/fs/bin/. You also could create your command in this directory and adding it to be run by 'runcmd=<you cmd>'.

-~~~~
-    runcmd=bmcsetup
-~~~~
-
+e.g.     runcmd=bmcsetup
+
+#### runimage
 ~~~~
    runimage=<URL>
 ~~~~
@@ -87,8 +86,8 @@

 The image.tgz should can be uncompressed by 'tar xvf image.tgz'. And image.tgz should include a file named 'runme.sh' which is a script to initiate the running of the image. Note: You could try to run 'wget http://$MASTER/image.tgz' manually to make sure the path has been set correctly.

-~~~~
-
+#### osimage
+~~~~
    osimage=<image name=""> or (install/netboot)
 ~~~~

@@ -99,11 +98,11 @@
 ~~~~

-  * shell
+#### shell

 Make the genesis gets into the shell for admin to log in and run command.

-  * standby
+#### standby

 Make the genesis gets into standby and waiting for the task from chain. If the compute node gets into this state, any new task set to chain.currstate will be run immediately.

@@ -131,6 +130,68 @@
 In this example, the runimage will be run first, and then the <rhels6.3-x86_64-install-compute> will be deployed to the node.

 During nodeset your request is put into the **currstate** attribute. The **chain** attribute is not used. The task in the **currstate** attribute will be passed to genesis and executed. If additional tasks are defined in the **currchain** attribute, these tasks will be run after the tasks in the **currstate** attribute are run.
+
+## Configure Raid Arraies 
+In many modern new compute machines, the disks in the machines have been formatted to RAID oriented format that you must create raid array for the disks manually before using them. Then how to configure raid unattendedly for hundreds of machines turns to be a problem. In xCAT, you can use the 'runimage' facility which introduced in the previous section to configure raid in the hardware discovery procedure or with separated manual steps.
+
+Following example shows how to use '''runimage''' facility to create raid0 array for each disk on a Power OPAL machine. You can customize the '''runme.sh' script to achieve your requirement. For the x86 machine, you can workout a similar runme.sh script for the corresponding machine.
+
+IBM has offerred the tool '''iprconfig' for raid configuratioin in IBM power machine. To leverage this tool, xCAT enabled it in xCAT genesis.ppc64 so that you admin can use genesis.ppc64 to configure raid.
+
+'''runimage''' is a facility which running in genesis to copy and run an image from xCAT management node. We add the code that configure raid into 'runme.sh', then execute the 'runimage' will perform the raid configuration steps which we added in 'runme.sh'.
+
+### Steps to Set Up Runimage 
+~~~~
+mkdir -p /install/runimage
+cd /install/runimage
+edit ./runme.sh with following example script
+chmod 755 runme.sh
+tar cvf setupipr.tar .
+nodeset <node> runimage=http://<MN IP="">/install/runimage/setupipr.tar,shell
+rsetboot <node> net
+rpower <node> on
+~~~~
+
+### The Example of runme.sh for ipr Raid Setup
+This example script will find out all disks, then format them to raid-oriented format and create raid0 array for each disk.
+
+~~~~
+#!/bin/bash
+# IBM(c) 2015 EPL license http://www.eclipse.org/legal/epl-v10.html
+
+# Get all disks which are formatted in JOBD functions
+jbod_disks=`iprconfig -c show-jbod-disks | grep "^sd[a-z]\+.*Active" | awk '{print $1}' | sort`
+
+# Format all the jbod disk to 'Advanced Function' format
+for disk in $jbod_disks; do
+    echo "Format disk [$disk] for Advanced Function to be ready for raid array creating."
+    `iprconfig -c format-for-raid $disk`
+done
+
+# Get all available IOAs
+ioas=`iprconfig -c show-ioas | grep "^sg[0-9]\+.*Operational" | awk '{print $1}' | sort`
+
+# Exit if there's no available IOA
+if [ -z "$ioas" ]; then
+    echo "Error: No available IOA found."
+    exit 0
+fi
+
+for ioa in $ioas; do
+    # Figure out all available disks for the IOA
+    disks=`iprconfig -c query-raid-create $ioa | grep "^sg[0-9]\+.*Active" | awk '{print $1}'`
+
+    # Create arraies:
+    # Create raid0 for each of active disks
+    for disk in $disks; do
+        # Create a raid 0 for each disk
+        echo "Create raid 0 array with device /dev/$disk."
+        `iprconfig -c raid-create -r 0 /dev/$disk >/dev/null`
+    done
+done
+
+~~~~
+

 ## Automatically Deploying Nodes After Discovery

@@ -898,4 +959,3 @@
 After the OS install:

   * Proceed to to setup the xCAT MN as a new xCAT MN using the instructions in this document.
-

XCAT_iDataPlex_Advanced_Setup modified by Ling

Ling — Fri, 17 Apr 2015 19:11:52 -0000

--- v145
+++ v146
@@ -451,7 +451,7 @@
     objcopy -R .note.module.sig module.ko new_module.ko
 ~~~~

-After this, replace the old module with the new one, rerun 'depmod' and 'mknb'
+After this, replace the old module with the new one, rerun 'depmod' and 'mknb'. In above Adaptec AACRAID driver example, you can do the following:

 ~~~~
     cd /opt/xcat/share/xcat/netboot/genesis/x86_64/fs/lib/modules/2.6.32-431.el6.x86_64/kernel/drivers/scsi/aacraid

XCAT_iDataPlex_Advanced_Setup modified by Ling

Ling — Fri, 17 Apr 2015 19:09:36 -0000

--- v144
+++ v145
@@ -442,6 +442,23 @@

   * Genesis is now ready to use for discovery. To use the new genesis for firmware updates or running other utilities on nodes, run nodeset for the nodes again.
+
+
+Note: 
+It's possible to see an error, "module signed with unknown key" either when running mknb or booting the newly rebuilt genesis kernel. If this happens, it is necessary to remove the signature from the kernel module:
+
+~~~~
+    objcopy -R .note.module.sig module.ko new_module.ko
+~~~~
+
+After this, replace the old module with the new one, rerun 'depmod' and 'mknb'
+
+~~~~
+    cd /opt/xcat/share/xcat/netboot/genesis/x86_64/fs/lib/modules/2.6.32-431.el6.x86_64/kernel/drivers/scsi/aacraid
+    objcopy -R .note.module.sig aacraid.ko new_ aacraid.ko
+    mv new_ aacraid.ko aacraid.ko
+~~~~
+

 ## **Configuring Secondary Adapters**

XCAT_iDataPlex_Advanced_Setup modified by Guang Cheng Li

Guang Cheng Li — Wed, 08 Oct 2014 07:17:10 -0000

--- v143
+++ v144
@@ -445,7 +445,7 @@

 ## **Configuring Secondary Adapters**

-To configure secondary adapters, see [Configuring_Secondary_Adapters].
+To configure secondary adapters, see [Configuring_Secondary_Adapters](Configuring_Secondary_Adapters).

 ## Build a Compressed Image

XCAT_iDataPlex_Advanced_Setup modified by

Thu, 28 Aug 2014 00:32:08 -0000

--- v142
+++ v143
@@ -527,6 +527,7 @@
 numcols=3;
 colwidths=20,30,20;
 -->
+
 | Booting Node | <-- Network Transfer --> | Management Node
 ---------------|--------------------------|-----------------
 | PXE ROM | DHCP request --> | DHCP server
@@ -573,6 +574,7 @@
 | /opt/xcat/xcatinstallpost | execute mypostscript.post in /xcatpost
 | mypostscript.post | execute postbootscripts in /xcatpost
 | updateflag.awk | update node status to booted --> | xCAT server
+
 
@@ -584,6 +586,7 @@
 numcols=3;
 colwidths=20,30,20;
 -->
+
 | Booting Node | Network Transfer | Management Node
 ---------------|------------------|-----------------
 | PXE ROM | DHCP request --> | DHCP server
@@ -621,6 +624,7 @@
 | /opt/xcat/xcatinstallpost | execute mypostscript.post in /xcatpost |
 | mypostscript.post | execute postbootscripts in /xcatpost |
 | updateflag.awk | update node status to booted --> | xCAT server
+
 
@@ -632,6 +636,7 @@
 numcols=3;
 colwidths=20,30,20;
 -->
+
 | Booting Node | Network Transfer | Management Node
 ---------------|------------------|-----------------
 | PXE ROM | DHCP request --> | DHCP server
@@ -659,6 +664,7 @@
 | xcatdsklspost | execute the postscripts |
 | xcatdsklspost | execute the post BOOT scripts |
 | xcatdsklspost | update node status --> | xCAT server
+
 
@@ -670,6 +676,7 @@
 numcols=3;
 colwidths=20,30,20;
 -->
+
 | Booting Node | Network Transfer | Management Node
 ---------------|------------------|-----------------
 | PXE ROM | DHCP request --> | DHCP server
@@ -695,6 +702,7 @@
 | installer postscripts | execute the postscripts <--> | xCAT server
 | installer postscripts | execute the post BOOT scripts <--> | xCAT server
 | | update node status --> | xCAT server
+
 
@@ -708,6 +716,7 @@
 numcols=3;
 colwidths=20,30,20;
 -->
+
 | Booting Node | Network Transfer | Management Node
 ---------------|------------------|-----------------
 | PXE ROM | DHCP request -> | DHCP server
@@ -744,6 +753,7 @@
 | Reboot | |
 | Boot from hard disk | |
 | Installed Windows System | Run post boot scripts |
+
 
@@ -766,6 +776,7 @@
 numcols=3;
 colwidths=20,30,20;
 -->
+
 | Machine name  | IP Address | Alias
 ----------------|------------|------
 | managementnode.pub.site.net | 10.0.12.53 |  managementnode.site.net
@@ -778,6 +789,7 @@
 | node02.10g.site.net | 10.0.17.15 | node02.site.net
 | node01.priv.site.net | 192.168.1.21 |
 | node02.priv.site.net| 192.168.1.22 |
+

XCAT_iDataPlex_Advanced_Setup modified by

Thu, 28 Aug 2014 00:27:32 -0000

--- v141
+++ v142
@@ -522,242 +522,11 @@

 ### Network Installation of a x86_64 Stateful Node Using Kickstart

-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Booting Node <-- Network Transfer --> Management Node
PXE ROM DHCP request --> DHCP server
PXE ROM <-- IP configuration DHCP server
PXE ROM <-- TFTP server IP address DHCP server
PXE ROM <-- bootloader file name DHCP server
PXE ROM request for bootloader --> TFTP server
PXE ROM <-- bootloader executable (xnba.kpxe or xnba.efi) TFTP server
bootloader (xnba.kpxe/xnba.efi) DHCP request --> DHCP server
bootloader (xnba.kpxe/xnba.efi) <-- bootloader config URL DHCP server
bootloader (xnba.kpxe/xnba.efi) request bootloader configuration --> HTTP server
bootloader (xnba.kpxe/xnba.efi) <-- bootloader configuration HTTP server
UEFI bootloader (xnba.efi) only request elilo (elilo-x64.efi) --> HTTP server
UEFI bootloader (xnba.efi) only <-- elilo (/tftpboot/xcat/elilo-x64.efi) HTTP server
UEFI bootloader (xnba.efi) only request elilo configuration --> HTTP server
UEFI bootloader (xnba.efi) only <-- configuration(/tftpboot/xcat/xnba/nodes/<node>.elilo) HTTP server
bootloader (xnba/elilo) request for linux kernel --> HTTP server
bootloader (xnba/elilo) <-- linux kernel HTTP server
bootloader (xnba/elilo) request for initrd --> HTTP server
bootloader (xnba/elilo) <-- initrd.img HTTP server
initrd request kickstart file --> HTTP server
initrd <-- kickstart file (/install/autoinst/<node>) HTTP server
initrd request 2nd stage bootloader --> DHCP server
initrd <-- 2nd stage bootloader (/install/<os>/x86_64/images/install.img) HTTP server
kickstart installer (install.img) request installation pkgs --> HTTP server
kickstart installer (install.img) <-- installation pkgs HTTP server
kickstart %post (post.xcat) request postscripts --> HTTP server
kickstart %post (post.xcat) <-- postscripts (/install/postscripts/*) HTTP server
kickstart %post (post.xcat) execute the postscripts <--> xCAT server
xCAT postscript (for Power only) set node to boot from local disk 
updateflag.awk configure bootloader configuration to boot node from hd --> xCAT server
kickstart installer (install.img) reboot node 
PXE DHCP request --> DHCP server
PXE <-- IP configuration DHCP server
PXE <-- TFTP server IP address DHCP server
PXE <-- bootfile name (xnba.kpxe) DHCP server
PXE request for bootloader (xnba.kpxe) --> TFTP server
PXE <-- bootloader executable (xnba.kpxe) TFTP server
bootloader xnba.kpxe request bootloader configuration --> TFTP server
bootloader xnba.kpxe <-- bootloader configuration (/tftpboot/xcat/xnba/nodes/<node>)(localboot) TFTPserver
boot from local disk 
/etc/init.d/xcatpostinit1 execute /opt/xcat/xcatinstallpost 
/opt/xcat/xcatinstallpost set "REBOOT=TRUE" in /opt/xcat/xcatinfo 
/opt/xcat/xcatinstallpost execute mypostscript.post in /xcatpost 
mypostscript.post execute postbootscripts in /xcatpost 
updateflag.awk update node status to booted --> xCAT server
-
-
-
-
-
+
 | Booting Node | <-- Network Transfer --> | Management Node
 ---------------|--------------------------|-----------------
 | PXE ROM | DHCP request --> | DHCP server
@@ -804,8 +573,17 @@
 | /opt/xcat/xcatinstallpost | execute mypostscript.post in /xcatpost
 | mypostscript.post | execute postbootscripts in /xcatpost
 | updateflag.awk | update node status to booted --> | xCAT server
+

 ### Network Installation of a x86_64 Stateful Node using Autoyast
+
+
 | Booting Node | Network Transfer | Management Node
 ---------------|------------------|-----------------
 | PXE ROM | DHCP request --> | DHCP server
@@ -843,10 +621,17 @@
 | /opt/xcat/xcatinstallpost | execute mypostscript.post in /xcatpost |
 | mypostscript.post | execute postbootscripts in /xcatpost |
 | updateflag.awk | update node status to booted --> | xCAT server
+

 ### Network Boot of a x86_64 Stateless (RAMdisk) Node

-
+
 | Booting Node | Network Transfer | Management Node
 ---------------|------------------|-----------------
 | PXE ROM | DHCP request --> | DHCP server
@@ -874,10 +659,17 @@
 | xcatdsklspost | execute the postscripts |
 | xcatdsklspost | execute the post BOOT scripts |
 | xcatdsklspost | update node status --> | xCAT server
+

 ### Network Boot of a Statelite (NFS root) Node

-
+
 | Booting Node | Network Transfer | Management Node
 ---------------|------------------|-----------------
 | PXE ROM | DHCP request --> | DHCP server
@@ -903,12 +695,19 @@
 | installer postscripts | execute the postscripts <--> | xCAT server
 | installer postscripts | execute the post BOOT scripts <--> | xCAT server
 | | update node status --> | xCAT server
+

 ### Network Deployment Diskful Windows Compute Node Using WinPE
 NOTE: The deployment process could use proxydhcp or not. If using proxydhcp, ignore the 'NO Proxydhcp Only' part. Otherwise ignore the 'Proxydhcp Only' part.
 NOTE: The compute node could boot in BIOS or UEFI mode. If booting in BIOS mode, ignore the 'UEFI Only' part. Otherwise ignore the 'BIOS Only' part.

-
+
 | Booting Node | Network Transfer | Management Node
 ---------------|------------------|-----------------
 | PXE ROM | DHCP request -> | DHCP server
@@ -945,6 +744,9 @@
 | Reboot | |
 | Boot from hard disk | |
 | Installed Windows System | Run post boot scripts |
+

@@ -959,6 +761,11 @@

 Network Table

+
 | Machine name  | IP Address | Alias
 ----------------|------------|------
 | managementnode.pub.site.net | 10.0.12.53 |  managementnode.site.net
@@ -971,6 +778,10 @@
 | node02.10g.site.net | 10.0.17.15 | node02.site.net
 | node01.priv.site.net | 192.168.1.21 |
 | node02.priv.site.net| 192.168.1.22 |
+
+

Booting Node	<-- Network Transfer -->	Management Node
PXE ROM	DHCP request -->	DHCP server
PXE ROM	<-- IP configuration	DHCP server
PXE ROM	<-- TFTP server IP address	DHCP server
PXE ROM	<-- bootloader file name	DHCP server
PXE ROM	request for bootloader -->	TFTP server
PXE ROM	<-- bootloader executable (xnba.kpxe or xnba.efi)	TFTP server
bootloader (xnba.kpxe/xnba.efi)	DHCP request -->	DHCP server
bootloader (xnba.kpxe/xnba.efi)	<-- bootloader config URL	DHCP server
bootloader (xnba.kpxe/xnba.efi)	request bootloader configuration -->	HTTP server
bootloader (xnba.kpxe/xnba.efi)	<-- bootloader configuration	HTTP server
UEFI bootloader (xnba.efi) only	request elilo (elilo-x64.efi) -->	HTTP server
UEFI bootloader (xnba.efi) only	<-- elilo (/tftpboot/xcat/elilo-x64.efi)	HTTP server
UEFI bootloader (xnba.efi) only	request elilo configuration -->	HTTP server
UEFI bootloader (xnba.efi) only	<-- configuration(/tftpboot/xcat/xnba/nodes/<node>.elilo)	HTTP server
bootloader (xnba/elilo)	request for linux kernel -->	HTTP server
bootloader (xnba/elilo)	<-- linux kernel	HTTP server
bootloader (xnba/elilo)	request for initrd -->	HTTP server
bootloader (xnba/elilo)	<-- initrd.img	HTTP server
initrd	request kickstart file -->	HTTP server
initrd	<-- kickstart file (/install/autoinst/<node>)	HTTP server
initrd	request 2nd stage bootloader -->	DHCP server
initrd	<-- 2nd stage bootloader (/install/<os>/x86_64/images/install.img)	HTTP server
kickstart installer (install.img)	request installation pkgs -->	HTTP server
kickstart installer (install.img)	<-- installation pkgs	HTTP server
kickstart %post (post.xcat)	request postscripts -->	HTTP server
kickstart %post (post.xcat)	<-- postscripts (/install/postscripts/*)	HTTP server
kickstart %post (post.xcat)	execute the postscripts <-->	xCAT server
xCAT postscript (for Power only)	set node to boot from local disk
updateflag.awk	configure bootloader configuration to boot node from hd -->	xCAT server
kickstart installer (install.img)	reboot node
PXE	DHCP request -->	DHCP server
PXE	<-- IP configuration	DHCP server
PXE	<-- TFTP server IP address	DHCP server
PXE	<-- bootfile name (xnba.kpxe)	DHCP server
PXE	request for bootloader (xnba.kpxe) -->	TFTP server
PXE	<-- bootloader executable (xnba.kpxe)	TFTP server
bootloader xnba.kpxe	request bootloader configuration -->	TFTP server
bootloader xnba.kpxe	<-- bootloader configuration (/tftpboot/xcat/xnba/nodes/<node>)(localboot)	TFTPserver
boot from local disk
/etc/init.d/xcatpostinit1	execute /opt/xcat/xcatinstallpost
/opt/xcat/xcatinstallpost	set "REBOOT=TRUE" in /opt/xcat/xcatinfo
/opt/xcat/xcatinstallpost	execute mypostscript.post in /xcatpost
mypostscript.post	execute postbootscripts in /xcatpost
updateflag.awk	update node status to booted -->	xCAT server

XCAT_iDataPlex_Advanced_Setup modified by

Tue, 26 Aug 2014 20:12:58 -0000

XCAT_iDataPlex_Advanced_Setup modified by

Tue, 26 Aug 2014 20:12:28 -0000

XCAT_iDataPlex_Advanced_Setup modified by

Tue, 26 Aug 2014 20:12:02 -0000

--- v138
+++ v139
@@ -3,6 +3,11 @@
 [TOC]

 ## **Use the driver update disk**
+
+

 Linux supplies the driver update disk mechanism to support the devices which cannot be driven by the released distribution during the installation process. "driver update disk" is a media which contains the drivers and related configuration files for certain devices.