Upgrading Maximo Application Suite by using static catalog

You can upgrade your Maximo Application Suite by using static catalogs. If you are using the dynamic catalog, then updates are automatically applied as soon as they are released.

Upgrade is the act of switching a Maximo Application Suite installation to a new subscription channel. Upgrade is distinct from an update in which new versions are available on existing subscription channels. New features are available from new subscription channels, while updates to existing functions (including security updates) and bug fixes are available within existing subscription channels.

Before you begin

You can upgrade to a Maximo Application Suite version already supported by the ibm-operator-catalog CatalogSource currently installed in the cluster.

  • If you are using the static catalog and not updated to a catalog that includes the Maximo Application Suite version you want to upgrade to, then you must first update your Maximo Application Suite.
  • If you are using the dynamic catalog, then no action is required. The catalog source automatically updates to the latest Maximo Application Suite version.

Procedure

If you are using a static catalog, first update your catalog that includes the Maximo Application Suite version. You can then upgrade your Maximo Application Suite.

Note: Mirroring the images is a simple but time consuming process.

  1. Optional: Prepare for a disconnected update by mirroring the container images.
    Use the following three modes:
    • direct - mirrors images directly from the source registry to your private registry
    • to-filesystem - mirrors images from the source to a local directory
    • from-filesystem - mirrors images from a local directory to your private registry.
    Run the mirror-images command to mirror images.
    docker run -ti --rm --pull always quay.io/ibmmas/cli mas mirror-images
    Note: Ensure you select the Maximo Application Suite version that is installed in the cluster. If multiple Maximo Application Suite instances are running in the cluster for different versions, then you must run the command multiple times to ensure that you mirror the content for all Maximo Application Suite versions that are used in the cluster.
    When prompted, set the target registry to mirror the image, select the Maximo Application Suite Operator catalog to mirror, and select the subset of content that you want to mirror. You can choose to mirror everything from the catalog, or control exactly what is mirrored to your private registry to reduce the time and bandwidth that is used to mirror the images, and reduce the storage requirements of the registry.
    You can run the mirror-images command in noninteractive mode.
    mas mirror-images \
      -m direct \
      -d /mnt/local-mirror/ \
      -H myprivateregistry.com -P 5000 -u $REGISTRY_USERNAME -p $REGISTRY_PASSWORD \
      -c v8-221129-amd64 -C 8.9.x --mirror-core --mirror-iot --mirror-optimizer --mirror-manage \
      --ibm-entitlement $IBM_ENTITLEMENT_KEY \
      --redhat-username $REDHAT_USERNAME --redhat-password $REDHAT_PASSWORD \
      --no-confirm

    For more information, see Mirror images.

  2. Update Maximo Application Suite.
    Run the mas update command and choose the catalog for update. This command updates the operator catalog that is installed in your cluster, and the Operator Lifecycle Manager (OLM) automatically updates all installed operators to the newest version available on the current subscription channel.
    docker run -ti --rm --pull always quay.io/ibmmas/cli mas update
    Important: You must select a newer catalog than what is already in use. Updating to an older static catalog is not supported.

    You can run the update command in noninteractive mode.

    mas update -c v8-221129-amd64 --no-confirm
  3. Upgrade Maximo Application Suite.
    Run mas upgrade and choose the Maximo Application Suite instance to upgrade. The upgrade automatically detects the installed release, and upgrades to the next available release.
    docker pull quay.io/ibmmas/cli 
    docker run -ti --rm quay.io/ibmmas/cli mas upgrade
    Note: Ensure you select the Maximo Application Suite release that you want to upgrade to instead of the one you are currently using. For example, if you are upgrading from Maximo Application Suite 8.8 to Maximo Application Suite 8.9, use -C 8.9.x.
    You can run the mas upgrade command in noninteractive mode:
    mas upgrade -i inst1 --no-confirm