Release Notes

Migration Toolkit for Applications 6.0

New features, known issues, and resolved issues

Red Hat Customer Content Services

Abstract

Migration Toolkit for Applications 6.0 accelerates large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to OpenShift via the user interface.
This document describes new features and improvements, known issues, and resolved issues for the Migration Toolkit for Applications, versions 6.0.0 and 6.0.1.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. Introduction

Migration Toolkit for Applications 6.0 accelerates large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to OpenShift via the user interface.

These release notes cover all z-stream releases of MTA 6.0 with the most recent release listed first.

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.
Note

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

  1. Log into the OpenShift web console, click Operators → Installed Operators → Migration Toolkit for Applications Operator → Tackle, and then click the Tackle instance.
  2. Click YAML view.
  3. Add rwx_supported to the CR settings that are listed in the spec section, and set its value to false.
  4. 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

  1. Log into your cluster using the OpenShift CLI.

  2. Set rwx_supported to false by 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.

Chapter 3. MTA 6.0.0

3.1. New features and improvements

This section describes the new features and improvements of the Migration Toolkit for Applications (MTA) 6.0.0.

Application inventory module

New application portfolio driven UI that enables organizations to manage and classify their applications using an extensible tagging model.

Application assessment module

A questionnaire based tool that assesses the suitability of applications for deployment in containers within an enterprise Kubernetes platform, highlighting potential risks that should be considered when deciding which migration strategy to follow.

Administrator perspective

Dedicated perspective to manage tool-wide configuration, it has a similar approach and design to the OpenShift Administrator Perspective.

Enhanced RBAC

Three new differentiated personas with different permissions — Administrator, Architect and Migrator.

Integration with repositories

Full integration with source code (Git, Subversion) and binaries (Maven) repositories to automate the retrieval of applications for analysis.

Credentials management

Secure store for multiple credential types (source control, Maven settings files, proxy). Credentials are managed by Administrators and assigned by Architects to applications.

Proxy integration

HTTP and HTTPS proxy configuration can be managed in the MTA UI.

Enhanced analysis modes

Aside from source and binary analysis modes, now MTA includes the Source + Dependencies mode that parses the POM file available in the source repository to gather dependencies from corporate or public artifact repositories, adding them to the scope of the analysis.

Analysis scope selection

Simplified user experience to configure the analysis scope, with the possibility to force the analysis of known Open Source libraries.

Authless deployment

MTA can now be optionally deployed without Keycloak, allowing full unauthenticated admin access to the tool. This is especially useful when deploying the tool in resource constrained environments like local instances of Minikube, where only a single user would have access to it.

Additional migration paths

New transformation targets have been added to MTA:

  • OpenJDK 11 to OpenJDK 17
  • EAP and Spring Boot applications to Azure App Service

Seamless upgrades

MTA lifecycle is now managed by a new operator with Capability Level II, allowing seamless upgrades between GA versions.

Transaction report

A new transaction report is now available in the application analysis reports. This new option analyzes the application data layer and provides detailed information about how transactions propagate across different layers, expressing it as a sequence of service entries, call graphs and SQL statements.

Important

Transaction report is provided as Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

See Technology Preview features support scope on the Red Hat Customer Portal for information about the support scope for Technology Preview features.

3.2. Known issues

At the time of release, there are no known issues in this release.

3.3. Resolved issues

At the time of the release, there are no resolved issues for this release.

Legal Notice

Copyright © 2023 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.