MAS DevOps Ansible Collection Ansible CLI
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_contentsourcepolicy 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

suite_db2_setup_for_manage¤

This role shouldn't need to exist, it should be part of the Manage operator, but is not so we have to do it as a seperate step in the install flow for now. The role will perform some initial setup on the Db2 instance that is needed to prepare it for use with the Manage application and supports both CP4D version 3.5 and 4.0.

The role will copy a bash script (setupdb.sh) into the Db2 pod and execute it inside the container, this script will perform a number of configuration changes to the database as well as configuring the tablespaces for Maximo Manage because the operator is not yet able to do this itself.

Role Variables¤

db2_instance_name¤

The name of the db2 instance to execute the setup in.

db2_namespace¤

The namespace where the Db2 instance is running.

db2_username¤

The username that will be used to connect to the database specified by db2_dbname.

db2_dbname¤

The name of the database in the instance to connect to when executing the setup script.

db2_schema¤

The name of the Manage schema where the hack should be targeted in.

db2_tablespace_data_size¤

The size of the tablespace data in the database.

db2_tablespace_index_size¤

The size of the tablespace indexes in the database.

db2_config_version¤

Version of the enhanced DB2 parameters, currently support 1.0.0

enforce_db2_config¤

Flag to indicate restart the DB2 instance or not, the enhanced DB2 parameters required restart DB2 instance, this will cause downtime, should execute during customer maintenance window or newly created DB2 instance if set to True

Example Playbook¤

- hosts: localhost
  any_errors_fatal: true
  vars:
    db2_instancename: mydb2

    db2_namespace: db2u
    db2_config_version: "1.0.0"

    # It will cause downtime if set to true, please be careful.
    enforce_db2_config: true
  roles:
    - ibm.mas_devops.suite_db2_setup_for_manage

License¤

EPL-2.0