diff --git a/assemblies/cli-guide/assembly_installing-mta-cli.adoc b/assemblies/mta-install-title/assembly_installing-mta-cli.adoc similarity index 70% rename from assemblies/cli-guide/assembly_installing-mta-cli.adoc rename to assemblies/mta-install-title/assembly_installing-mta-cli.adoc index 24400697..6de61bb9 100644 --- a/assemblies/cli-guide/assembly_installing-mta-cli.adoc +++ b/assemblies/mta-install-title/assembly_installing-mta-cli.adoc @@ -11,7 +11,7 @@ endif::[] ifdef::context[] [id="installing-mta-cli_{context}"] endif::[] -= Installing {ProductShortName} command-line interface += Installing the {ProductName} command-line interface :context: installing-mta-cli @@ -19,11 +19,11 @@ You can install the {ProductFullName} command-line interface (CLI) on Linux, Win NOTE: You can also install the CLI for use with Docker on Windows. Note, however, that this is a Developer Preview feature only. -include::topics/mta-cli/proc_installing-cli-zip.adoc[leveloffset=+1] +include::topics/mta-install/proc_installing-cli-zip.adoc[leveloffset=+1] -include::topics/mta-cli/proc_installing-mta-disconnected-environment.adoc[leveloffset=+1] +include::topics/mta-install/proc_installing-mta-disconnected-environment.adoc[leveloffset=+1] -include::topics/mta-cli/proc_installing-cli-for-docker.adoc[leveloffset=+1] +include::topics/mta-install/proc_installing-cli-for-docker.adoc[leveloffset=+1] ifdef::parent-context-of-installing-mta-cli[:context: {parent-context-of-installing-mta-cli}] diff --git a/assemblies/mta-install-title/assembly_installing-mta-ui.adoc b/assemblies/mta-install-title/assembly_installing-mta-ui.adoc new file mode 100644 index 00000000..f0ec40d8 --- /dev/null +++ b/assemblies/mta-install-title/assembly_installing-mta-ui.adoc @@ -0,0 +1,34 @@ +:_newdoc-version: 2.18.3 +:_template-generated: 2025-04-10 + +ifdef::context[:parent-context-of-installing-mta-ui: {context}] + +:_mod-docs-content-type: ASSEMBLY + +ifndef::context[] +[id="installing-mta-ui"] +endif::[] +ifdef::context[] +[id="installing-mta-ui_{context}"] +endif::[] += Installing the {ProductName} user interface +:context: installing-mta-ui + +You can install the {ProductFullName} user interface (UI) on all Red Hat OpenShift cloud services and Red Hat OpenShift self-managed editions. + +To create {ProductShortName} instances, you must first install the {ProductShortName} Operator. The {ProductShortName} Operator is a structural layer that manages resources deployed on OpenShift, such as database, front end, and back end, to automatically create an {ProductShortName} instance. + +include::topics/mta-install/ref_persistent-volume-requirements.adoc[leveloffset=+1] + +include::assembly_red-hat-build-of-keycloak.adoc[leveloffset=+1] + +include::topics/mta-install/proc_installing-mta-operator.adoc[leveloffset=+1] + +include::topics/mta-install/proc_creating-mta-instance.adoc[leveloffset=+1] + +include::topics/mta-install/ref_custom-resource-settings.adoc[leveloffset=+1] + + +ifdef::parent-context-of-installing-mta-ui[:context: {parent-context-of-installing-mta-ui}] +ifndef::parent-context-of-installing-mta-ui[:!context:] + diff --git a/assemblies/mta-install-title/assembly_intro-to-mta.adoc b/assemblies/mta-install-title/assembly_intro-to-mta.adoc new file mode 100644 index 00000000..b32aa207 --- /dev/null +++ b/assemblies/mta-install-title/assembly_intro-to-mta.adoc @@ -0,0 +1,35 @@ +:_newdoc-version: 2.18.5 +:_template-generated: 2025-07-31 +:_mod-docs-content-type: ASSEMBLY + +ifdef::context[:parent-context-of-intro-to-mta: {context}] + +ifndef::context[] +[id="intro-to-mta"] +endif::[] +ifdef::context[] +[id="intro-to-mta_{context}"] +endif::[] += Introduction to the {ProductName} + +:context: intro-to-mta + +{ProductFullName} is a set of tools that you can use to accelerate large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. {ProductShortName} looks for common resources and known trouble spots when migrating applications. It provides a high-level view of the technologies used by the application. {ProductShortName} also generates a detailed report that evaluates a migration or modernization path. By using this report, you can estimate the effort required for large-scale projects and reduce the work involved. + +By using the {ProductShortName}, you can perform the following tasks: + +* Use the {ProductShortName} extensive default questionnaire to assess your applications, or create your own custom questionnaire to estimate the difficulty, time, and other resources needed to prepare an application for containerization. You can use the results of an assessment for discussions between stakeholders to determine which applications are suitable for containerization. + +* Analyze applications by applying one or more sets of rules to each application. You can use these rules to determine which specific lines of the application must be modified before the application can be modernized. + +* Examine application artifacts, including project source directories and application archives, and produce an HTML report that highlights areas that require changes. + +include::topics/mta-install/con_mta-features.adoc[leveloffset=+1] + +include::topics/mta-install/con_mta-rules.adoc[leveloffset=+1] + +include::topics/mta-install/con_mta-tools.adoc[leveloffset=+1] + +ifdef::parent-context-of-intro-to-mta[:context: {parent-context-of-intro-to-mta}] +ifndef::parent-context-of-intro-to-mta[:!context:] + diff --git a/assemblies/mta-install-title/assembly_red-hat-build-of-keycloak.adoc b/assemblies/mta-install-title/assembly_red-hat-build-of-keycloak.adoc new file mode 100644 index 00000000..8a64ed33 --- /dev/null +++ b/assemblies/mta-install-title/assembly_red-hat-build-of-keycloak.adoc @@ -0,0 +1,29 @@ +:_newdoc-version: 2.18.5 +:_template-generated: 2025-07-31 +:_mod-docs-content-type: ASSEMBLY + +ifdef::context[:parent-context-of-red-hat-build-of-keycloak: {context}] + +ifndef::context[] +[id="red-hat-build-of-keycloak"] +endif::[] +ifdef::context[] +[id="red-hat-build-of-keycloak_{context}"] +endif::[] += Red Hat Build of Keycloak + +:context: red-hat-build-of-keycloak + +Starting from version 7.3.0, {ProductShortName} uses the link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0[Red Hat Build of Keycloak (RHBK)] instance for user authentication and authorization. An RHBK instance is installed during the installation of the {ProductShortName} user interface. The {ProductShortName} Operator manages the RHBK instance and configures a dedicated realm with necessary roles and permissions. + +You can use the {ProductShortName}-managed RHBK instance to perform advanced RHBK configurations, such as link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html/server_administration_guide/user-storage-federation#adding_a_provider[adding a provider for User Federation] or link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html/server_administration_guide/identity_broker[integrating identity providers]. + +include::topics/mta-install/proc_accessing-rhbk-admin-console.adoc[leveloffset=+1] + +include::topics/mta-install/con_roles-personas-users-permissions.adoc[leveloffset=+1] + + + +ifdef::parent-context-of-red-hat-build-of-keycloak[:context: {parent-context-of-red-hat-build-of-keycloak}] +ifndef::parent-context-of-red-hat-build-of-keycloak[:!context:] + diff --git a/assemblies/mta-install-title/topics b/assemblies/mta-install-title/topics new file mode 120000 index 00000000..9c652798 --- /dev/null +++ b/assemblies/mta-install-title/topics @@ -0,0 +1 @@ +../../topics/ \ No newline at end of file diff --git a/docs/cli-guide/master.adoc b/docs/cli-guide/master.adoc index 049fa225..60915519 100644 --- a/docs/cli-guide/master.adoc +++ b/docs/cli-guide/master.adoc @@ -19,8 +19,6 @@ include::topics/mta-cli/con_intro-to-the-cli.adoc[leveloffset=+1] include::topics/mta-cli/ref_supported-migration-paths.adoc[leveloffset=+1] -include::assemblies/cli-guide/assembly_installing-mta-cli.adoc[leveloffset=+1] - include::assemblies/cli-guide/assembly_analyzing-applications-mta-cli.adoc[leveloffset=+1] include::assemblies/cli-guide/assembly_analyzing-nonjava-applications.adoc[leveloffset=+1] diff --git a/docs/install-guide/assemblies b/docs/install-guide/assemblies new file mode 120000 index 00000000..51bb5102 --- /dev/null +++ b/docs/install-guide/assemblies @@ -0,0 +1 @@ +../../assemblies/ \ No newline at end of file diff --git a/docs/install-guide/master-docinfo.xml b/docs/install-guide/master-docinfo.xml new file mode 100644 index 00000000..5f5a6aab --- /dev/null +++ b/docs/install-guide/master-docinfo.xml @@ -0,0 +1,11 @@ +{WebConsoleBookName} +{DocInfoProductName} +{DocInfoProductNumber} +Installing the Migration Toolkit for Applications user interface and command-line interface + + By using the Migration Toolkit for Applications (MTA), you can accelerate large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. For example, you can inventory, assess, analyze, and manage applications for faster migration to OpenShift through the user interface at both the portfolio and application levels. + + + Red Hat Customer Content Services + + diff --git a/docs/install-guide/master.adoc b/docs/install-guide/master.adoc new file mode 100644 index 00000000..c6b95cad --- /dev/null +++ b/docs/install-guide/master.adoc @@ -0,0 +1,31 @@ +:mta: +include::topics/templates/document-attributes.adoc[] +:_mod-docs-content-type: ASSEMBLY +[id="installing-mta-title"] += Installing the Migration Toolkit for Applications + +:toc: +:toclevels: 4 +:numbered: +:imagesdir: topics/images +:context: installing-mta-title +:installing-mta-title: + +//Inclusive language statement +include::topics/making-open-source-more-inclusive.adoc[leveloffset=+1] + +//Introduction to MTA +include::assemblies/mta-install-title/assembly_intro-to-mta.adoc[leveloffset=+1] + +include::topics/mta-cli/ref_supported-migration-paths.adoc[leveloffset=+1] + +//Installing MTA +include::assemblies/mta-install-title/assembly_installing-mta-ui.adoc[leveloffset=+1] + +include::assemblies/mta-install-title/assembly_installing-mta-cli.adoc[leveloffset=+1] + +include::topics/mta-cli/ref_contributing-to-mta-development.adoc[leveloffset=+1] + + + +:!installing-mta-title: \ No newline at end of file diff --git a/docs/install-guide/topics b/docs/install-guide/topics new file mode 120000 index 00000000..cd717d99 --- /dev/null +++ b/docs/install-guide/topics @@ -0,0 +1 @@ +../topics/ \ No newline at end of file diff --git a/docs/topics/mta-cli/ref_supported-migration-paths.adoc b/docs/topics/mta-cli/ref_supported-migration-paths.adoc index a853be4f..45d83a31 100644 --- a/docs/topics/mta-cli/ref_supported-migration-paths.adoc +++ b/docs/topics/mta-cli/ref_supported-migration-paths.adoc @@ -4,7 +4,7 @@ :_mod-docs-content-type: REFERENCE [id="supported-migration-paths_{context}"] -= Supported {ProductShortName} migration paths += Supported {ProductName} migration paths You can run the {ProductFullName} analysis to assess your applications' suitability for migration to multiple target platforms. {ProductShortName} supports the following migration paths: diff --git a/docs/topics/mta-install/con_mta-features.adoc b/docs/topics/mta-install/con_mta-features.adoc new file mode 100644 index 00000000..51a5255d --- /dev/null +++ b/docs/topics/mta-install/con_mta-features.adoc @@ -0,0 +1,17 @@ +:_newdoc-version: 2.18.5 +:_template-generated: 2025-07-31 +:_mod-docs-content-type: CONCEPT + +[id="mta-features_{context}"] += {ProductShortName} features + +{ProductFullName} provides the following features to simplify upgrades with more migration paths: + +* *Application inventory and assessment modules* to assist organizations in managing, classifying, and tagging their applications while assessing application suitability for deployment in containers, including flagging potential risks for migration strategies. +* *Full integration with source code and binary repositories* to automate the retrieval of applications for analysis along with proxy integration, including HTTP and HTTPS proxy configuration managed in the user interface. +* *Improved analysis capabilities* with new analysis modes, including source and dependency modes that parse repositories to gather dependencies and add these dependencies to the overall scope of the analysis. You can also use a simplified user experience to configure the analysis scope, including open source libraries. +* *Enhanced Role-Based Access Control (RBAC)* powered by link:https://access.redhat.com/products/red-hat-build-of-keycloak[Red Hat build of Keycloak] to define new differentiated personas (administrator, architect, and migrator) with different permissions to suit the needs of each user, including credentials management for multiple credential types. +* *Administration perspective* to provide tool-wide configuration management for administrators. +* *Support for Red Hat OpenShift on AWS (ROSA)* introduced in {ProductShortName} version 7.0.0. +* *Support for Azure Red Hat OpenShift (ARO)* introduced in version MTA 7.0.0. +* *Support for analyzing different languages* introduced in {ProductShortName} version 7.1.0. \ No newline at end of file diff --git a/docs/topics/mta-install/con_mta-rules.adoc b/docs/topics/mta-install/con_mta-rules.adoc new file mode 100644 index 00000000..2eec5579 --- /dev/null +++ b/docs/topics/mta-install/con_mta-rules.adoc @@ -0,0 +1,34 @@ +:_newdoc-version: 2.18.5 +:_template-generated: 2025-07-31 +:_mod-docs-content-type: CONCEPT + +[id="mta-rules_{context}"] += {ProductShortName} rules + +The {ProductFullName} contains rule-based migration tools (analyzers) that you can use to analyze the application user interfaces (APIs), technologies, and architectures used by the applications you plan to migrate. {ProductShortName} analyzer rules use the following rule pattern: + +---- +when(condition) + message(message) + tag(tags) +---- + +You can use the {ProductShortName} rules internally to perform the following tasks: + +* Extract files from archives. +* Decompile files. +* Scan and classify file types. +* Analyze XML and other file content. +* Analyze the application code. +* Build the reports. + +{ProductShortName} builds a data model based on the rule execution results and stores component data and relationships in a graph database. This database can then be queried and updated as required by the migration rules and for reporting purposes. + +[NOTE] +==== +You can create your own custom analyzer rules. You can use custom rules to identify the use of custom libraries or other components that might not be covered by the provided standard migration rules. + +For instructions on how to write custom rules, see link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/rules_development_guide/index[Rules Development Guide]. +==== + + diff --git a/docs/topics/mta-install/con_mta-tools.adoc b/docs/topics/mta-install/con_mta-tools.adoc new file mode 100644 index 00000000..989b95b3 --- /dev/null +++ b/docs/topics/mta-install/con_mta-tools.adoc @@ -0,0 +1,57 @@ +:_newdoc-version: 2.18.5 +:_template-generated: 2025-07-31 +:_mod-docs-content-type: CONCEPT + +[id="mta-tools_{context}"] += {ProductShortName} tools + +You can use the following {ProductFullName} tools for assistance in the various stages of your migration and modernization efforts: + +* *User interface (UI)* ++ +By using the user interface for the {ProductName}, you can perform the following tasks: + +** Assess the risks involved in containerizing an application for hybrid cloud environments on Red Hat OpenShift. +** Analyze the changes that must be made in the code of an application to containerize the application. + ++ +For more information about using the MTA user interface, see link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/user_interface_guide/index[User Interface Guide]. + +* *Command-line interface (CLI)* ++ +The CLI is a command-line tool in the {ProductName} that you can use to assess and prioritize migration and modernization efforts for applications. It provides numerous reports that highlight the analysis without using the other tools. The CLI includes a wide array of customization options. By using the CLI, you can tune {ProductShortName} analysis options or integrate with external automation tools. ++ +For more information about using the CLI, see link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/cli_guide/index[CLI Guide]. + +* *{ProductName} Operator* ++ +By using the {ProductName} Operator, you can install the user interface on OpenShift Container Platform. ++ +For more information about the prerequisites for the MTA Operator installation, see link:https://access.redhat.com/support/policy/updates/openshift_operators[OpenShift Operator Life Cycles]. + +* *IDE add-ons* ++ +You can migrate and modernize applications by using the {ProductName} add-ons for the following applications: ++ +** Eclipse +** Visual Studio Code, Visual Studio Codespaces, and Eclipse Che +** IntelliJ IDEA, both the Community and Ultimate versions + + ++ +You can use these add-on to perform the following tasks: + +** Analyze your projects by using customizable sets of rules. +** Mark issues in the source code. +** Fix the issues by using the provided guidance. +** Use the automatic code replacement, if possible. + + ++ +For more information about using add-ons, see the following documentation: + +** link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/eclipse_plugin_guide/index[Eclipse Plugin Guide] +** link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/intellij_idea_plugin_guide/index[IntelliJ IDEA Plugin Guide] +** link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/visual_studio_code_extension_guide/index[Visual Studio Code Extension Guide] + + diff --git a/docs/topics/mta-install/con_roles-personas-users-permissions.adoc b/docs/topics/mta-install/con_roles-personas-users-permissions.adoc new file mode 100644 index 00000000..0fad932a --- /dev/null +++ b/docs/topics/mta-install/con_roles-personas-users-permissions.adoc @@ -0,0 +1,16 @@ +:_newdoc-version: 2.18.5 +:_template-generated: 2025-07-31 +:_mod-docs-content-type: CONCEPT + +[id="roles-personas-users-permissions_{context}"] += Roles, personas, users, and permissions + +The {ProductFullName} uses three roles, each corresponds to a persona. The roles are already defined in your RHBK instance. You do not need to create them. If you are an {ProductShortName} administrator, you can create users in your RHBK and assign each user one or more roles, one role per persona. Although a user can have more than one role, each role corresponds to a specific persona: + +* The `tackle-admin` role corresponds to the Administrator persona. The administrator has all the permissions that architects and migrators have, along with the ability to create some application-wide configuration parameters that other users can consume, but cannot change or view, for example, Git credentials or Maven `settings.xml` files. + +* The `tackle-architect` role corresponds to the Architect persona. An architect is a technical lead for the migration project who can run assessments and can create and modify applications and information related to them. The architect cannot modify or delete sensitive information, but can consume it. For example, the architect can associate an existing credential to the repository of a specific application. + +* The `tackle-migrator` role corresponds to the Migrator persona. A migrator is a user who can analyze applications, but not create, modify, or delete them. + +{ProductShortName} has two views, *Administration* and *Migration*. Only administrators can access the *Administration* view. Architects and migrators have no access to Administration view, they cannot even see it. Administrators can perform all actions supported by *Migration* view. Architects and migrators can see all elements of *Migration* view, but their ability to perform actions in *Migration* view depends on the permissions granted to their role. \ No newline at end of file diff --git a/docs/topics/mta-install/proc_accessing-rhbk-admin-console.adoc b/docs/topics/mta-install/proc_accessing-rhbk-admin-console.adoc new file mode 100644 index 00000000..0924f80e --- /dev/null +++ b/docs/topics/mta-install/proc_accessing-rhbk-admin-console.adoc @@ -0,0 +1,34 @@ +:_newdoc-version: 2.18.5 +:_template-generated: 2025-07-31 +:_mod-docs-content-type: PROCEDURE + +[id="accessing-rhbk-admin-console_{context}"] += Accessing the RHBK Admin Console + +To perform advanced configurations to an RHBK instance, you must be logged in to the RHBK Admin Console + +.Procedure + +. Retrieve your admin credentials: ++ +[subs="+quotes"] +---- +$ *oc get secret mta-keycloak-rhbk -n openshift-mta -o json| jq -r '.data.password | @base64d'* +---- ++ +The admin credentials for RHBK are stored in the `mta-keycloak-rhbk` secret file in the namespace where you installed MTA. + +. Enter the following URL in your browser: ++ +[subs="+quotes,attributes"] +---- +https://__/auth/admin +---- + +. Access the RHBK Admin Console by entering your credentials. + +[role="_additional-resources"] +.Additional resources +* link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html/server_administration_guide/user-storage-federation#ldap[Configuring LDAP and Active Directory in RHBK] +* link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html/server_administration_guide/red_hat_build_of_keycloak_features_and_concepts[Red Hat Build of Keycloak features and concepts ] + diff --git a/docs/topics/mta-install/proc_creating-mta-instance.adoc b/docs/topics/mta-install/proc_creating-mta-instance.adoc new file mode 100644 index 00000000..6d3d45fa --- /dev/null +++ b/docs/topics/mta-install/proc_creating-mta-instance.adoc @@ -0,0 +1,31 @@ +:_newdoc-version: 2.18.5 +:_template-generated: 2025-08-01 +:_mod-docs-content-type: PROCEDURE + +[id="creating-mta-instance_{context}"] += Creating a MTA instance + +You can use the {ProductFullName} user interface (UI) to assess and analyze your applications to get insights about the adoption process, at both the portfolio and application levels as you inventory, assess, analyze, and manage applications for faster migration to Red Hat OpenShift. + +.Prerequisites + +* You installed the {ProductShortName} Operator on your system. For more information, see xref:installing-mta-operator_installing-mta-ui[Installing the Migration Toolkit for Applications Operator]. +* 4 vCPUs, 8 GB RAM, and 40 GB persistent storage. +* Any cloud services or self-hosted edition of Red Hat OpenShift on versions 4.13-4.15. +* You are logged in as a user with `cluster-admin` permissions. + + +.Procedure +. Click *MTA Operator*. +. Under *Provided APIs*, search for *Tackle* and click *Create Instance*. +. Access the user interface from your browser by using the route exposed by the `mta-ui` application within OpenShift. +. Log in to the user interface instance by using the default credentials: +** User name: `admin` +** Password: `Passw0rd!` +. When prompted, create a new password. + + +[role="_additional-resources"] +.Additional resources +* link:https://access.redhat.com/support/policy/updates/openshift_operators[OpenShift Operator Life Cycles] + diff --git a/docs/topics/mta-cli/proc_installing-cli-for-docker.adoc b/docs/topics/mta-install/proc_installing-cli-for-docker.adoc similarity index 100% rename from docs/topics/mta-cli/proc_installing-cli-for-docker.adoc rename to docs/topics/mta-install/proc_installing-cli-for-docker.adoc diff --git a/docs/topics/mta-cli/proc_installing-cli-zip.adoc b/docs/topics/mta-install/proc_installing-cli-zip.adoc similarity index 87% rename from docs/topics/mta-cli/proc_installing-cli-zip.adoc rename to docs/topics/mta-install/proc_installing-cli-zip.adoc index a91b8da4..ea9edd9f 100644 --- a/docs/topics/mta-cli/proc_installing-cli-zip.adoc +++ b/docs/topics/mta-install/proc_installing-cli-zip.adoc @@ -12,7 +12,7 @@ You can install the {ProductFullName} command-line interface (CLI) by using the * Red Hat Container Registry Authentication for `registry.redhat.io`. Red Hat distributes container images from `registry.redhat.io`, which requires authentication. For more details, see link:https://access.redhat.com/RegistryAuthentication[Red Hat Container Registry Authentication]. + -NOTE: This prerequisite is not applicable for the containerless mode. For more information, see xref:running-the-containerless-mta-cli_analyzing-applications-mta-cli[Analyzing applications in containerless mode]. +NOTE: This prerequisite is not applicable for the containerless mode. For more information, see link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/cli_guide/analyzing-applications-mta-cli_cli-guide#running-the-containerless-mta-cli_analyzing-applications-mta-cli[Analyzing applications in containerless mode]. * You installed Java Development Kit (JDK) version 17 or later. * You set the `JAVA_HOME` environmental variable. diff --git a/docs/topics/mta-cli/proc_installing-mta-disconnected-environment.adoc b/docs/topics/mta-install/proc_installing-mta-disconnected-environment.adoc similarity index 100% rename from docs/topics/mta-cli/proc_installing-mta-disconnected-environment.adoc rename to docs/topics/mta-install/proc_installing-mta-disconnected-environment.adoc diff --git a/docs/topics/mta-install/proc_installing-mta-operator.adoc b/docs/topics/mta-install/proc_installing-mta-operator.adoc new file mode 100644 index 00000000..d7d9c813 --- /dev/null +++ b/docs/topics/mta-install/proc_installing-mta-operator.adoc @@ -0,0 +1,59 @@ +:_newdoc-version: 2.18.3 +:_template-generated: 2025-04-10 +:_mod-docs-content-type: PROCEDURE + +[id="installing-mta-operator_{context}"] += Installing the {ProductShortName} Operator + +To create {ProductFullName} instances, you must first install the {ProductShortName} Operator. The {ProductShortName} Operator is a structural layer that manages resources deployed on OpenShift, such as database, front end, and back end, to automatically create an {ProductShortName} instance. + +.Prerequisites + +* 4 vCPUs, 8 GB RAM, and 40 GB persistent storage. +* Any cloud services or self-hosted edition of Red Hat OpenShift on versions 4.13-4.15. +* 2 RWO persistent volumes (PVs) used by different components. For more information, see xref:[Persistent volume requirements]. +* You are logged in as a user with `cluster-admin` permissions. + + +.Procedure + +. In the Red Hat OpenShift web console, click *Operators* and then click *OperatorHub*. +. Type _{ProductShortName}_ in the *Filter by keyword* field to search for the {ProductShortName} Operator. +. Click the {ProductName} Operator and then click *Install*. +. On the *Install Operator* page, click *Install*. +. Optional: Review and edit the custom resource (CR) settings. ++ +A window for creating CR settings opens automatically after the installation of MTA Operator is complete. The default settings are acceptable. However, make sure to check the system requirements for storage, memory, and cores. ++ +Alternatively, to work directly with the YAML file, click the *YAML* view and review the CR settings that are listed in the spec section of the YAML file. For more details about commonly used CR settings, see xref:custom-resource-settings_installing-mta-ui[Custom resource settings]. ++ +The `spec` section of the YAML file can have the following configuration: ++ +[subs="+quotes"] +---- +kind: Tackle +apiVersion: tackle.konveyor.io/v1alpha1 +metadata: + name: mta + namespace: openshift-mta +spec: + hub_bucket_volume_size: "2.5Gi" + maven_data_volume_size: "2.5Gi" + rwx_supported: "false" +---- +. Verify that the MTA pods are running by clicking *Workloads* and then *Pods* in the *Administration* view. + +.Verification + +* Verify that the MTA Operator appears in the `openshift-mta` project with the status *Succeeded* by clicking *Operators* and then *Installed Operators*. + +[role="_additional-resources"] +.Next steps + +* xref:creating-mta-instance_installing-mta-ui[Create an {ProductShortName} instance]. + +[role="_additional-resources"] +.Additional resources +* link:https://access.redhat.com/support/policy/updates/openshift_operators[OpenShift Operator Life Cycles] + + diff --git a/docs/topics/mta-install/ref_custom-resource-settings.adoc b/docs/topics/mta-install/ref_custom-resource-settings.adoc new file mode 100644 index 00000000..015b0fe3 --- /dev/null +++ b/docs/topics/mta-install/ref_custom-resource-settings.adoc @@ -0,0 +1,32 @@ +:_newdoc-version: 2.18.3 +:_template-generated: 2025-04-10 + +:_mod-docs-content-type: REFERENCE + +[id="custom-resource-settings_{context}"] += Custom resource settings + +The following are the most commonly used custom resource (CR) settings that you can find in the `spec` section of the YAML file. + +.Common custom resource settings +[options="header"] +|==== +|CR name|Default size|Description +|`cache_data_volume_size`|100GB|A size requested for the cache volume. This CR is ignored when the `rwx_supported` option is set to `false`. +|`cache_storage_class`|Default storage class|A storage class used for the cache volume. This CR is ignored when the `rwx_supported` option is set to `false`. +|`feature_auth_required`|True|A flag to indicate whether keycloak authorization is required. When set to `false`, the flag mounts to `“noauth“`, which means only a single user can use the web console. The single user is the default `admin` user. +|`feature_isolate_namespace`|True|A flag to indicate whether namespace isolation by using network policies is enabled. +|`hub_database_volume_size`|10GB|A size requested for the Hub database volume. +|`hub_bucket_volume_size`|100GB|A size requested for the Hub bucket volume. +|`hub_bucket_storage_class`|Default storage class|A storage class used for the bucket volume. +|`keycloak_database_data_volume_size`|1GB|A size requested for the Keycloak database volume. +|`pathfinder_database_data_volume_size`|1GB|A size requested for the Pathfinder database volume. +|`rwx_supported`|True|A flag to indicate whether the cluster storage supports RWX mode. +|rwo_storage_class|NA|A storage class requested for the Tackle RW0 volumes. +|`rhsso_external_access`|False|A flag to indicate whether a dedicated route is created to access the {ProductShortName} managed RHSSO instance. +|`analyzer_container_limits_cpu`|1|A maximum number of CPUs the pod is allowed to use. +|`analyzer_container_limits_memory`|4GB|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|A minimum number of CPUs the pod needs to run. +|`analyzer_container_requests_memory `|4GB|Minimum amount of memory the pod needs to run. +|==== + diff --git a/docs/topics/mta-install/ref_persistent-volume-requirements.adoc b/docs/topics/mta-install/ref_persistent-volume-requirements.adoc new file mode 100644 index 00000000..03ec6546 --- /dev/null +++ b/docs/topics/mta-install/ref_persistent-volume-requirements.adoc @@ -0,0 +1,20 @@ +:_newdoc-version: 2.18.3 +:_template-generated: 2025-04-10 + +:_mod-docs-content-type: REFERENCE + +[id="persistent-volume-requirements_{context}"] += Persistent volume requirements + +To successfully deploy, the {ProductShortName} Operator requires two ReadWriteOnce (RWO) persistent volumes (PVs) used by different components. If the `rwx_supported` configuration option is set to `true`, the {ProductShortName} Operator requires additional two ReadWriteMany (RWX) PVs that are used by Maven and the hub file storage. + +.Required persistent volumes +[options="header"] +|==== +|Name|Default size|Access mode|Description +|`hub database`|10GB |RWO|A hub database that includes information about applications, stakeholders, business services, and other {ProductShortName}-related information. +|`hub bucket`|100GB|RWX|A hub file storage that is required if the `rwx_supported` configuration option is set to `true`. +|`keycloak postgresql`|1GB|RWO|The Keycloak back end database. +|`cache`|100GB|RWX|Maven m2 cache that is required if the `rwx_supported` configuration option is set to `true`. +|==== +