Recent changes to Using_Clone_to_Deploy_Server

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Wed, 03 Dec 2014 09:01:15 -0000

--- v47
+++ v48
@@ -233,4 +233,7 @@
     [root@Centos6.5 node]# rpm -ivh systemimager-client-4.3.0-0.1.noarch.rpm
 ~~~~

- 
+#### Kernel panic at times when install target node with rhels7.0 in power 7 server
+
+When you clone rhels7.0 image to target node which is power 7 server lpar, maybe you will hit Kernel panic problem at times after boot loader grub2 download kernel and initrd. This is an known issue but without resolve yet. up to now, we recommend you try again. 
+

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Wed, 03 Dec 2014 08:48:33 -0000

--- v46
+++ v47
@@ -27,7 +27,7 @@
 |  2.9 and later    | redhat | 6.4           |ppc64   |Basic clone node/update delta changes/LVM
 |                   | sles   | 11.3          |ppc64   |Basic clone node/update delta changes
 |                   | redhat | 7.0           |ppc64   |Basic clone node/update delta changes/LVM
-|                   | redhat | 6.4           |x86_64  |support LVM
+|                   | redhat | 6.4  7.0      |x86_64  |support LVM

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Wed, 05 Nov 2014 10:59:07 -0000

--- v45
+++ v46
@@ -135,7 +135,7 @@
     updatenode <golden-cilent> -S
 ~~~~

-[Note] If you install systemimager RPMs on Centos 6.5 node by yum, you maybe hit failure. this is a konw issue(please refer to konw issue section) because some defect of Centos6.5 itself.
+[Note] If you install systemimager RPMs on Centos 6.5 node by above steps, you maybe hit failure. this is a known issue because some defect of Centos6.5 itself. Please refer to known issue section for help.

 ### Capture Image from Golden Client

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Wed, 05 Nov 2014 10:55:20 -0000

--- v44
+++ v45
@@ -24,9 +24,9 @@
 |                   | redhat | 6.4           |x86_64  |Add feature: update delta changes(has limitation)
 |                   | sles   | 11.3          |x86_64  |Add feature: update delta changes
 |                   | sles   | 10.x          |x86_64  |Not support any more
-|  2.9 and later    | redhat | 6.4           |ppc64   |Basic clone node and update delta changes
-|                   | sles   | 11.3          |ppc64   |Basic clone node and update delta changes
-|                   | redhat | 6.4           |ppc64   |support LVM
+|  2.9 and later    | redhat | 6.4           |ppc64   |Basic clone node/update delta changes/LVM
+|                   | sles   | 11.3          |ppc64   |Basic clone node/update delta changes
+|                   | redhat | 7.0           |ppc64   |Basic clone node/update delta changes/LVM
 |                   | redhat | 6.4           |x86_64  |support LVM

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Mon, 27 Oct 2014 02:57:53 -0000

--- v43
+++ v44
@@ -34,7 +34,7 @@
 -->

-### Using Sysclone to install Nodes
+### Using Sysclone to Install Nodes

 This document describes how to install and configure a template node (called golden client), capture an image from this template node. Then using this image to deploy other same nodes (called target nodes) quickly.

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Thu, 25 Sep 2014 07:17:10 -0000

--- v42
+++ v43
@@ -24,6 +24,10 @@
 |                   | redhat | 6.4           |x86_64  |Add feature: update delta changes(has limitation)
 |                   | sles   | 11.3          |x86_64  |Add feature: update delta changes
 |                   | sles   | 10.x          |x86_64  |Not support any more
+|  2.9 and later    | redhat | 6.4           |ppc64   |Basic clone node and update delta changes
+|                   | sles   | 11.3          |ppc64   |Basic clone node and update delta changes
+|                   | redhat | 6.4           |ppc64   |support LVM
+|                   | redhat | 6.4           |x86_64  |support LVM

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Wed, 24 Sep 2014 09:36:57 -0000

--- v41
+++ v42
@@ -55,7 +55,7 @@
     zypper -n install systemimager-server
 ~~~~

-    Maybe you will encounter below failed message when you install systemimager-server, jsut ignore it.
+    Maybe you will encounter below failed message when you install systemimager-server, just ignore it.

 ~~~~   
     Can't locate AppConfig.pm in @INC (@INC contains: /usr/lib/systemimager/perl /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/lib/systemimager/perl/SystemImager/Config.pm line 13.
@@ -94,7 +94,7 @@

 ### Install and Configure the Golden Client

