Chapter 2. MTA 6.0.1
2.1. New features and improvements
This section describes the new features and improvements of the Migration Toolkit for Applications (MTA) 6.0.1.
MTA no longer requires support for RWX volumes
Previously, MTA required support for RWX volumes, and in version 6.0.1 this is optional. The Tackle CR includes a new configuration option, rwx_supported, a Boolean parameter whose default is true.
-
When this option is set to
true, the MTA Operator creates a cache volume as RWX. This volume is used by Maven as a durable local m2 cache that is shared across tasks. -
When it is set to
false, the Maven m2 cache will be local with each task. You can always configure the Maven cache separately.
If you upgrade from version 6.0.0 to version 6.0.1, you can set this parameter after the upgrade.
2.1.1. Setting the parameter in the OpenShift web console after upgrading to version 6.0.1
You can set the value of rwx_supported in the OpenShift web console after you upgrade to MTA 6.0.1.
Procedure
-
Log into the OpenShift web console, click Operators
Installed Operators Migration Toolkit for Applications Operator Tackle, and then click the Tackle instance. - Click YAML view.
-
Add
rwx_supportedto the CR settings that are listed in thespecsection, and set its value tofalse. - Click Save.
2.1.2. Setting the parameter in the Tackle Custom Resource (CR) using the CLI after upgrading to version 6.0.1
You can set the value of rwx_supported in the Tackle CR using the OpenShift CLI after you upgrade to MTA 6.0.1.
Procedure
- Log into your cluster using the OpenShift CLI.
Set
rwx_supportedtofalseby entering the following command:$ oc patch tackle $(oc get tackle -n openshift-mta|grep -iv name|cut -d " " -f 1) -n openshift-mta --type merge --patch '{"spec":{"rwx_supported": "false"}}'
2.2. Known issues
At the time of release, there are no known issues in this release.
2.3. Resolved issues
At the time of the release, there are no resolved issues for this release.
