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 Update Playbook Content Preparation Usage

OneClick Update¤

This playbook will update the IBM Maximo Operator Catalog on your OpenShift cluster. This will make available new operator updates, which will be automatically applied across the cluster. These updates will not change the functionality of the software in your cluster, they will only carry fixes for security vulnerabilities and bugs.

Note

If you are using the dynamic catalog (ibm-maximo-operator-catalog:v8) this playbook can be ignored, as you will recieve catalog updates in your cluster as soon as they are released. This playbook is specifically for customers who choose to use static catalogs to control the consumption of updates in their cluster.

This is distinct from an upgrade, which will modify the operator subscriptions on your cluster to deliver new features. Performing an updating may make new upgrades available in the cluster, but it will never initiate the upgrade, you must choose when to upgrade.

Playbook Content¤

  1. Install IBM Operator Catalog (1 minute)

Preparation¤

You will need to determine the version of the IBM Maximo Operator Catalog that you wish to update to. Generally speaking, you should update the most recent catalog available.

Important

If you are using a private/mirror registry it is critical that you mirror the images from the updated catalog before you run this playbook, otherwise you will see numerous containers in ImagePullBackoff as the updates are rolled out automatically after the catalog has been updated.

You do not need to worry about translating the image tags to digests to make these catalogs compatible with image mirroring on OpenShift, the role will automatically usse the image digest when it installs any static operator catalog.

Usage¤

Required environment variables¤

Example¤

Only one parameter is required, the new tag of the IBM Maximo Operator Catalog that you wish to use:

export MAS_CATALOG_VERSION=@@MAS_LATEST_CATALOG@@
oc login --token=xxxx --server=https://myocpserver
ansible-playbook ibm.mas_devops.oneclick_update

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