MAS DevOps Ansible Collection Ansible CLI
Edit on GitHub Home Ansible Automation Platform OCP Install Cloud Pak For Data Install Core Add AIBroker Add IoT Add Manage Add Monitor Add Optimizer Add Predict Add Visual Inspection Update Upgrade Uninstall Core Backup & Restore ocp_cluster_monitoring ocp_config ocp_deprovision ocp_efs ocp_github_oauth ocp_login ocp_node_config ocp_provision ocp_roks_upgrade_registry_storage ocp_upgrade ocp_verify appconnect aws_bucket_access_point aws_documentdb_user aws_policy aws_route53 aws_user_creation aws_vpc cert_manager cis common-services configure_manage_eventstreams cos cos_bucket cp4d_admin_pwd_update cp4d cp4d_service db2 dro eck grafana ibm_catalogs kafka nvidia_gpu mongodb ocs sls turbonomic uds mirror_case_prepare mirror_extras_prepare mirror_images mirror_ocp ocp_idms ocp_simulate_disconnected_network registry suite_app_config suite_app_install suite_app_uninstall suite_app_upgrade suite_app_rollback suite_app_backup_restore suite_certs suite_config suite_db2_setup_for_manage suite_dns suite_install suite_manage_attachments_config suite_manage_birt_report_config suite_manage_bim_config suite_manage_customer_files_config suite_manage_imagestitching_config suite_manage_import_certs_config suite_manage_load_dbc_scripts suite_manage_logging_config suite_manage_pvc_config suite_uninstall suite_upgrade suite_rollback suite_verify suite_backup_restore ansible_version_check entitlement_key_rotation gencfg_jdbc gencfg_watsonstudio gencfg_workspace gencfg_mongo
Home Playbooks OneClick Upgrade Playbook Content Preparation Usage

OneClick Upgrade¤

This playbook will upgrade the channel subscriptions for IBM Maximo Application Suite on your OpenShift cluster. Upgrades can only be performed to releases available in the version of the IBM Maximo Pperator Catalog that is installed in your cluster. To update to a newer version of the operator catalog refer to the oneclick-update playbook documentation.

The playbook will attempt to upgrade MAS Core and all installed applications.

Note

If you are using the dynamic catalog (ibm-maximo-operator-catalog:v8) you will always have access to the latest MAS releases, as you will recieve catalog updates in your cluster as soon as they are released. Customers using the static catalogs to control the consumption of updates in their cluster will need to ensure that the version of the catalog they have installed supports the version of MAS that they wish to upgrade to.

Playbook Content¤

  1. Upgrade MAS Core
  2. Verify MAS Core
  3. Upgrade MAS Application (Assist)
  4. Upgrade MAS Application (HP Utilities)
  5. Upgrade MAS Application (IoT)
  6. Upgrade MAS Application (Manage)
  7. Upgrade MAS Application (Monitor)
  8. Upgrade MAS Application (Optimizer)
  9. Upgrade MAS Application (Predict)
  10. Upgrade MAS Application (Safety)
  11. Upgrade MAS Application (Visual Inspection)

Preparation¤

If you are using a private/mirror registry it is critical that you mirror the images for the new release before you run this playbook, otherwise you will see numerous containers in ImagePullBackoff as the updates are rolled out automatically after the subscription has been changed, if you have not mirrored the new images the subscription change itself may fail if the operator bundle is not on your private registry.

Usage¤

Required Parameters¤

Optional Parameters¤

If you provide no values for MAS Core or the individual applications, the roles will attempt to upgrade to the next level of MAS and upgrade applications to the latest version supported by the installed version of MAS Core (after upgrading MAS Core).

Example¤

The simplest way to upgrade MAS is to provide only the instance ID that you wish to upgrade, allowing the roles to determine the correct target version each application.

export MAS_INSTANCE_ID=instance1
oc login --token=xxxx --server=https://myocpserver
ansible-playbook ibm.mas_devops.oneclick_upgrade

You can also explicitly specify the target upgrade:

export MAS_INSTANCE_ID=instance1
export MAS_CHANNEL=8.8.x
export MAS_APP_CHANNEL_IOT=8.5.x
oc login --token=xxxx --server=https://myocpserver
ansible-playbook ibm.mas_devops.oneclick_upgrade

Tip

If you do not want to set up all the dependencies on your local system, you can run the update from inside our container image: docker run -ti --rm --pull always quay.io/ibmmas/cli