Downloading CASE packages before running IBM Software Hub installation commands in a restricted network

If you will run the IBM Software Hub installation commands in a restricted network, you must have the CASE packages for the components that you plan to install on the client workstation from which you will run the installation commands.

Installation phase

Setting up a client workstation
Setting up a cluster
Collecting required information
Preparing to run installs in a restricted network
Preparing to run installs from a private container registry
Preparing the cluster for IBM Software Hub
Preparing to install an instance of IBM Software Hub
Installing an instance of IBM Software Hub
Setting up the control plane
Installing solutions and services

Who needs to complete this task?

All administrators Cluster administrators, registry administrators, and instance administrators must complete this task.

When do you need to complete this task?

In a restricted network, you must ensure that you have the CASE packages for the components that you plan to install before you complete the following tasks:

Repeat as needed Complete this task on each workstation that will be used to complete one or more of the preceding tasks.

Alternatively, you can complete this task once and transfer the CASE packages to each workstation from which you will complete installation tasks.

Before you begin

Best practice: You can run the commands in this task exactly as written if you set up environment variables. For instructions, see Setting up installation environment variables.

Ensure that you source the environment variables before you run the commands in this task.

About this task

You can download the CASE packages from either of the following locations:

GitHub (github.com)
IBM Cloud Pak Open Container Initiative (icr.io)

Important: The client workstation must be able to access the site from which you plan to download the CASE packages.

Procedure

To prepare to run installs in a restricted network:

Download the CASE packages for the components that you plan to install.

Run the appropriate command depending on the site from which you plan to download the CASE packages:

GitHub

cpd-cli manage case-download \
--components=${COMPONENTS} \
--release=${VERSION} \
--patch_id=${PATCH_ID}

IBM Cloud Pak Open Container Initiative

cpd-cli manage case-download \
--components=${COMPONENTS} \
--release=${VERSION} \
--patch_id=${PATCH_ID} \
--from_oci=true

watsonx Assistant and watsonx Orchestrate users only. Download the CASE package for the ibm_events_operator component.

Run the appropriate command depending on the site from which you plan to download the CASE packages:

GitHub

cpd-cli manage case-download \
--components=ibm_events_operator \
--release=${VERSION} \
--patch_id=${PATCH_ID}

IBM Cloud Pak Open Container Initiative

cpd-cli manage case-download \
--components=ibm_events_operator \
--release=${VERSION} \
--patch_id=${PATCH_ID} \
--from_oci=true

IBM Software Hub Control Center users only. Download the CASE package for the ibm_swhcc component.

Run the appropriate command depending on the site from which you plan to download the CASE packages:

GitHub

cpd-cli manage case-download \
--components=ibm_swhcc \
--release=${VERSION} \
--patch_id=${PATCH_ID}

IBM Cloud Pak Open Container Initiative

cpd-cli manage case-download \
--components=ibm_swhcc \
--release=${VERSION} \
--patch_id=${PATCH_ID} \
--from_oci=true

Results

The CASE packages for the specified components are downloaded to the work directory.

Important: If you transfer the CASE packages to other workstations, ensure that you complete the following steps on each workstation:

Change to the directory that contains the work directory.
Set the following permissions on the work directory:
```
chown -R 1001 ./work
chmod -R 775 ./work
```
Restart the container:
```
cpd-cli manage restart-container
```

What to do next

Now that you've downloaded the CASE packages to your client workstation, you're ready to complete Preparing to run IBM Software Hub installs from a private container registry.