-The Golden Client acts as a regular node for xCAT, just have some extra rpms to support clone.  When you deploy golden client with xCAT, you just need to add a few additional definitions to it's image which will be used to deploy golden client.
+The Golden Client acts as a regular node for xCAT, just have some extra rpms to support clone.  When you deploy golden client with xCAT, you just need to add a few additional definitions to the image which will be used to deploy golden client.

 For information of how to install a regular node, read this documentation :
 [Installing_Stateful_Linux_Nodes#Option_1:_Installing_Stateful_Nodes_Using_ISOs_or_DVDs](Installing_Stateful_Linux_Nodes/#option-1-installing-stateful-nodes-using-isos-or-dvds). 
@@ -136,7 +136,7 @@
 When imgcapture is run, it pulls the image from the golden-client, and creates a image files system and a corresponding osimage definition on the xcat management node. You can use below command to check the osimage attributes.

 ~~~~
- lsdef -t osimage <mycomputeimage> 
+    lsdef -t osimage <mycomputeimage> 
 ~~~~

 #### Install the target nodes with the image from the golden-client
@@ -194,7 +194,7 @@

 3.2 If you are running xCAT 2.8.5 or later:

-    you could push the updates out to the other nodes quickly by below command:
+you could push the updates out to the other nodes quickly by below command:

 ~~~~
     updatenode <target-node-range> -S

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Wed, 24 Sep 2014 09:22:52 -0000

--- v40
+++ v41
@@ -58,12 +58,12 @@
     Maybe you will encounter below failed message when you install systemimager-server, jsut ignore it.

 ~~~~   
-Can't locate AppConfig.pm in @INC (@INC contains: /usr/lib/systemimager/perl /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/lib/systemimager/perl/SystemImager/Config.pm line 13.
-BEGIN failed--compilation aborted at /usr/lib/systemimager/perl/SystemImager/Config.pm line 13.
-Compilation failed in require at /usr/lib/systemimager/perl/SystemImager/Server.pm line 17.
-BEGIN failed--compilation aborted at /usr/lib/systemimager/perl/SystemImager/Server.pm line 17.
-Compilation failed in require at /usr/sbin/si_mkrsyncd_conf line 28.
-BEGIN failed--compilation aborted at /usr/sbin/si_mkrsyncd_conf line 28.
+    Can't locate AppConfig.pm in @INC (@INC contains: /usr/lib/systemimager/perl /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/lib/systemimager/perl/SystemImager/Config.pm line 13.
+    BEGIN failed--compilation aborted at /usr/lib/systemimager/perl/SystemImager/Config.pm line 13.
+    Compilation failed in require at /usr/lib/systemimager/perl/SystemImager/Server.pm line 17.
+    BEGIN failed--compilation aborted at /usr/lib/systemimager/perl/SystemImager/Server.pm line 17.
+    Compilation failed in require at /usr/sbin/si_mkrsyncd_conf line 28.
+    BEGIN failed--compilation aborted at /usr/sbin/si_mkrsyncd_conf line 28.
 ~~~~

   * Do some preparation for install and configure golden client in management node. Copy the xcat-dep-***.tar.bz2 file to directory "/install/post/otherpkgs/<osversion>/<arch>/xcat/" of the management node according your golden client's OS version and system architecture, then untar it. For example: 
@@ -171,16 +171,9 @@
     imgcapture <golden-client> -t sysclone -o <myimagename>
 ~~~~ 

-3. To synchronize the changes to your target nodes do the following:
-3.1 If you are running xCAT 2.8.5 or later:
-
-    For the nodes you want to update with this updated golden image:
-
-~~~~
-    updatenode <target-node-range> -S
-~~~~
-
-3.2 If you are running xCAT 2.8.4 or older:
+3.To synchronize the changes to your target nodes do the following:
+
+3.1 If you are running xCAT 2.8.4 or older:

 For one of the nodes you want to update, test the update to see which files will be updated:

@@ -198,3 +191,11 @@
 ~~~~
     xdsh <target-node-range> -s 'si_updateclient --server <mgmtnode-ip> --yes'
 ~~~~
+
+3.2 If you are running xCAT 2.8.5 or later:
+
+    you could push the updates out to the other nodes quickly by below command:
+
+~~~~
+    updatenode <target-node-range> -S
+~~~~

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Wed, 24 Sep 2014 09:13:06 -0000

--- v39
+++ v40
@@ -32,17 +32,19 @@

 ### Using Sysclone to install Nodes

-This section describes how to install or configure a diskful node (we call it a golden-client), capture an osimage from the golden-client. That  osimage from the golden-client can be used to install  other nodes (called the target nodes). 
+Sometime, in a cluster, we need to deploy many nodes which have same configuration. we hope to have a quicker deployment method, rather than install and configure them one by one and repeat same operation. Xcat provides a feature called Sysclone to help you solve this problem.
+
+This document describes how to install and configure a template node (we call it a golden-client), capture an image from this template node. Then using this image to deploy other same nodes (called the target nodes) quickly. 

 ### Prepare the xCAT Mgmt Node for Using Sysclone

-How to configure xCAT Mgmt Node please refer to [Install_xCAT_on_the_Management_Node](Install_xCAT_on_the_Management_Node).
+How to configure xCAT management node please refer to [Install_xCAT_on_the_Management_Node](Install_xCAT_on_the_Management_Node).

-For support Sysclone, we need to install the systemimager rpms on MN and the golden-client. 
-
-  * Download the xcat-dep tarball which includes systemimager rpms. (You might already have the xcat-dep tarball on the mgmt node. If not, go to [xcat-dep](http://sourceforge.net/projects/xcat/files/xcat-dep/2.x_Linux) and get the latest xCAT dependency tarball.) 
-
-  * Install systemimager server on Mgmt Node
+For support Sysclone, we need to install some extra systemimager rpms on management node and the golden-client. 
+
+  * Download the xcat-dep tarball (xcat-dep-***.tar.bz2) which includes systemimager rpms. (You might already have the xcat-dep tarball on the management node. If not, go to [xcat-dep](http://sourceforge.net/projects/xcat/files/xcat-dep/2.x_Linux) and get the latest xCAT dependency tarball.) 
+
+  * Install systemimager server on management node

 ~~~~   
     (For RH/CentOS):
@@ -53,10 +55,21 @@
     zypper -n install systemimager-server
 ~~~~  

-  * Do some preparation for install and configure the golden client. Copy the xcat-dep-***.tar.bz2 file to directroy /install/post/otherpkgs/<osversion>/<arch>/xcat/ of the management node according your OS version and system architecture and untar it. For example: 
-
-~~~~   
-    (For Redhat6.3 on x86_64):    
+    Maybe you will encounter below failed message when you install systemimager-server, jsut ignore it.
+
+~~~~   
+Can't locate AppConfig.pm in @INC (@INC contains: /usr/lib/systemimager/perl /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/lib/systemimager/perl/SystemImager/Config.pm line 13.
+BEGIN failed--compilation aborted at /usr/lib/systemimager/perl/SystemImager/Config.pm line 13.
+Compilation failed in require at /usr/lib/systemimager/perl/SystemImager/Server.pm line 17.
+BEGIN failed--compilation aborted at /usr/lib/systemimager/perl/SystemImager/Server.pm line 17.
+Compilation failed in require at /usr/sbin/si_mkrsyncd_conf line 28.
+BEGIN failed--compilation aborted at /usr/sbin/si_mkrsyncd_conf line 28.
+~~~~
+
+  * Do some preparation for install and configure golden client in management node. Copy the xcat-dep-***.tar.bz2 file to directory "/install/post/otherpkgs/<osversion>/<arch>/xcat/" of the management node according your golden client's OS version and system architecture, then untar it. For example: 
+
+~~~~   
+    (For Redhat6.3 and x86_64 system):    
     mkdir -p /install/post/otherpkgs/rhels6.3/x86_64/xcat
     cp xcat-dep-*.tar.bz2  /install/post/otherpkgs/rhels6.3/x86_64/xcat
     cd /install/post/otherpkgs/rhels6.3/x86_64/xcat
@@ -64,7 +77,7 @@
 ~~~~      

 ~~~~ 
-    (For SLES11.3 on x86_64):  
+    (For SLES11.3 and x86_64 system):  
     mkdir -p /install/post/otherpkgs/sles11.3/x86_64/xcat
     cp xcat-dep-*.tar.bz2  /install/post/otherpkgs/sles11.3/x86_64/xcat
     cd /install/post/otherpkgs/sles11.3/x86_64/xcat
@@ -72,25 +85,24 @@
 ~~~~      

 ~~~~   
-    (For Redhat6.3 on ppc64):    
+    (For Redhat6.3 and ppc64 system):    
     mkdir -p /install/post/otherpkgs/rhels6.3/ppc64/xcat
     cp xcat-dep-*.tar.bz2  /install/post/otherpkgs/rhels6.3/ppc64/xcat
     cd /install/post/otherpkgs/rhels6.3/ppc64/xcat
     tar jxvf xcat-dep-*.tar.bz2
 ~~~~ 

-### Install or Configure the Golden Client
-
-The Golden Client is a regular node for xCAT.  When you deploy golden client with xCAT, you just need add a few additional definitions to it's osimage which will used to install in golden client.
-
-For information on how to install a regular node, read this documentation :
+### Install and Configure the Golden Client
+
+The Golden Client acts as a regular node for xCAT, just have some extra rpms to support clone.  When you deploy golden client with xCAT, you just need to add a few additional definitions to it's image which will be used to deploy golden client.
+
+For information of how to install a regular node, read this documentation :
 [Installing_Stateful_Linux_Nodes#Option_1:_Installing_Stateful_Nodes_Using_ISOs_or_DVDs](Installing_Stateful_Linux_Nodes/#option-1-installing-stateful-nodes-using-isos-or-dvds). 

-For the osimage to support clone, add the sysclone otherpkglist file and otherpkgdir to osimage definition.
-Then use updatenode or normal deployment to install systemimager rpms on golden client. Centos share the same pkglist file with redhat. For example: 
-
-~~~~  
-    (For RH6.3/CentOS6.3 on x86_64 ): 
+For support clone, add 'otherpkglist' and 'otherpkgdir' attributes to the image definition which will be used to deploy golden client and deploy golden client as normal. then the golden client will have extra rpms to support clone. If you have deployed your golden client already, using 'updatenode' command to push these extra rpms to golden client. Centos share the same pkglist file with redhat. For example: 
+
+~~~~  
+    (For RH6.3/CentOS6.3 and x86_64 system): 
     chdef -t osimage -o <osimage-name> otherpkglist=/opt/xcat/share/xcat/install \
          /rh/sysclone.rhels6.x86_64.otherpkgs.pkglist
     chdef -t osimage -o <osimage-name> -p otherpkgdir=/install/post/otherpkgs/rhels6.3/x86_64
@@ -98,7 +110,7 @@
 ~~~~      

 ~~~~  
-    (For SLES11.3 on x86_64):  
+    (For SLES11.3 and x86_64 system):  
     chdef -t osimage -o <osimage-name> otherpkglist=/opt/xcat/share/xcat/install  \
      /sles/sysclone.sles11.x86_64.otherpkgs.pkglist
     chdef -t osimage -o <osimage-name> -p otherpkgdir=/install/post/otherpkgs/sles11.3/x86_64
@@ -106,7 +118,7 @@
 ~~~~      

 ~~~~  
-    (For RH6.3/CentOS6.3 on ppc64 ): 
+    (For RH6.3 and ppc64 system): 
     chdef -t osimage -o <osimage-name> otherpkglist=/opt/xcat/share/xcat/install \
          /rh/sysclone.rhels6.ppc64.otherpkgs.pkglist
     chdef -t osimage -o <osimage-name> -p otherpkgdir=/install/post/otherpkgs/rhels6.3/ppc64
@@ -115,13 +127,13 @@

 ### Capture image of the Golden Client 

-On the Management node, use xCAT command imgcapture to capture an osimage from the golden-client. 
+On the Management node, use xCAT command imgcapture to capture an image from the golden-client. 

 ~~~~     
-    imgcapture <golden-client> -t sysclone -o <mycomputeimage>
-~~~~      
-
-When imgcapture is run, it pulls the osimage from the golden-client, and creates the image files system and a corresponding osimage definition on the xcat management node. You can use this  command to check the osimage attributes.
+    imgcapture <golden-client> -t sysclone -o <mycomputeimage> 
+~~~~      
+
+When imgcapture is run, it pulls the image from the golden-client, and creates a image files system and a corresponding osimage definition on the xcat management node. You can use below command to check the osimage attributes.

 ~~~~
  lsdef -t osimage <mycomputeimage> 
@@ -129,12 +141,17 @@

 #### Install the target nodes with the image from the golden-client

-The nodeset command configures the  node for installation. rsetboot tells the node hardware to boot from the network for the next boot. Powering on the node using rpower starts the installation process: 
-
-~~~~     
+following below commands to install the target nodes with the image captured from golden client.
+
+~~~~    
+    (For x86_64 system):  
     nodeset <target-node> osimage=<mycomputeimage>
     rsetboot <target-node> net
     rpower <target-node> boot
+
+    (For ppc64 system):  
+    nodeset <target-node> osimage=<mycomputeimage>
+    rnetboot <target-node> 
 ~~~~

Using_Clone_to_Deploy_Server modified by huweihua

huweihua — Wed, 24 Sep 2014 03:40:10 -0000

--- v38
+++ v39
@@ -53,35 +53,44 @@
     zypper -n install systemimager-server
 ~~~~

-  * Do some preparation for install and configure the golden client. Copy the file to the management node and untar it in the appropriate directory(/install/post/otherpkgs/<osversion>/<arch>/xcat/. For example: 
+  * Do some preparation for install and configure the golden client. Copy the xcat-dep-***.tar.bz2 file to directroy /install/post/otherpkgs/<osversion>/<arch>/xcat/ of the management node according your OS version and system architecture and untar it. For example: 

 ~~~~   
-    (For RH/CentOS):    
+    (For Redhat6.3 on x86_64):    
     mkdir -p /install/post/otherpkgs/rhels6.3/x86_64/xcat
+    cp xcat-dep-*.tar.bz2  /install/post/otherpkgs/rhels6.3/x86_64/xcat
     cd /install/post/otherpkgs/rhels6.3/x86_64/xcat
     tar jxvf xcat-dep-*.tar.bz2
 ~~~~      

 ~~~~ 
-    (For SLES):  
+    (For SLES11.3 on x86_64):  
     mkdir -p /install/post/otherpkgs/sles11.3/x86_64/xcat
+    cp xcat-dep-*.tar.bz2  /install/post/otherpkgs/sles11.3/x86_64/xcat
     cd /install/post/otherpkgs/sles11.3/x86_64/xcat
     tar jxvf xcat-dep-*.tar.bz2
 ~~~~      

+~~~~   
+    (For Redhat6.3 on ppc64):    
+    mkdir -p /install/post/otherpkgs/rhels6.3/ppc64/xcat
+    cp xcat-dep-*.tar.bz2  /install/post/otherpkgs/rhels6.3/ppc64/xcat
+    cd /install/post/otherpkgs/rhels6.3/ppc64/xcat
+    tar jxvf xcat-dep-*.tar.bz2
+~~~~ 

 ### Install or Configure the Golden Client

-The Golden Client is a regular node for xCAT.  When you deploy golden client with xCAT, you just need add a few additional definitions to it's  osimage, which will used to install in golden client.
+The Golden Client is a regular node for xCAT.  When you deploy golden client with xCAT, you just need add a few additional definitions to it's osimage which will used to install in golden client.

 For information on how to install a regular node, read this documentation :
 [Installing_Stateful_Linux_Nodes#Option_1:_Installing_Stateful_Nodes_Using_ISOs_or_DVDs](Installing_Stateful_Linux_Nodes/#option-1-installing-stateful-nodes-using-isos-or-dvds). 

 For the osimage to support clone, add the sysclone otherpkglist file and otherpkgdir to osimage definition.
- Then use updatenode to install the rpms. Centos share the same pkglist file with redhat. For example: 
+Then use updatenode or normal deployment to install systemimager rpms on golden client. Centos share the same pkglist file with redhat. For example: 

 ~~~~  
-    (For RH/CentOS): 
+    (For RH6.3/CentOS6.3 on x86_64 ): 
     chdef -t osimage -o <osimage-name> otherpkglist=/opt/xcat/share/xcat/install \
          /rh/sysclone.rhels6.x86_64.otherpkgs.pkglist
     chdef -t osimage -o <osimage-name> -p otherpkgdir=/install/post/otherpkgs/rhels6.3/x86_64
@@ -89,12 +98,20 @@
 ~~~~      

 ~~~~  
-    (For SLES):  
+    (For SLES11.3 on x86_64):  
     chdef -t osimage -o <osimage-name> otherpkglist=/opt/xcat/share/xcat/install  \
      /sles/sysclone.sles11.x86_64.otherpkgs.pkglist
     chdef -t osimage -o <osimage-name> -p otherpkgdir=/install/post/otherpkgs/sles11.3/x86_64
     updatenode <golden-cilent> -S
 ~~~~      
+
+~~~~  
+    (For RH6.3/CentOS6.3 on ppc64 ): 
+    chdef -t osimage -o <osimage-name> otherpkglist=/opt/xcat/share/xcat/install \
+         /rh/sysclone.rhels6.ppc64.otherpkgs.pkglist
+    chdef -t osimage -o <osimage-name> -p otherpkgdir=/install/post/otherpkgs/rhels6.3/ppc64
+    updatenode <golden-cilent> -S
+~~~~ 

 ### Capture image of the Golden Client