Creating a second software golden image

[Bill McNAMARA_1]

Ref:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x76cbe7726eccd5118ff10090279cd0f9,00.html


At the moment I have specified my golden image to be just coreOs software.

I would like to have other images created that would append to the coreOs image and be selectably installed.
(not some files may overlap, but acceptably overwritten by the second image.)

For example, soft1base.gz, soft1+x.gz, soft1+y.gz images.

How can I best create these images without going through the process of duplicating my coreOs golden image.

Choices are for the moment, swinstall from bundle disadvantage: lot of reboots, and lot of configuration

advantage: hopefully easier to manipulate (via script?)

What do you suggest?

Later,
Bill

[harry d brown jr]

You can include additional files in the operating system archive if you wish using two different techniques. The first is to edit the file /var/opt/ignite/recovery/makrec.append and add to it the file name, directory name, or software distributor product name you wish to include in the operating system archive. The second technique is to run make_recovery in preview mode with the -p option, manually add files to include and/or exclude from the archive, and resume the make_recovery with the -r option. The manual pages for /opt/ignite/bin/make_recovery and /opt/ignite/bin/ignite appear at the end of this chapter.

http://vig.pearsoned.com/samplechapter/0130125148.pdf

live free or die
harry

ps: I have no clue if this will help you :-(

[Bill McNAMARA_1]

but there's soooo much to read.

Is there not a oneliner to create images of installed software... like

# ignite_put_this_tar_gz -infile image1.gz
# ignite_add_config_choice -image1.gz

Later,
Bill

[harry d brown jr · Accepted solution]

You mean like this:

# make_config -s /var/opt/ignite/Patches -a 800 -c /var/opt/ignite/data/Rel_B.11.00/misc_patch_bundle_cfg

[Bill McNAMARA_1]

If I then modify the /var/opt/ignite/INDEX file to include the new bundle in our "HP-UX B.10.20 archive" configuration:
cfg "HP-UX B.10.20 archive" {
description "The ARCHIVE B.10.20 release with patches."
"/opt/ignite/data/Rel_B.10.20/config"
"/var/opt/ignite/data/Rel_B.10.20/core_700_archive_cfg"
"/var/opt/ignite/data/Rel_B.10.20/patch_bundle_cfg"
"/var/opt/ignite/data/Rel_B.10.20/misc_patch_bundle_cfg"
"/var/opt/ignite/config.local"
}

Will my Default installation always include the misc_patch_bundle depot..

I don't really want that though, I'd prefer to make it optional.

How can I do this?

Later,
Bill

[harry d brown jr]

As long as you don't have load_with_any set, then it should be optional:

* To force install of the patch bundle:

In the sw_sel stanza for the patch bundle in the file /var/opt/ignite/data/Rel_B.10.20/patch_bundle_cfg (you created this file with the make_config command), add the following line:

load_with_any = "golden image"

"golden image" is the name used in the sw_sel stanza in the file /var/opt/ignite/data/Rel_B.10.20/core_700_archive_cfg for our archive 10.20 UX system. The load_with_any line will cause this software selection to always be loaded with the "golden image" archive.

http://www.software.hp.com/products/IUX/docs/sysadm.html#Chapter-4


live free or die
harry

[Bill McNAMARA_1]

okay, finally...

If I want to create an installation script, calling
swinstall network:/var/opt/ignite/BUNDLE

and I know that a few of these products require reboots.

Would this affect my install:
ie
proposed script:
swintall -x patch1
swintall -x patch2
swintall -x patch3
swintall -x patch4
(reboot)
swintall -x patch5
swintall -x patch6
(reboot)
swintall -x patch7

(The make_config does not work because it installs in incorrect order)

Is this possible with ignite?


Later,
Bill

[Bill McNAMARA_1]

Can I do this in the INDEX file?:

cfg "HP-UX B.11.00 Option B" {
description "The ARCHIVE B.11.00 release with extra good stuff."
"/opt/ignite/data/Rel_B.11.00/config"
"/var/opt/ignite/data/Rel_B.11.00/golden.cfg"
"/var/opt/ignite/data/Rel_B.11.00/patch_bundle.cfg"
"/var/opt/ignite/config.local"
#
# in particular this:
#
post_config_script += "/var/opt/ignite/scripts/wierd_install.ksh"
}

[harry d brown jr]

Bill,

The order of the config file is the order inwhich it will install, so yes that will work.

live free or die
harry

[Bill McNAMARA_1]

Thanks for your patience Harry..!

Later,
Bill