Chapter 3. Installing the Migration Toolkit for Applications user interface

Procedure

1. In the Red Hat OpenShift web console, click Operators OperatorHub.
2. Use the Filter by keyword field to search for MTA.
3. Click the Migration Toolkit for Applications Operator and then click Install.
4. On the Install Operator page, click Install.
5. Click Operators Installed Operators to verify that the MTA Operator appears in the openshift-mta project with the status Succeeded.
6. Click the MTA Operator.

7. Under Provided APIs, locate Tackle, and click Create Instance.

   The Create Tackle window opens in Form view.

8. Review the custom resource (CR) settings. The default choices should be acceptable, but make sure to check the system requirements for storage, memory, and cores.

9. To work directly with the YAML file, click YAML view and review the CR settings that are listed in the spec section of the YAML file.

   The most commonly used CR settings are listed in this table:

   Table 3.2. Tackle CR settings

   Name	Default	Description
   cache_data_volume_size	100 GiB	Size requested for the cache volume; ignored when rwx_supported=false
   cache_storage_class	Default storage class	Storage class used for the cache volume; ignored when rwx_supported=false
   feature_auth_required	True	Flag to indicate whether keycloak authorization is required (single user/“noauth”)
   feature_isolate_namespace	True	Flag to indicate whether namespace isolation using network policies is enabled
   hub_database_volume_size	10 GiB	Size requested for the Hub database volume
   hub_bucket_volume_size	100 GiB	Size requested for the Hub bucket volume
   hub_bucket_storage_class	Default storage class	Storage class used for the bucket volume
   keycloak_database_data_volume_size	1 GiB	Size requested for the Keycloak database volume
   pathfinder_database_data_volume_size	1 GiB	Size requested for the Pathfinder database volume
   maven_data_volume_size	100 GiB	Size requested for the Maven m2 cache volume; deprecated in MTA 6.0.1
   rwx_storage_class	NA	Storage class requested for the Tackle RWX volumes; deprecated in MTA 6.0.1
   rwx_supported	True	Flag to indicate whether the cluster storage supports RWX mode
   rwo_storage_class	NA	Storage class requested for the Tackle RW0 volumes
   rhsso_external_access	False	Flag to indicate whether a dedicated route is created to access the MTA managed RHSSO instance
   analyzer_container_limits_cpu	1	Maximum number of CPUs the pod is allowed to use
   analyzer_container_limits_memory	4GiB	Maximum amount of memory the pod is allowed to use. You can increase this limit if the pod displays OOMKilled errors.
   analyzer_container_requests_cpu	1	Minimum number of CPUs the pod needs to run
   analyzer_container_requests_memory	4GiB	Minimum amount of memory the pod needs to run

   Example YAML file

   kind: Tackle
   apiVersion: tackle.konveyor.io/v1alpha1
   metadata:
     name: mta
     namespace: openshift-mta
   spec:
     hub_bucket_volume_size: "25Gi"
     maven_data_volume_size: "25Gi"
     rwx_supported: "false"

10. Edit the CR settings if needed, and then click Create.
11. In Administration view, click Workloads Pods to verify that the MTA pods are running.
12. Access the user interface from your browser by using the route exposed by the mta-ui application within OpenShift.

13. Use the following credentials to log in:

    • User name: admin
    • Password: Passw0rd!
14. When prompted, create a new password.