Determining which components to upgrade (Upgrading from Version 5.2 to Version 5.4)

To successfully upgrade from IBM® Software Hub Version 5.2 to Version 5.4, you must determine which components are installed for the instance of IBM Software Hub that you want to upgrade.

Upgrade phase
  • You are not here. Updating your client workstation
  • You are here icon. Collecting required information
  • You are not here. Preparing to run an upgrade in a restricted network
  • You are not here. Preparing to run an upgrade from a private container registry
  • You are not here. Upgrading prerequisite software
  • You are not here. Upgrading shared cluster components
  • You are not here. Preparing to upgrade an instance
  • You are not here. Upgrading an instance
  • You are not here. Setting up IBM Software Hub
Who needs to complete this task?
Operations team The IBM Software Hub operations team must determine:
  • Which components are installed on the cluster
  • Which components are associated with the instance of IBM Software Hub that you want to upgrade.
When do you need to complete this task?

Repeat as needed Repeat this task for each instance of IBM Software Hub on your cluster.

Ensure that you complete this task before you:
  • Mirror images to your private container registry
  • Prepare to upgrade an instance of IBM Software Hub

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.

Before you determine which components you need to upgrade, review the following guidance:

Environments with multiple instances of IBM Software Hub
You can upgrade each instance of IBM Software Hub on the cluster independently. You can optionally leave different instances at different versions.
Version support
Important: All of the components that are associated with an instance of IBM Software Hub must be installed at the same version. You cannot install services from different releases of IBM Software Hub in the same instance.
Options for upgrading components

You have two options for upgrading the components:

Option Benefits Drawbacks
Upgrade each component individually. If you feel more comfortable running upgrades one at a time, this option gives you more granular control over the upgrade process.

Keep in mind that all of the operators are upgraded at the same time. You cannot upgrade the operators individually.
  • You must complete more steps to successfully install the software on your environment.
  • The order in which you upgrade components is important.
Upgrade all of the components at the same time.
  • You can complete the upgrade in fewer steps.
  • The cpd-cli is designed to upgrade the components in the correct order, which reduces the likelihood of errors.

If you encounter an issue when upgrading a component, you can follow the instructions to upgrade the service separately.

Procedure

To determine which components to upgrade:

  1. Log the cpd-cli in to the Red Hat® OpenShift® Container Platform cluster: 
    ${CPDM_OC_LOGIN}
    Remember: CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command.
  2. Determine whether the scheduling service is installed: 
    oc get scheduling -A
    • If the scheduling service is installed, the command returns information about the project where the scheduling service is installed and the version that is installed.

      Ensure that the COMPONENTS variable in your environment variables script includes the scheduler component.

    • If the scheduling service is not installed, the command returns an empty response.
  3. Determine which services are installed in the instance of IBM Software Hub that you want to upgrade: 
    cpd-cli manage list-deployed-components \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS}

    The command returns a list of the services that are installed in the project.

    Important: If the command returns the ws component, ensure that you add the ws_runtimes component to the your COMPONENTS environment variable when you update your environment variables script.

What to do next

Now that you've identified which components to upgrade, you're ready to complete Determining which models and images to mirror to your private container registry (Upgrading from Version 5.2 to Version 5.4).