diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ka_method/html/duplication.html | 71 |
1 files changed, 34 insertions, 37 deletions
diff --git a/docs/ka_method/html/duplication.html b/docs/ka_method/html/duplication.html index 9298eafa8..e0efa1dfe 100644 --- a/docs/ka_method/html/duplication.html +++ b/docs/ka_method/html/duplication.html @@ -1,9 +1,9 @@ <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /><title>Clone a node/computer using KA method</title><link rel="stylesheet" href="styleguibo.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="#id2621064" title="Clone a node/computer using KA method" /><link rel="next" href="#id2883863" title="1.CLONING WILL ERASE ALL CLIENT NODES DATA !" /></head><body><div xml:lang="en" class="article" title="Clone a node/computer using KA method" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="id2621064"></a>Clone a node/computer using KA method</h2></div></div><hr /></div><div class="toc"><dl><dt><span class="sect1"><a href="#id2883863">1. CLONING WILL ERASE ALL CLIENT NODES DATA !</a></span></dt><dt><span class="sect1"><a href="#id2883870">2. Clone a computer over the network</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2883893">2.1. KA method</a></span></dt><dt><span class="sect2"><a href="#id2884282">2.2. HOW it works</a></span></dt><dd><dl><dt><span class="sect3"><a href="#id2884287">2.2.1. Steps</a></span></dt><dt><span class="sect3"><a href="#id2884358">2.2.2. Needed files</a></span></dt></dl></dd><dt><span class="sect2"><a href="#id2884413">2.3. Step 1: PXE, TFTP, DHCPD services</a></span></dt><dd><dl><dt><span class="sect3"><a href="#id2884449">2.3.1. PXE parameters on server</a></span></dt><dt><span class="sect3"><a href="#id2884530">2.3.2. TFTP server</a></span></dt><dt><span class="sect3"><a href="#id2884561">2.3.3. PXE configuration</a></span></dt><dt><span class="sect3"><a href="#id2884573">2.3.4. DHCPD configuration</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="#id2884679">3. Setup a node as a golden node</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2884685">3.1. The rescue.sqfs file</a></span></dt><dd><dl><dt><span class="sect3"><a href="#id2884741">3.1.1. ka-d.sh</a></span></dt><dt><span class="sect3"><a href="#id2884774">3.1.2. replication.conf</a></span></dt><dt><span class="sect3"><a href="#id2884786">3.1.3. fdisk_to_desc</a></span></dt><dt><span class="sect3"><a href="#id2884815">3.1.4. gen_modprobe_conf.pl</a></span></dt><dt><span class="sect3"><a href="#id2884838">3.1.5. ka-d-client</a></span></dt><dt><span class="sect3"><a href="#id2884873">3.1.6. ka-d-server</a></span></dt><dt><span class="sect3"><a href="#id2884922">3.1.7. ka_replication.sh</a></span></dt><dt><span class="sect3"><a href="#id2884946">3.1.8. store_log.sh</a></span></dt><dt><span class="sect3"><a href="#id2884974">3.1.9. bootable_flag.sh</a></span></dt><dt><span class="sect3"><a href="#id2884985">3.1.10. make_initrd_grub</a></span></dt><dt><span class="sect3"><a href="#id2885008">3.1.11. make_initrd_lilo</a></span></dt><dt><span class="sect3"><a href="#id2885031">3.1.12. prepare_node.sh</a></span></dt><dt><span class="sect3"><a href="#id2885057">3.1.13. send_status.pl</a></span></dt><dt><span class="sect3"><a href="#id2885080">3.1.14. status_node.pl</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="#id2885099">4. The golden node, KA server</a></span></dt><dt><span class="sect1"><a href="#id2885248">5. KA client node</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2885253">5.1. PXE server (kamethod)</a></span></dt><dt><span class="sect2"><a href="#id2885290">5.2. Stage1 KA method, node waiting stage2 </a></span></dt><dt><span class="sect2"><a href="#id2885337">5.3. Stage2, the duplication process</a></span></dt><dt><span class="sect2"><a href="#id2885407">5.4. Prepare the node</a></span></dt><dt><span class="sect2"><a href="#id2885433">5.5. PXE server to local boot</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2885450">6. Step by step from scratch KA duplication</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2885485">6.1. Golden node side</a></span></dt><dt><span class="sect2"><a href="#id2885629">6.2. KA client side</a></span></dt><dt><span class="sect2"><a href="#id2886415">6.3. Post duplication process</a></span></dt></dl></dd></dl></div><div class="sect1" title="1.CLONING WILL ERASE ALL CLIENT NODES DATA !"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2883863"></a>1.CLONING WILL ERASE ALL CLIENT NODES DATA !</h2></div></div></div><p>!! USE WITH CARE !! </p></div><div class="sect1" title="2.Clone a computer over the network"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2883870"></a>2.Clone a computer over the network</h2></div></div></div><p> +<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /><title>Clone a node/computer using KA method</title><link rel="stylesheet" href="styleguibo.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="#id2251469" title="Clone a node/computer using KA method" /><link rel="next" href="#id2514268" title="1.CLONING WILL ERASE ALL CLIENT NODES DATA !" /></head><body><div xml:lang="en" class="article" title="Clone a node/computer using KA method" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="id2251469"></a>Clone a node/computer using KA method</h2></div></div><hr /></div><div class="toc"><dl><dt><span class="sect1"><a href="#id2514268">1. CLONING WILL ERASE ALL CLIENT NODES DATA !</a></span></dt><dt><span class="sect1"><a href="#id2514275">2. Clone a computer over the network</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2514297">2.1. KA method</a></span></dt><dt><span class="sect2"><a href="#id2514686">2.2. HOW it works</a></span></dt><dd><dl><dt><span class="sect3"><a href="#id2514692">2.2.1. Steps</a></span></dt><dt><span class="sect3"><a href="#id2514762">2.2.2. Needed files</a></span></dt></dl></dd><dt><span class="sect2"><a href="#id2514817">2.3. Step 1: PXE, TFTP, DHCPD services</a></span></dt><dd><dl><dt><span class="sect3"><a href="#id2514853">2.3.1. PXE parameters on server</a></span></dt><dt><span class="sect3"><a href="#id2514934">2.3.2. TFTP server</a></span></dt><dt><span class="sect3"><a href="#id2514965">2.3.3. PXE configuration</a></span></dt><dt><span class="sect3"><a href="#id2514977">2.3.4. DHCPD configuration</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="#id2515083">3. Setup a node as a golden node</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2515089">3.1. The rescue.sqfs file</a></span></dt><dd><dl><dt><span class="sect3"><a href="#id2515145">3.1.1. ka-d.sh</a></span></dt><dt><span class="sect3"><a href="#id2515179">3.1.2. replication.conf</a></span></dt><dt><span class="sect3"><a href="#id2515190">3.1.3. fdisk_to_desc</a></span></dt><dt><span class="sect3"><a href="#id2515219">3.1.4. gen_modprobe_conf.pl</a></span></dt><dt><span class="sect3"><a href="#id2515242">3.1.5. ka-d-client</a></span></dt><dt><span class="sect3"><a href="#id2515277">3.1.6. ka-d-server</a></span></dt><dt><span class="sect3"><a href="#id2515326">3.1.7. ka_replication.sh</a></span></dt><dt><span class="sect3"><a href="#id2515350">3.1.8. store_log.sh</a></span></dt><dt><span class="sect3"><a href="#id2515378">3.1.9. bootable_flag.sh</a></span></dt><dt><span class="sect3"><a href="#id2515390">3.1.10. make_initrd_grub</a></span></dt><dt><span class="sect3"><a href="#id2515413">3.1.11. make_initrd_lilo</a></span></dt><dt><span class="sect3"><a href="#id2515436">3.1.12. prepare_node.sh</a></span></dt><dt><span class="sect3"><a href="#id2515461">3.1.13. send_status.pl</a></span></dt><dt><span class="sect3"><a href="#id2515484">3.1.14. status_node.pl</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="#id2515504">4. The golden node, KA server</a></span></dt><dt><span class="sect1"><a href="#id2515652">5. KA client node</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2515657">5.1. PXE server (kamethod)</a></span></dt><dt><span class="sect2"><a href="#id2515694">5.2. Stage1 KA method, node waiting stage2 </a></span></dt><dt><span class="sect2"><a href="#id2515741">5.3. Stage2, the duplication process</a></span></dt><dt><span class="sect2"><a href="#id2515811">5.4. Prepare the node</a></span></dt><dt><span class="sect2"><a href="#id2515837">5.5. PXE server to local boot</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2515854">6. Step by step from scratch KA duplication</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2515889">6.1. Golden node side</a></span></dt><dt><span class="sect2"><a href="#id2516032">6.2. KA client side</a></span></dt><dt><span class="sect2"><a href="#id2516818">6.3. Post duplication process</a></span></dt></dl></dd></dl></div><div class="sect1" title="1.CLONING WILL ERASE ALL CLIENT NODES DATA !"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2514268"></a>1.CLONING WILL ERASE ALL CLIENT NODES DATA !</h2></div></div></div><p>!! USE WITH CARE !! </p></div><div class="sect1" title="2.Clone a computer over the network"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2514275"></a>2.Clone a computer over the network</h2></div></div></div><p> Goal of duplication is to easily deploy a computer over network without taking care of numbers of computer. In this documentation, we call golden node the node we want to clone. We can duplicate SCSI or IDE hard drive, and duplication support multiple filesystem (reiserfs, ext2, ext3, ext4, xfs, jfs). This method came from a very old project called CLIC, and was used under IGGI project, all Mandrake Clustering products, and now it is used under XtreemOS project. Now it should be available in 2010 spring, and all futur product. - </p><p>WARNING: all data on client nodes will be ERASED ! We duplicate partitions of HDD's golden node, and the process will do an fdisk command on the client node, so ALL YOUR DATA will be erased on client nodes.</p><div class="sect2" title="2.1.KA method"><div class="titlepage"><div><div><h3 class="title"><a id="id2883893"></a>2.1.KA method</h3></div></div></div><p> + </p><p>WARNING: all data on client nodes will be ERASED ! We duplicate partitions of HDD's golden node, and the process will do an fdisk command on the client node, so ALL YOUR DATA will be erased on client nodes.</p><div class="sect2" title="2.1.KA method"><div class="titlepage"><div><div><h3 class="title"><a id="id2514297"></a>2.1.KA method</h3></div></div></div><p> With KA method you can quickly duplicate a node using a <span class="bold"><strong>desc</strong></span> file describing partitions. KA method only duplicate data on partitions, so if you have 80go HDD disk, and only 10go on it, KA only duplicates 10go, and not the whole disk. KA method doesn't not support RAID software. @@ -11,15 +11,15 @@ Drawbacks: </p><p> </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>KA method doesn't support RAID software (use dolly to do that)</p></li><li class="listitem"><p>all data on client nodes are erased</p></li><li class="listitem"><p>you need a PXE, DHDCP and TFTP server</p></li><li class="listitem"><p>you must re-create same partition table as the golden node (even if size can differ)</p></li><li class="listitem"><p>even if it has been tested, it's still an experimental method</p></li><li class="listitem"><p>cloning script are old, and need a full rewrite</p></li><li class="listitem"><p>now it's only works with the Mandriva installer (need to patch it to support a KA method)</p></li><li class="listitem"><p>if a node crash while doing a duplication, the duplication process stop (or became very unstable)</p></li><li class="listitem"><p>using fdisk to erase and re-format the HDD is not a good way to proceed</p></li><li class="listitem"><p>UUID support is not really done (fstab use old /dec/sdX)</p></li><li class="listitem"><p>you can only clone Linux filesystems (if you want to duplicate another kinf of FS, it's up to you to modify the scripts)</p></li><li class="listitem"><p>of course various other things !</p></li></ul></div><p> - </p></div><div class="sect2" title="2.2.HOW it works"><div class="titlepage"><div><div><h3 class="title"><a id="id2884282"></a>2.2.HOW it works</h3></div></div></div><div class="sect3" title="2.2.1.Steps"><div class="titlepage"><div><div><h4 class="title"><a id="id2884287"></a>2.2.1.Steps</h4></div></div></div><p> + </p></div><div class="sect2" title="2.2.HOW it works"><div class="titlepage"><div><div><h3 class="title"><a id="id2514686"></a>2.2.HOW it works</h3></div></div></div><div class="sect3" title="2.2.1.Steps"><div class="titlepage"><div><div><h4 class="title"><a id="id2514692"></a>2.2.1.Steps</h4></div></div></div><p> The clone process works in three steps - </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="bold"><strong>PXE boot to retrieve stage1</strong></span>: the computer boot on PXE mode, retrieve <span class="bold"><strong>vmlinuz</strong></span> and an <span class="bold"><strong>initrd</strong></span> image. The computer is in <span class="bold"><strong>stage1</strong></span> mode, and is able to get the stage2 throug KA. Network is up.</p></li><li class="listitem"><p><span class="bold"><strong>get stage2</strong></span>: the computer gets the stage2 with the KA method. The <span class="bold"><strong>stage2</strong></span> contains all necessary tools to recognize your hardware (the most important things is to detect your HDD and your network card), and all necessary tools/scripts to finalize the cloning process.</p></li><li class="listitem"><p><span class="bold"><strong>Duplication process</strong></span>: the computer auto-probes needed modules to be able to access the HDD. A basic log server is launched on the client node to be able to run command and get status of the KA duplication process. The computer reconfigure the modprobe.conf and restore the booloader (grub or lilo)</p></li></ul></div></div><div class="sect3" title="2.2.2.Needed files"><div class="titlepage"><div><div><h4 class="title"><a id="id2884358"></a>2.2.2.Needed files</h4></div></div></div><p> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="bold"><strong>PXE boot to retrieve stage1</strong></span>: the computer boot on PXE mode, retrieve <span class="bold"><strong>vmlinuz</strong></span> and an <span class="bold"><strong>initrd</strong></span> image. The computer is in <span class="bold"><strong>stage1</strong></span> mode, and is able to get the stage2 throug KA. Network is up.</p></li><li class="listitem"><p><span class="bold"><strong>get stage2</strong></span>: the computer gets the stage2 with the KA method. The <span class="bold"><strong>stage2</strong></span> contains all necessary tools to recognize your hardware (the most important things is to detect your HDD and your network card), and all necessary tools/scripts to finalize the cloning process.</p></li><li class="listitem"><p><span class="bold"><strong>Duplication process</strong></span>: the computer auto-probes needed modules to be able to access the HDD. A basic log server is launched on the client node to be able to run command and get status of the KA duplication process. The computer reconfigure the modprobe.conf and restore the booloader (grub or lilo)</p></li></ul></div></div><div class="sect3" title="2.2.2.Needed files"><div class="titlepage"><div><div><h4 class="title"><a id="id2514762"></a>2.2.2.Needed files</h4></div></div></div><p> All needed files are available in Mandriva Linux cooker. </p><p> </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="bold"><strong>install/stage2/rescue.sqfs</strong></span>: this is the stage2 file with all needed files to detect and probe modules, and launch the third step of the duplication process. This file will be used on the golden node.</p></li><li class="listitem"><p><span class="bold"><strong>isolinux/alt0/vmlinuz</strong></span>: linux kernel, needed in the <span class="bold"><strong>/var/lib/tftpboot/X86PC/linux/images/</strong></span> directory of the PXE server</p></li><li class="listitem"><p><span class="bold"><strong>isolinux/alt0/all.rdz</strong></span>: stage1 and all needed modules and tools.</p></li></ul></div><p> - </p></div></div><div class="sect2" title="2.3.Step 1: PXE, TFTP, DHCPD services"><div class="titlepage"><div><div><h3 class="title"><a id="id2884413"></a>2.3.Step 1: PXE, TFTP, DHCPD services</h3></div></div></div><p> + </p></div></div><div class="sect2" title="2.3.Step 1: PXE, TFTP, DHCPD services"><div class="titlepage"><div><div><h3 class="title"><a id="id2514817"></a>2.3.Step 1: PXE, TFTP, DHCPD services</h3></div></div></div><p> To easily clone a computer node, we use PXE technology to boot a <span class="bold"><strong>kernel</strong></span>, and an <span class="bold"><strong>initrd</strong></span> image wich contains all needed modules for network and media storage. Documentation about PXE can be found here: <a class="ulink" href="http://people.mandriva.com/~aginies/doc/pxe/" target="_top">PXE doc</a>. Please, keep in mind setting such services can <span class="bold"><strong>DISTURB</strong></span> your current network architecture. - </p><div class="sect3" title="2.3.1.PXE parameters on server"><div class="titlepage"><div><div><h4 class="title"><a id="id2884449"></a>2.3.1.PXE parameters on server</h4></div></div></div><p> + </p><div class="sect3" title="2.3.1.PXE parameters on server"><div class="titlepage"><div><div><h4 class="title"><a id="id2514853"></a>2.3.1.PXE parameters on server</h4></div></div></div><p> Mandriva Linux installer supports various methods to install a computer. With PXE configuration file you can specify wich method you want to use to install your node, or add a specific option at boot prompt. Edit your default PXE configuration file to add your custom entry (<span class="bold"><strong>/var/lib/tftpboot/X86PC/linux/pxelinux.cfg/default</strong></span>). </p><p> </p><pre class="screen"> @@ -40,7 +40,7 @@ label kamethod At boot prompt no you can boot: </p><p> </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="bold"><strong>DEFAULT local</strong></span>: default boot will be local one, change it with the name of a <span class="bold"><strong>LABEL</strong></span></p></li><li class="listitem"><p><span class="bold"><strong>local</strong></span>: boot local</p></li><li class="listitem"><p><span class="bold"><strong>kamethod</strong></span>: automatic mode, get stage2 through <span class="bold"><strong>KA</strong></span>. Network interface is set to eth0. Auto setup the network with DHCP, and use the KA technology to launch the replication method.</p></li></ul></div><p> - </p></div><div class="sect3" title="2.3.2.TFTP server"><div class="titlepage"><div><div><h4 class="title"><a id="id2884530"></a>2.3.2.TFTP server</h4></div></div></div><p> + </p></div><div class="sect3" title="2.3.2.TFTP server"><div class="titlepage"><div><div><h4 class="title"><a id="id2514934"></a>2.3.2.TFTP server</h4></div></div></div><p> TFTP server should be activated in <span class="bold"><strong>/etc/xinetd.d/tftp</strong></span> file, and the <span class="bold"><strong>xinetd</strong></span> service started. </p><p> </p><pre class="screen"> @@ -57,7 +57,7 @@ service tftp cps= 100 2 flags= IPv4 }</pre><p> - </p></div><div class="sect3" title="2.3.3.PXE configuration"><div class="titlepage"><div><div><h4 class="title"><a id="id2884561"></a>2.3.3.PXE configuration</h4></div></div></div><p> + </p></div><div class="sect3" title="2.3.3.PXE configuration"><div class="titlepage"><div><div><h4 class="title"><a id="id2514965"></a>2.3.3.PXE configuration</h4></div></div></div><p> </p><pre class="programlisting"> # which interface to use interface=eth0 @@ -97,7 +97,7 @@ tftpdbase=/ # domain=guibland.com domain= </pre><p> - </p></div><div class="sect3" title="2.3.4.DHCPD configuration"><div class="titlepage"><div><div><h4 class="title"><a id="id2884573"></a>2.3.4.DHCPD configuration</h4></div></div></div><p> + </p></div><div class="sect3" title="2.3.4.DHCPD configuration"><div class="titlepage"><div><div><h4 class="title"><a id="id2514977"></a>2.3.4.DHCPD configuration</h4></div></div></div><p> IE of an <span class="bold"><strong>/etc/dhcpd.conf</strong></span> configuration file. Change <span class="bold"><strong>IPADDR_TFTP</strong></span> with the IP address of the TFTP serrver, and the <span class="bold"><strong>NET</strong></span> value. Don't forget to adjust the <span class="bold"><strong>domain-name</strong></span> and the <span class="bold"><strong>domain-name-servers</strong></span>. </p><p> </p><pre class="screen"> @@ -183,7 +183,7 @@ subnet NET.0 netmask 255.255.255.0 { range NET.30 NET.40; } }</pre><p> - </p></div></div></div><div class="sect1" title="3.Setup a node as a golden node"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2884679"></a>3.Setup a node as a golden node</h2></div></div></div><div class="sect2" title="3.1.The rescue.sqfs file"><div class="titlepage"><div><div><h3 class="title"><a id="id2884685"></a>3.1.The rescue.sqfs file</h3></div></div></div><p> + </p></div></div></div><div class="sect1" title="3.Setup a node as a golden node"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2515083"></a>3.Setup a node as a golden node</h2></div></div></div><div class="sect2" title="3.1.The rescue.sqfs file"><div class="titlepage"><div><div><h3 class="title"><a id="id2515089"></a>3.1.The rescue.sqfs file</h3></div></div></div><p> You need the rescue disk (wich contains the <span class="bold"><strong>/ka</strong></span> directory), Just extract this file, and copy all directory in <span class="bold"><strong>/mnt/ka</strong></span>. </p><p> @@ -197,7 +197,7 @@ bin/ dev/ etc/ ka/ lib/ modules/ proc/ sbin/ squashfs-root/ tmp/ usr/ </pre><p> </p><p> Go in the <span class="bold"><strong>/mnt/ka/ka</strong></span> directory, and see all new files available. All those files are needed to do a <span class="bold"><strong>KA</strong></span> duplication process. We will explain now the rule of each of them. You can modify all them, those files will be copied in the directory <span class="bold"><strong>/tmp/stage2</strong></span> of the client node of the duplication process (second step). - </p><div class="sect3" title="3.1.1.ka-d.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2884741"></a>3.1.1.ka-d.sh</h4></div></div></div><p> + </p><div class="sect3" title="3.1.1.ka-d.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2515145"></a>3.1.1.ka-d.sh</h4></div></div></div><p> This is the master script to declare a node as a golden node. This script takes a lot of arguments. This script should be run on the host wich have the <span class="bold"><strong>/mnt/ka</strong></span> directory. </p><pre class="screen"> @@ -213,38 +213,38 @@ bin/ dev/ etc/ ka/ lib/ modules/ proc/ sbin/ squashfs-root/ tmp/ usr/ -r 'grub|lilo' : choose the bootloader (you can add mkinitrd options) ie: ka-d.sh -n 3 -p sda /tmp/desc -X 'sdb|sdc' -r 'grub --with=ata_piix --with=piix'</pre><p> - </p></div><div class="sect3" title="3.1.2.replication.conf"><div class="titlepage"><div><div><h4 class="title"><a id="id2884774"></a>3.1.2.replication.conf</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.2.replication.conf"><div class="titlepage"><div><div><h4 class="title"><a id="id2515179"></a>3.1.2.replication.conf</h4></div></div></div><p> This file contains all variables needed by other scripts. It also tries to get information like IP address. - </p></div><div class="sect3" title="3.1.3.fdisk_to_desc"><div class="titlepage"><div><div><h4 class="title"><a id="id2884786"></a>3.1.3.fdisk_to_desc</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.3.fdisk_to_desc"><div class="titlepage"><div><div><h4 class="title"><a id="id2515190"></a>3.1.3.fdisk_to_desc</h4></div></div></div><p> This script generate the description table of the hard drive disk in the <span class="bold"><strong>/tmp/desc</strong></span> file. This file must follow some rules: one line per partition, with two fields : type of partition and size in megabytes. The type can be linux, swap, extended. Other types can be obtained by appending their hexadecimal number to 'type'. For example linux is the same as type83. The size is either a number of megabytes, or the keyword fill (to take all available space). The logical partitions must have the logical keyword. Do a <span class="bold"><strong>man ka-d</strong></span> for more help. - </p></div><div class="sect3" title="3.1.4.gen_modprobe_conf.pl"><div class="titlepage"><div><div><h4 class="title"><a id="id2884815"></a>3.1.4.gen_modprobe_conf.pl</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.4.gen_modprobe_conf.pl"><div class="titlepage"><div><div><h4 class="title"><a id="id2515219"></a>3.1.4.gen_modprobe_conf.pl</h4></div></div></div><p> This script creates a basic output like the content of the<span class="bold"><strong>/etc/modprobe.conf</strong></span> file. Drawbacks this file must be updated for each new modules available in the kernel (based on the <span class="bold"><strong>kernel/list_modules.pm</strong></span> file). - </p></div><div class="sect3" title="3.1.5.ka-d-client"><div class="titlepage"><div><div><h4 class="title"><a id="id2884838"></a>3.1.5.ka-d-client</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.5.ka-d-client"><div class="titlepage"><div><div><h4 class="title"><a id="id2515242"></a>3.1.5.ka-d-client</h4></div></div></div><p> The <span class="bold"><strong>ka-d-client</strong></span> binary file is used to get stage2 with the <span class="bold"><strong>KA</strong></span> method, and after get the whole system. The important argument is the <span class="bold"><strong>-s</strong></span> session name. A <span class="bold"><strong>KA</strong></span> can only connect to a specific session (getstage2, kainstall ...). The code source is available in the ka-deploy SRPM. - </p></div><div class="sect3" title="3.1.6.ka-d-server"><div class="titlepage"><div><div><h4 class="title"><a id="id2884873"></a>3.1.6.ka-d-server</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.6.ka-d-server"><div class="titlepage"><div><div><h4 class="title"><a id="id2515277"></a>3.1.6.ka-d-server</h4></div></div></div><p> The <span class="bold"><strong>ka-d-server</strong></span> binary file is used to be a <span class="bold"><strong>KA</strong></span> golden node server. Like the <span class="bold"><strong>ka-d-client</strong></span> the session arguments is an important parameter (<span class="bold"><strong>-s session_name</strong></span>). The session name will be <span class="bold"><strong>getstage2</strong></span> to retrieve the stage2 (after the PXE boot) and will be <span class="bold"><strong>kainstall1</strong></span> at duplication process step. If you want to do more than one duplication process of nodes at the same time, you should synchronize the ka_sesion name between the server and the client. The code source is available in the ka-deploy SRPM. - </p></div><div class="sect3" title="3.1.7.ka_replication.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2884922"></a>3.1.7.ka_replication.sh</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.7.ka_replication.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2515326"></a>3.1.7.ka_replication.sh</h4></div></div></div><p> Script launched on the <span class="bold"><strong>KA</strong></span> client (after getting stage2 and probing modules), to do the full process of the <span class="bold"><strong>Ka</strong></span> duplication. This script call other scripts to prepare the node (prepare_node.sh), configure the bootloader (make_initrd_grub or make_initrd_lilo). - </p></div><div class="sect3" title="3.1.8.store_log.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2884946"></a>3.1.8.store_log.sh</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.8.store_log.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2515350"></a>3.1.8.store_log.sh</h4></div></div></div><p> Basic script to store the log of the <span class="bold"><strong>KA</strong></span> duplication process on an FTP server. Adjust to feet your need, and uncomment the line <span class="bold"><strong>#store_log.sh</strong></span> in the <span class="bold"><strong>/mnt/ka/ka/ka_replication.sh</strong></span> file. - </p></div><div class="sect3" title="3.1.9.bootable_flag.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2884974"></a>3.1.9.bootable_flag.sh</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.9.bootable_flag.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2515378"></a>3.1.9.bootable_flag.sh</h4></div></div></div><p> Script to set bootable an HDD using fdisk. First arg must be the HDD device. - </p></div><div class="sect3" title="3.1.10.make_initrd_grub"><div class="titlepage"><div><div><h4 class="title"><a id="id2884985"></a>3.1.10.make_initrd_grub</h4></div></div></div><p> - Restore and reload the Grub bootloader in the <span class="bold"><strong>/mnt/disk</strong></span> directory. It's a very basic script, and perhaps use the <span class="bold"><strong>restore_bootloader</strong></span> of the Mandriva Linux Rescue should be a better idea.</p></div><div class="sect3" title="3.1.11.make_initrd_lilo"><div class="titlepage"><div><div><h4 class="title"><a id="id2885008"></a>3.1.11.make_initrd_lilo</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.10.make_initrd_grub"><div class="titlepage"><div><div><h4 class="title"><a id="id2515390"></a>3.1.10.make_initrd_grub</h4></div></div></div><p> + Restore and reload the Grub bootloader in the <span class="bold"><strong>/mnt/disk</strong></span> directory. It's a very basic script, and perhaps use the <span class="bold"><strong>restore_bootloader</strong></span> of the Mandriva Linux Rescue should be a better idea.</p></div><div class="sect3" title="3.1.11.make_initrd_lilo"><div class="titlepage"><div><div><h4 class="title"><a id="id2515413"></a>3.1.11.make_initrd_lilo</h4></div></div></div><p> Restore and reload the lilo bootloader in the <span class="bold"><strong>/mnt/disk</strong></span> directory. Again it's a very basic script, perhaps we should use the <span class="bold"><strong>restore_bootloader</strong></span> of the Mandriva Linux Rescue. - </p></div><div class="sect3" title="3.1.12.prepare_node.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2885031"></a>3.1.12.prepare_node.sh</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.12.prepare_node.sh"><div class="titlepage"><div><div><h4 class="title"><a id="id2515436"></a>3.1.12.prepare_node.sh</h4></div></div></div><p> This script remove in the futur system the old network's udev rules, old dhcp cache files, launch the script <span class="bold"><strong>gen_modprobe_conf.pl</strong></span> to regenerate an up to date <span class="bold"><strong>/etc/modprobe.conf</strong></span> in the new system, and launch the script to restore the bootloader. If you want to do more action on the installed, system, you can modify this script. - </p></div><div class="sect3" title="3.1.13.send_status.pl"><div class="titlepage"><div><div><h4 class="title"><a id="id2885057"></a>3.1.13.send_status.pl</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.13.send_status.pl"><div class="titlepage"><div><div><h4 class="title"><a id="id2515461"></a>3.1.13.send_status.pl</h4></div></div></div><p> Very basic perl script to open the port 12345, and paste the content of the <span class="bold"><strong>/tmp/ka*</strong></span> file. It also permit the execution of commands on node, if user send a message from the golden node with the <span class="bold"><strong>exec</strong></span> prefix. - </p></div><div class="sect3" title="3.1.14.status_node.pl"><div class="titlepage"><div><div><h4 class="title"><a id="id2885080"></a>3.1.14.status_node.pl</h4></div></div></div><p> + </p></div><div class="sect3" title="3.1.14.status_node.pl"><div class="titlepage"><div><div><h4 class="title"><a id="id2515484"></a>3.1.14.status_node.pl</h4></div></div></div><p> Script to connect to a client node, first arg must be the IP address of the node. You can run command on the node with the <span class="bold"><strong>exec</strong></span> prefix. - </p></div></div></div><div class="sect1" title="4.The golden node, KA server"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2885099"></a>4.The golden node, KA server</h2></div></div></div><p> + </p></div></div></div><div class="sect1" title="4.The golden node, KA server"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2515504"></a>4.The golden node, KA server</h2></div></div></div><p> Now, it is time to build a description of the node partitions. You can use the script <span class="bold"><strong>/mnt/ka/ka/fdisk_to_desc</strong></span> as root user, or your favorite text editor, you can write a file like this one: </p><p> @@ -262,7 +262,6 @@ logical linux fill</pre><p> Type the following to start the ka replication server as root user on the golden node: </p><p> </p><pre class="programlisting"> - <screen> [root@node40 ka]# ./ka-d.sh -n 1 -p sda /root/desc -X sdb -r "grub --with=jfs --with=ata_piix" takembr = desc = sda /root/desc @@ -289,13 +288,13 @@ Socket 5 on port 30764 on node40.guibland.com ready. </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="bold"><strong>-r "grub --with=jfs --with=ata_piix"</strong></span>: use grub bootloader and <span class="bold"><strong>--with=jfs --with=piix</strong></span> mkinitrd option in the chrooted system after the <span class="bold"><strong>KA</strong></span> deploiement</p></li><li class="listitem"><p><span class="bold"><strong>-n nb_nodes</strong></span>: specify how many nodes are clients</p></li><li class="listitem"><p><span class="bold"><strong>-p sda desc</strong></span>: specify the name of the hdd</p></li><li class="listitem"><p><span class="bold"><strong>-x /tmp</strong></span>: exclude <span class="bold"><strong>/tmp</strong></span> directory</p></li><li class="listitem"><p><span class="bold"><strong>-X sdb</strong></span>: exclude <span class="bold"><strong>sdb</strong></span> hdd for the duplication</p></li></ul></div><p> </p><p> Now the golden node is waiting for clients nodes to start replication. - </p></div><div class="sect1" title="5.KA client node"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2885248"></a>5.KA client node</h2></div></div></div><div class="sect2" title="5.1.PXE server (kamethod)"><div class="titlepage"><div><div><h3 class="title"><a id="id2885253"></a>5.1.PXE server (kamethod)</h3></div></div></div><p> + </p></div><div class="sect1" title="5.KA client node"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2515652"></a>5.KA client node</h2></div></div></div><div class="sect2" title="5.1.PXE server (kamethod)"><div class="titlepage"><div><div><h3 class="title"><a id="id2515657"></a>5.1.PXE server (kamethod)</h3></div></div></div><p> We have to configure the PXE to boot by default on <span class="bold"><strong>kamethod</strong></span>. To do this just edit <span class="bold"><strong>/var/lib/tftpboot/X86PC/linux/pxelinux.cfg/default</strong></span> and set <span class="bold"><strong>DEFAULT</strong></span> to kamethod: </p><pre class="screen">DEFAULT kamethod</pre><p> So, next time a node boots, the PXE server will force the node to boot using the kamethod entry. - </p></div><div class="sect2" title="5.2.Stage1 KA method, node waiting stage2"><div class="titlepage"><div><div><h3 class="title"><a id="id2885290"></a>5.2.Stage1 KA method, node waiting stage2 </h3></div></div></div><p> + </p></div><div class="sect2" title="5.2.Stage1 KA method, node waiting stage2"><div class="titlepage"><div><div><h3 class="title"><a id="id2515694"></a>5.2.Stage1 KA method, node waiting stage2 </h3></div></div></div><p> Now, you boot all remaining nodes. The replication process will start once all nodes are up and waiting on the <span class="bold"><strong>KA</strong></span> screen. @@ -304,7 +303,7 @@ Socket 5 on port 30764 on node40.guibland.com ready. server the message <span class="bold"><strong>Can't reach a valid KA server</strong></span> will appear. Each node will try five times to reach the <span class="bold"><strong>KA</strong></span> server, after that the node will reboot. As the node boots on <span class="bold"><strong>kamethod</strong></span>, it will retry until it finds it. - </p></div><div class="sect2" title="5.3.Stage2, the duplication process"><div class="titlepage"><div><div><h3 class="title"><a id="id2885337"></a>5.3.Stage2, the duplication process</h3></div></div></div><p> + </p></div><div class="sect2" title="5.3.Stage2, the duplication process"><div class="titlepage"><div><div><h3 class="title"><a id="id2515741"></a>5.3.Stage2, the duplication process</h3></div></div></div><p> Once all the nodes have found the <span class="bold"><strong>KA</strong></span> server, the first duplication process will start. This step duplicates the <span class="bold"><strong>stage2</strong></span> from the <span class="bold"><strong>/mnt/ka</strong></span> directory @@ -315,7 +314,7 @@ Socket 5 on port 30764 on node40.guibland.com ready. Nodes will rewrite their partition table, then format their filesystems (ReiserFs, XFS, ext2/3/4, JFS). All new partitions will be mounted in the <span class="bold"><strong>/mnt/disk</strong></span> directory. Then, the drive duplication process will begin. On a fast Ethernet switch you can reach speeds of 10MBytes/sec. - </p></div><div class="sect2" title="5.4.Prepare the node"><div class="titlepage"><div><div><h3 class="title"><a id="id2885407"></a>5.4.Prepare the node</h3></div></div></div><p> + </p></div><div class="sect2" title="5.4.Prepare the node"><div class="titlepage"><div><div><h3 class="title"><a id="id2515811"></a>5.4.Prepare the node</h3></div></div></div><p> At the end of the duplication process, each node will chroot its partitions and rebuild its <span class="bold"><strong>/boot/initrd.img</strong></span>, and <span class="bold"><strong>/etc/modprobe.conf</strong></span> files. @@ -323,12 +322,12 @@ Socket 5 on port 30764 on node40.guibland.com ready. SCSI drives and adjusting its network card driver. Before rebooting, each node reinstalls lilo/grub. All your node are now ready, and are clone of master node. - </p></div><div class="sect2" title="5.5.PXE server to local boot"><div class="titlepage"><div><div><h3 class="title"><a id="id2885433"></a>5.5.PXE server to local boot</h3></div></div></div><p> + </p></div><div class="sect2" title="5.5.PXE server to local boot"><div class="titlepage"><div><div><h3 class="title"><a id="id2515837"></a>5.5.PXE server to local boot</h3></div></div></div><p> Don't forget to change the default PXE boot to <span class="bold"><strong>local</strong></span> so node after replication will boot localy. - </p></div></div><div class="sect1" title="6.Step by step from scratch KA duplication"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2885450"></a>6.Step by step from scratch KA duplication</h2></div></div></div><p>We will use a PIV 3gz box as golden node, with a SATA hard drive, and an Intel 82540EM Gigabit Ethernet Controller card. This golden box will be the: PXE, DHCPD, TFTP server. Client nodes are</p><p> + </p></div></div><div class="sect1" title="6.Step by step from scratch KA duplication"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2515854"></a>6.Step by step from scratch KA duplication</h2></div></div></div><p>We will use a PIV 3gz box as golden node, with a SATA hard drive, and an Intel 82540EM Gigabit Ethernet Controller card. This golden box will be the: PXE, DHCPD, TFTP server. Client nodes are</p><p> </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>basic PIV 2.8gz, with a Realtek Semiconductor 8139 network card, and a IDE hard drive disk</p></li><li class="listitem"><p>PE2650 dual XEON 2.4gz, SCSI Hard Drive disk, and NetXtreme BCM5701 Gigabit Ethernet cards</p></li></ul></div><p> - </p><p>Both nodes are configured to boot on their network card.</p><div class="sect2" title="6.1.Golden node side"><div class="titlepage"><div><div><h3 class="title"><a id="id2885485"></a>6.1.Golden node side</h3></div></div></div><p> + </p><p>Both nodes are configured to boot on their network card.</p><div class="sect2" title="6.1.Golden node side"><div class="titlepage"><div><div><h3 class="title"><a id="id2515889"></a>6.1.Golden node side</h3></div></div></div><p> Prepapre the golden node, install all needed tools. </p><p> </p><pre class="programlisting"> @@ -444,7 +443,6 @@ guibland.com valid_lft forever preferred_lft forever [root@localhost ~]# vi /etc/pxe.conf ------------ # which interface to use interface=eth0 default_address=10.0.1.42 @@ -482,7 +480,6 @@ tftpdbase=/ # domain name domain=guibland.com ---------------- [root@localhost ~]# vi /etc/xinetd.d/tftp service tftp @@ -951,7 +948,7 @@ Total data sent = 792 Megs, in 25445 packets Transfer time = 69.904 seconds, throughput = 11.343 Mbytes/second The pipeline was emptied in 4.002 seconds </pre><p> - </p></div><div class="sect2" title="6.2.KA client side"><div class="titlepage"><div><div><h3 class="title"><a id="id2885629"></a>6.2.KA client side</h3></div></div></div><p> + </p></div><div class="sect2" title="6.2.KA client side"><div class="titlepage"><div><div><h3 class="title"><a id="id2516032"></a>6.2.KA client side</h3></div></div></div><p> To get the log of the client node, launch <span class="bold"><strong>/mnt/ka/ka/status_node.pl IPADD</strong></span> on the golden node. </p><pre class="programlisting"> [root@node42 ka]# status_node.pl 10.0.1.111 @@ -1188,7 +1185,7 @@ Total data received = 788 Megs (10.796 Mbytes/sec); BUF :0M End of data flow 10.0.1.111> ftp: connect: Connection refused 10.0.1.111> Local directory now /tmp 10.0.1.111> Not connected. -</pre></div><div class="sect2" title="6.3.Post duplication process"><div class="titlepage"><div><div><h3 class="title"><a id="id2886415"></a>6.3.Post duplication process</h3></div></div></div><p>Now client nodes reboots, so we have to switch PXE to a local boot.</p><p> +</pre></div><div class="sect2" title="6.3.Post duplication process"><div class="titlepage"><div><div><h3 class="title"><a id="id2516818"></a>6.3.Post duplication process</h3></div></div></div><p>Now client nodes reboots, so we have to switch PXE to a local boot.</p><p> </p><pre class="programlisting"> [root@node42 ka]# vi /var/lib/tftpboot/X86PC/linux/pxelinux.cfg/default DEFAULT local |