Steps to deploy callhome

Redeploying the IIAS callhome container

This section outlines a method for redeploying the IIAS callhome container using Podman and a build artifact from Fixed Central.

Procedure:

SSH into the cluster host:
```
ssh root@{cluster-hostname}
```
Log in to the head node:
```
ssh node0101
```
Disable the CallHome app:
```
ap apps disable CallHome
```
Stop the Platform Manager:
```
apstop -p
```

Stop and rename existing callhome container using Pod man.

podman stop callhome
podman rename callhome old_callhome

After this, please verify Exited and updated name of callhome. For example:

[root@node0101 ~]# podman ps -a
CONTAINER ID  IMAGE                                                                                                   COMMAND         CREATED       STATUS                      PORTS       NAMES
45119005e09b  localhost/ibmdashdb/common:v11.5.9.0-ppc64le                                                                            2 weeks ago   Up 35 hours                             dashDB
18de4fbbab62  localhost/callhome/release-1.0.31.0:1.2.0.0-ppc64le                                                     /usr/sbin/init  2 weeks ago   Exited (137) 4 minutes ago              old_callhome
3ef1724b7ab9  docker-na-public.artifactory.swg-devops.com/hyc-dsp-docker-local/ibmdashdb/common:latest-console-ppcle                  34 hours ago  Up 34 hours                             web_console
[root@node0101 ~]#

Create a working directory and navigate to it:

mkdir /root/callhome_build
mkdir /root/callhome_build_untar
cd /root/callhome_build

Download the build artifact from the Fixed Central.

Verify the file is present:

ls -ltrh /root/callhome_build

Example:

[root@sail62-t14-n1 callhome_build]# ls -ltrh
total 917M
-rw-r--r--. 1 root root 917M Aug 24 04:06 1.0.31.0-callhome-Special-Build-IM-IIAS-fp350-ppc64le.tar.gz

Untar the build content in /root/callhome_build_untar directory to avoid confusion.

tar -xzvf 1.0.31.0-callhome-Special-Build-IM-IIAS-fp350-ppc64le.tar.gz -C  ../callhome_build_untar/

Example:

tar -xzvf 1.0.31.0-callhome-Special-Build-IM-IIAS-fp350-ppc64le.tar.gz -C  ../callhome_build_untar/
callhome_image-1.2.0.1-20250822025845b4-release-1.2.0.1-sb.ppc64le.tar.gz

Verify the file is present:

ls -ltrh /root/callhome_build_untar

Example:

[root@sail62-t14-n1 ~]# ls -ltrh /root/callhome_build_untar
total 921M
-rw-r--r--. 1 root root 921M Aug 22 06:06 callhome_image-1.2.0.1-20250822025845b4-release-1.2.0.1-sb.ppc64le.tar.gz
[root@sail62-t14-n1 ~]#

Deploy the callhome container using apinit:

Syntax:

apinit callhome -f /root/callhome_build_untar/<callhome_tar> -e /opt/ibm/appliance/storage/head/dashdb.env -d --log  /root/callhome_build_untar/callhome_deploy-`date +%Y%m%d%H%m%s`.log

Example: If tar name is callhome_image-1.2.0.1-20250822025845b4-release-1.2.0.1-sb.ppc64le.tar.gz

/opt/ibm/appliance/platform/container-api/bin/apinit callhome -f /root/callhome_build_untar/callhome_image-1.2.0.1-20250822025845b4-release-1.2.0.1-sb.ppc64le.tar.gz -e /opt/ibm/appliance/storage/head/dashdb.env -d --log  /root/callhome_build_untar/callhome_deploy-`date +%Y%m%d%H%m%s`.log

If apinit takes longer than expected, check logs:
```
cd /root/callhome_build_untar
```
Look for log files starting with apinit and the latest timestamp.
Start the Platform Manager:
```
apstart -p
```
Enable the CallHome app:
```
ap apps enable CallHome
```