Upgrading Anaconda Repository for Cloud Pak for Data

Upgrade steps

Extract the installer

First, extract the installer:

./ate-installer-6.1.4-installer.sh -- --help`

You will see the folder ./ate-installer-6.1.4-<HASH>, where <HASH> represents your hash.

cd into the folder:

# Replace <HASH> with your hash
cd ./ate-installer-6.1.4-<HASH>

From here, you can run the upgrade.

Default upgrade command

The following is the default command for upgrading to 6.1.4. Depending on your setup, you might need to add to the command. This might mean appending more directives to your upgrade command, such as those in the following subsections. Run ./install.sh --help to see other options.

# Replace <FQDN> with your fully qualified domain name
# Replace <PREVIOUS_DIR> with the location of the previous installation (where the docker-compose.yml is located)
./install.sh -d <FQDN> --upgrade-from <PREVIOUS_DIR>

For example, say your domain name is team-edition.example.com, and the previous installer is stored in /home/user/installers/ate-installer-6.1.3-xxx. The proper command would be the following:

./install.sh -d team-edition.example.com --upgrade-from /home/user/installers/ate-installer-6.1.3-xxx

HTTPS setup

If your previous setup was for HTTPS, you need to provide the TLS certificate and key:

# Replace <PREV_BASE_DIR> with the base directory where config and file storage are saved. The default value is /opt/anaconda/repo.
# Replace <FQDN> with your fully qualified domain name
# Replace <TLS_CERTIFICATE> and <TLS_KEY> with your TLS cert and key
# Replace <PREVIOUS_DIR> with the location of the previous installation (where the docker-compose.yml is located)
./install.sh -b <PREV_BASE_DIR> -d <FQDN> --tls-cert <TLS_CERTIFICATE> --tls-key <TLS_KEY> --upgrade-from <PREVIOUS_DIR>

Custom implementation considerations

If you’re using a custom implementation, verify that docker-compose.yml or repo.conf (nginx configuration) reflect the upgraded changes.