Ignite-UX and SD-UX interoperability

[Bill McNAMARA_1]

Hi,

I have ignite working nicely with the following style of INDEX:

cfg "HP-UX B.11.00 Oct2001" {
description "HP-UX 11.00 Oct2001"
"/opt/ignite/data/Rel_B.11.00/config"
"/opt/ignite/data/Rel_B.11.00/hw_patches_cfg"
"/opt/ignite/data/Rel_B.11.00/core11.cfg"
"/opt/ignite/data/Rel_B.11.00/extrastuff.cfg"
"/var/opt/ignite/config.local"
}=TRUE

And all goes smoothly.

However, I need to do an installation of some other stuff via swinstall in a script and found that simply adding the
post_config_script+="/var/opt/ignite/scripts/install.ksh"

before the } of the index section does not work.

IGNITE complains of an invalid INDEX file.

Where should I put my script.

It looks like this btw:
(and creating a bundle is not okay)

swinstall -s labatt:/OCMP/SS7Depot/AAA OC-SS7-P294
swinstall -s labatt:/OCMP/SS7Depot/AAA OC-SS7-P396
swcopy -s labatt:/OCMP/SS7Depot/AAA OC-TSC-P315 @ /var/opt/ignite/SS7AAA]

swinstall -x autoreboot=true -s /var/opt/ignite/SS7AAA OC-TSC-P315

swcopy -s labatt:/OCMP/SS7Depot/SS7AAA OC-ISUP-ANSI @ /var/opt/ignite/SS7AAA


A reboot will be required halfway through the script too. Will ignite remember where it left off???

Later,
Bill

[Eugen Cocalea]

Hi,

What happens if you give up the '+' sign at

post_config_script="..."

?

And if you pass reinstall=false or reinstall_files=false for swinstall and recopy=false for swcopy, the first steps of the installation will be skipped anyway after the reboot.

E.

[Michael Roberts_3 · Accepted solution]

Bill,
You can't put the "post_config_script..." directly in the INDEX file.
You would put it in either config.local for all installs to run it
or a config file that is specific for this cfg like
/var/opt/ignite/Rel_B.11.00/OCMP_ANSI_TSU.cfg
then replace your line that has post_config... with
/var/opt/ignite/Rel_B.11.00/OCMP_ANSI_TSU.cfg

On the script itself, there isn't anything in there (besides the "rm"'s)
that can't be handled by standard Ignite mechanisms. The order that the
sw is loaded in can be handled by the load_order keyword.

To load software from the same depot in a specific order you could have
a config file that looks like:
sw_source "tsc app1" {
sd_server="192.20.3.54"
sd_depot_dir="/OCMP/SS7Depot/SS7_AAA"
description = "OCMP depot"
source_format = SD
pre_load_cmd += "
rm -Rf /opt/OCMP /opt/HPOC-Security /var/opt/log/OCMP
"
load_order = 4
}
sw_sel "OC-SS7-AAA" {
description = "OC-SS7-AAA"
sw_source = "tsc app1"
sw_category = "Applications"
sd_software_list = "OC-SS7-AAA"
impacts = "/opt" 454923Kb
}
sw_source "tsc app2" {
sd_server="192.20.3.54"
sd_depot_dir="/OCMP/SS7Depot/SS7_AAA"
description = "OCMP depot"
source_format = SD
load_order = 5
}
sw_sel "OC-SS7-AAA-P122" {
description = "OC-SS7-AAA"
sw_source = "tsc app2"
sw_category = "Applications"
sd_software_list = "OC-SS7-AAA-P122"
post_load_cmd +="
/usr/sbin/swconfig OC-TSC
"
impacts = "/opt" 54923Kb
}

=======
This allows Ignite to be in control of the reboots, (it is happier
that way), and allows for the installation in a particular order.
The config file is more verbose than the script, but it uses supported
Ignite mechanisms.