You must include your configured guest agent package in your automated installer manifest. You can use the sample automated installer manifest included with your Linux guest agent files and edit it for your own specific environment, or you can include your guest agent package in your existing manifests.

Prerequisites

.

Procedure

  1. Edit your AI manifest to point to the IPS Repository where you published the configured guest agent.

    For example,

    <publisher name="vmware">
        <origin name="http://10.118.192.254:9000/"/>
    </publisher>
  2. Edit the software packages and package groups.

    You must include your configured guest agent package in the software to install list.

          <software_data action="install">
            <name>pkg:/entire@0.5.11-0.175.3</name>
            <name>pkg:/group/system/solaris-large-server</name>
            <name>pkg:/mygugent-pkg</name>
          </software_data>
        </software>
  3. Save and exit.

Results

Your AI manifest includes the vRealize Automation guest agent software package, which is required for Linux Kickstart provisioning.

Customize your Solaris Automated Installation

You download the existing Solaris 11.3x86 AI Boot image and edit the boot grub menu and system configuration profile for your own specifications. You replace the AI manifest with the sample manifest included in your Linux guest agent packages. When you're satisfied with all your changes, you generate a new AI boot image.

  1. Download the Solaris 11.3 x86 Automated Installer Boot Image onto your Solaris 11.3 virtual machine.

  2. Mount the image and copy the files to a new location so you can modify them.

    root@solaris:~# mkdir /root/ai /root/ai/image /mnt/ai
    root@solaris:~# mount -F hsfs $(lofiadm -a /root/ai/sol-11_3-ai-x86.iso) /mnt/ai
    root@solaris:~# cd /mnt/ai
    root@solaris:/mnt/ai# find . -depth -print | cpio -pdm /root/ai/image
  3. Edit the set default configuration in the /root/ai/image/boot/grub/grub.cfg file to point to the "Oracle Solaris 11.3 Automated Install" grub boot menu entry. The first entry in the list is "0", and the second entry is "1."

    # GRUB2 configuration file
    load_video_$target
    terminal_output console
    set timeout=30
    set default="1"
    menuentry "Oracle Solaris 11.3 Automated Install custom" {
            search --no-floppy --file --set=root /.drought.us.oracle.com-2015-10-06T08:49:49.442166
            set kern=/platform/i86pc/kernel/amd64/unix
            echo -n "Loading ${root}$kern: "
            $multiboot $kern $kern -B install=true,aimanifest=prompt
            set gfxpayload="1024x768x32;1024x768x16;800x600x16;640x480x16;640x480x15;640x480x32"
            insmod gzio
            echo -n "Loading ${root}/platform/i86pc/amd64/boot_archive: "
            $module /platform/i86pc/amd64/boot_archive
    }
    menuentry "Oracle Solaris 11.3 Automated Install" {
            search --no-floppy --file --set=root /.drought.us.oracle.com-2015-10-06T08:49:49.442166
            set kern=/platform/i86pc/kernel/amd64/unix
            echo -n "Loading ${root}$kern: "
            $multiboot $kern $kern -B install=true
            set gfxpayload="1024x768x32;1024x768x16;800x600x16;640x480x16;640x480x15;640x480x32"
            insmod gzio
            echo -n "Loading ${root}/platform/i86pc/amd64/boot_archive: "
            $module /platform/i86pc/amd64/boot_archive
    }
    ...
  4. Generate a new grub boot image.

    root@solaris:/mnt/ai# cat /root/ai/image/boot/grub/i386-pc/cdboot.img /root/ai/image/boot/grub/i386-pc/core.img > /root/ai/myboot.img
    root@solaris:/mnt/ai# cp /root/ai/myboot.img /root/ai/image/boot/grub/i386-pc/myboot.img
  5. Mount the solaris.zlib image and copy the files to a new location so you can modify them.

    root@solaris:/mnt/ai# mkdir /root/ai/zlib /mnt/zlib
    root@solaris:/mnt/ai# mount -F hsfs $(lofiadm -a /root/ai/image/solaris.zlib) /mnt/zlib
    root@solaris:/mnt/ai# cd /mnt/zlib
    root@solaris:/mnt/zlib# find . -depth -print | cpio -pdm /root/ai/zlib
  6. Run the sysconfig create-profile command to create a new system profile.

    root@solaris:/mnt/zlib# sysconfig create-profile -o /root/ai
  7. Generate a new copy of solaris.zlib with your changes included and replace the old solaris.zlib.

    root@solaris:/mnt/zlib# cp /root/ai/sc_profile.xml /root/ai/zlib/share/auto_install/sc_profiles/enable_sci.xml
    root@solaris:/mnt/zlib# cd /root/ai/zlib
    root@solaris:~/ai/zlib# mkisofs -o /root/ai/mysolaris.zlib -quiet -N -l -R -U -allow-multidot -no-iso-translate -cache-inodes -d -D -V "compress" /root/ai/zlib/
    root@solaris:~/ai/zlib# lofiadm -C lzma /root/ai/mysolaris.zlib
    root@solaris:~/ai/zlib# cp /root/ai/mysolaris.zlib /root/ai/image/solaris.zlib
  8. Create a copy of the sample manifest file included in your guest agent package and open it for editing.

    root@solaris:/mnt/ai# cp /root/LinuxGuestAgentPkgs/solaris11-amd64/sample_ai_manifest.xml /root/ai/default.xml
    root@solaris:/mnt/ai# vi /root/ai/default.xml
  9. Edit the publisher origin name in the manifest file to point to your Solaris 11.3 virtual machine, which you configured to run as your local IPS repository.

    <publisher name="vmware">
        <origin name="http://10.118.192.254:9000/"/>
    </publisher>
  10. Replace the AI boot image manifest file with your own.

    root@solaris:/mnt/ai# cp /root/ai/default.xml /root/ai/image/auto_install/default.xml
  11. Generate a new AI boot image called myai.iso with all of your changes.

    root@solaris:~/ai/zlib# cd /root/ai/image
    root@solaris:~/ai/image# /usr/bin/mkisofs -d -D -J -l -r -U -relaxed-filenames -b boot/grub/i386-pc/myboot.img -no-emul-boot -boot-load-size 4 -boot-info-table -c .catalog -V "myai.iso" -o /root/ai/myai.iso "/root/ai/image/"
    
  12. Save the resulting myai.iso file to the location required by your hypervisor.

What to do next

Gather the following information so that your IaaS architects can include it in their blueprints:

  1. The name and location of the ISO image.

  2. For vCenter Server integrations, the vCenter Server guest operating system version with which vCenter Server is to create the machine.

Note:

You can create a property group with the property set BootIsoProperties to include the required ISO information. This makes it easier to include this information correctly on blueprints.