B.2 Using AutoYaST to Install Hot Patches on Managed Devices

You can use AutoYaST where you require customization, or require no user intervention. You do this by using a control file that has the installation and configuration details. You can use the configuration interface of AutoYaST to create the control file and provide it to YaST2 during installation.

You can use AutoYaST to install a ZENworks 7.2 Linux Management Hot Patch along with the operating system installation. You must perform the following tasks in the order listed.

  1. Append the following information to the autoinst.xml to include the add-on path of the ZENworks Linux Management agent:

    <add-on>
<add_on_products config:type="list">
<listentry>
 <media_url>NFS path of the Operating System/zlm-updates</media_url>
 <product>ZLM Hot Patch</product>
<!--      <product>SUSE Linux Enterprise Server 10 SP1</product>-->
 <product_dir>/</product_dir>
</listentry>
</add_on_products>

    IMPORTANT:During the installation process of the SUSE operating system, be sure to select the Clone this system for autoyast check box to automatically generate the template control file (/root/autoinst.xml). If you completed the installation without selecting this check box, you must re-install the operating system and select this check box.

  2. Configure the NFS server. For more information, see the SUSE documentation.

  3. Download the inst-source-utils-2007.5.15-0.3.noarch.rpm file from inst-source-utils and install it. By default, the following files are created under the /usr/bin directory:

    • create_directory.yast
    • create_md5sums
    • create_package_descr
    • createpatch
    • create_repo_for_patch.sh
    • create_update_source.sh

  4. In the create_update_source.sh file, set the values as follows:

    UPDATES=”$SOURCE/zlm-updates”

    NAME=”zlm-updates” where “zlm-update” is the base update source folder required for the ZENworks Linux Management client file.

  5. At the server console prompt, enter ‘create_update_source/install_source_path/’

    where install_source_pathis the installation path for the operating system on the NFS server.

    For example, for the SLES10 SP1 operating system, you must enter the following command: create_update_source/SLES10-SP1-x86_64.

    This creates a folder structure similar to the one shown below.

    zlm-updates
|_______-media.1
|_______content
|_______directory.yast
|_______-setup
           |__-descr
|_______-suse
           |____-i386
           |____-i486
           |____-i586
           |____-i686
           |____-noarch
           |____-x86_64

  6. Copy both the ZENworks Linux Management packages and the ZENworks Linux Management - client RPMs hot patch to the new zlm-update source. Each architecture must be copied to the corresponding directories.

    For example, you must copy i586 RPMs to the i586 directory.

  7. After copying both the ZENworks Linux Management packages and the hot patch ZENworks Linux Management - client RPMs, you must delete the earlier versions of the same RPM.

  8. At the server console prompt, go to /install_source_path/zlm-update/suse, then enter the create_package_descr-x /setup/descr command.

  9. At the server console prompt, go to the /install_source_path/zlm-update/suse/setup/descr prompt, then enter the create_directory_yast. command.

    IMPORTANT:Make sure to include a period at the end of the command.

  10. At the server console prompt, go to the /install_source_path/zlm-update/suse/ setup/descr prompt, then enter the create_md5sums command.

  11. At the /install_source_path/ prompt, enter the touch command to create an add_on_products file with the following content:

    nfs://install_source_path/zlm-update

  12. Edit the packages section in the control file to include the ZENworks Linux Management client package details.

    For example:

    <package>liby2util</package>
<package>libzypp</package>
<package>libzypp-zmd-backend</package>
<package>novell-zenworks-install</package>
<package>novell-zenworks-utilities</package>
<package>novell-zenworks-zmd-actions</package>
<package>novell-zenworks-zmd-gconfpolicyenforcers</package>
<package>novell-zenworks-zmd-oem</package>
<package>novell-zenworks-zmd-policyenforcers</package>
<package>novell-zenworks-zmd-policymanagers</package>
<package>novell-zenworks-zmd-settings</package>
<package>novell-zenworks-zmd-tess</package>
<package>rug</package>
<package>yast2</package>
<package>yast2-core</package>
<package>yast2-country</package>
<package>yast2-ncurses</package>
<package>yast2-packager</package>
<package>yast2-perl-bindings</package>
<package>yast2-pkg-bindings</package>
<package>yast2-qt</package>
<package>yast2-slp</package>
<package>zen-updater</package>
<package>zmd</package>
<package>zmd-inventory</package>
<package>zypper</package>
<package>novell-zenworks-zlm-release</package>
<package>suseRegister</package>
<package>yast2-inetd</package>
<package>yast2-online-update</package>
<package>yast2-registration</package>

  13. Append the following information to the init-script section in the control file: 

    <init-scripts config:type="list">
<script>
   <filename>init.sh</filename>
   <interpreter>shell</interpreter>
   <source><![CDATA[
   #!/bin/sh
   echo ’Registering to ZLM’
   rug shutdown -f
   rm /var/lib/zmd/services
   /etc/init.d/novell-zmd start
   rug set require-verified-certs false
   rug sa ZLM Server IP                  #zlm server
   echo ’Fnished Registration’
   ]]></source>
</script>
</init-scripts>
</profile>

  14. Prepare an info file for starting the AutoYaST installation. An example of the info file is shown below:

    install: nfs://NFSServerIP:/install_source_path
netdevice: eth0
server: NFSServerIP
serverdir: install_source_path
ip: IP address of the device
netmask: NetMask of the device
gateway: Gateway of the device
nameserver: Servername of the device
autoyast: floppy

  15. Copy both the control file and the info file to a floppy disk. On booting your device, specify the install option as linux autoyast=floppy.