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 Roles: Suite Mgmt suite_manage_pvc_config Role Variables Example Playbook Run Role Playbook License

suite_manage_pvc_config¤

This role extends support for configuring persistent volume claims for Manage application.

Note

This role should be executed after Manage application is deployed and activated because it needs Manage up and running prior to configuring the additional persistent volume claims.

The are two options to setup new Manage PVCS:

Role Variables¤

mas_instance_id¤

Required. The instance ID of Maximo Application Suite. This will be used to lookup for Manage application resources.

mas_workspace_id¤

Required. The workspace ID of Maximo Application Suite. This will be used to lookup for Manage application resources.

manage_workspace_cr_name¤

Optional. Name of the ManageWorkspace Custom Resource that will be targeted to configure the new PVC definitions.

mas_app_settings_custom_persistent_volume_pvc_name¤

Optional. Name of the Persistent Volume Claim to be configured.

mas_app_settings_custom_persistent_volume_pv_name¤

Optional. Name of the volume that will be created to store data from the PVC. Make sure your storage class provider supports the name you define. If not sure about what to set, you can leave it unset then a random name will the defined.

mas_app_settings_custom_persistent_volume_pvc_size¤

Optional. Size of the Persistent Volume Claim.

mas_app_settings_custom_persistent_volume_mount_path¤

Optional. Mouth path of the Persistent Volume in the Manage server container.

mas_app_settings_custom_persistent_volume_sc_name¤

Optional. Persistent Volume Claim Storage Class. If not set, it will be automatically defined accordingly to your cluster's available storage classes. Both ReadWriteMany(RWX) and ReadWriteOnce(RWO) are supported.

mas_app_settings_custom_persistent_volume_file_path¤

Optional. Alternatively, this defines a local path pointing the persistent volume definition from a custom file. Sample file definition can be found in files/manage-persistent-volumes-sample.yml.

Example Playbook¤

The following sample can be used to configure new PVCs for an existing Manage application instance.

- hosts: localhost
  any_errors_fatal: true
  vars:
    mas_instance_id: masinst1
    mas_workspace_id: masdev
    mas_app_settings_custom_persistent_volume_sc_name: "ibmc-file-gold-gid"
    mas_app_settings_custom_persistent_volume_pvc_name: "my-manage-pvc"
    mas_app_settings_custom_persistent_volume_pvc_size: "20Gi"
    mas_app_settings_custom_persistent_volume_mount_path: "/MyOwnFolder"
  roles:
    - ibm.mas_devops.suite_manage_pvc_config

The following sample can be used to configure new PVCs for an existing Manage application instance from a custom file definition.

- hosts: localhost
  any_errors_fatal: true
  vars:
    mas_instance_id: masinst1
    mas_workspace_id: masdev
    mas_app_settings_custom_persistent_volume_file_path: "/my-path/manage-pv.yml"
  roles:
    - ibm.mas_devops.suite_manage_pvc_config

Run Role Playbook¤

After installing the Ansible Collection you can easily run the role standalone using the run_role playbook provided.

```bash export MAS_APP_SETTINGS_CUSTOM_PV_STORAGE_CLASS=ibmc-file-silver-gid export MAS_APP_SETTINGS_CUSTOM_PVC_NAME=my-manage-pvc export MAS_APP_SETTINGS_CUSTOM_PVC_SIZE=20Gi export MAS_APP_SETTINGS_CUSTOM_MOUNT_PATH=/MyOwnDir export MAS_APP_SETTINGS_CUSTOM_PV_FILE_PATH=/my-path/manage-pv.yml

ROLE_NAME='suite_manage_pvc_config' ansible-playbook playbooks/run_role.yml

License¤

EPL-2.0