You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/topics/mta-cli/ref_contributing-to-mta-development.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@
8
8
= Contributing to the {ProductShortName} project
9
9
10
10
[role="_abstract"]
11
-
You can help the {ProductName} to cover most application constructs and server configurations, including yours.
11
+
You can help the {ProductName} to cover most application constructs and server configurations, including yours.
12
12
13
13
You can provide your help with any of the following items:
14
14
@@ -18,7 +18,7 @@ You can provide your help with any of the following items:
18
18
** Write a short description of the problem migration areas.
19
19
** Write a brief overview describing how to solve the problem in migration areas.
20
20
* Try {ProductName} on your application. Make sure to report any issues you meet.
21
-
* Try {ProductName} on your application. Make sure to report any issues you meet.{ProductShortName} uses Jira as its issue tracking system. If you encounter an issue executing {ProductShortName}, submit a link:{JiraWindupURL}[Jira issue].
21
+
* Try {ProductName} on your application. Make sure to report any issues you meet.{ProductShortName} uses Jira as its issue tracking system. If you encounter an issue executing {ProductShortName}, submit a link:{JiraWindupURL}[Jira issue].
22
22
* Contribute to the {ProductName} rules repository:
23
23
** Write a {ProductName} rule to identify or automate a migration process.
24
24
** Create a test for the new rule.
@@ -34,4 +34,4 @@ For more information, see link:{ProductDocRulesGuideURL}[_{RulesDevBookName}_].
Copy file name to clipboardExpand all lines: docs/topics/mta-install/proc_creating-mta-instance.adoc
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
:_mod-docs-content-type: PROCEDURE
4
4
5
5
[id="creating-mta-instance_{context}"]
6
-
= Creating a MTA instance
6
+
= Creating an MTA instance
7
7
8
8
[role="_abstract"]
9
9
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.
@@ -13,19 +13,19 @@ To use the {ProductShortName} UI for assessing and analyzing your applications,
13
13
.Prerequisites
14
14
15
15
* 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].
Copy file name to clipboardExpand all lines: docs/topics/mta-install/proc_installing-mta-operator.adoc
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,30 +6,30 @@
6
6
= Installing the {ProductShortName} Operator
7
7
8
8
[role="_abstract"]
9
-
To create {ProductFullName} instances, you must first install the {ProductShortName} Operator.
9
+
To create {ProductFullName} instances, you must first install the {ProductShortName} Operator.
10
10
11
-
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.
11
+
The {ProductShortName} Operator is a structural layer that manages resources deployed on OpenShift, such as the database, front end, and back end, to automatically create an {ProductShortName} instance.
* Any cloud services or self-hosted edition of Red Hat OpenShift on versions 4.13-4.15.
17
-
* 2 RWO persistent volumes (PVs) used by different components. For more information, see xref:[Persistent volume requirements].
18
-
* You are logged in as a user with `cluster-admin` permissions.
17
+
* 2 RWO persistent volumes (PVs) used by different components. For more information, see link:{mta-URL}/installing_the_migration_toolkit_for_applications/index#persistent-volume-requirements_installing-mta-ui[Persistent volume requirements].
18
+
* You are logged in as a user with `cluster-admin` permissions.
19
19
20
20
21
21
.Procedure
22
22
23
-
. In the Red Hat OpenShift web console, click *Operators* and then click *OperatorHub*.
24
-
. Type _{ProductShortName}_ in the *Filter by keyword* field to search for the {ProductShortName} Operator.
25
-
. Click the {ProductName} Operator and then click *Install*.
26
-
. On the *Install Operator* page, click *Install*.
23
+
. In the Red Hat OpenShift web console, click *Operators* and then click *OperatorHub*.
24
+
. Type _{ProductShortName}_ in the *Filter by keyword* field to search for the {ProductShortName} Operator.
25
+
. Click the {ProductName} Operator and then click *Install*.
26
+
. On the *Install Operator* page, click *Install*.
27
27
. Optional: Review and edit the custom resource (CR) settings.
28
28
+
29
29
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.
30
30
+
31
31
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].
32
-
+
32
+
+
33
33
The `spec` section of the YAML file can have the following configuration:
34
34
+
35
35
[subs="+quotes"]
@@ -44,11 +44,11 @@ spec:
44
44
maven_data_volume_size: "2.5Gi"
45
45
rwx_supported: "false"
46
46
----
47
-
. Verify that the MTA pods are running by clicking *Workloads* and then *Pods* in the *Administration* view.
47
+
. Verify that the MTA pods are running by clicking *Workloads* and then *Pods* in the *Administration* view.
48
48
49
49
.Verification
50
50
51
-
* Verify that the MTA Operator appears in the `openshift-mta` project with the status *Succeeded* by clicking *Operators* and then *Installed Operators*.
51
+
* Verify that the MTA Operator appears in the `openshift-mta` project with the status *Succeeded* by clicking *Operators* and then *Installed Operators*.
Copy file name to clipboardExpand all lines: docs/topics/mta-install/ref_persistent-volume-requirements.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
= Persistent volume requirements
8
8
9
9
[role="_abstract"]
10
-
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.
10
+
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 two additional ReadWriteMany (RWX) PVs that are used by Maven and the hub file storage.
11
11
12
12
.Required persistent volumes
13
13
[cols="25%,25%,25%,25%", options="header"]
@@ -30,7 +30,7 @@ To successfully deploy, the {ProductShortName} Operator requires two ReadWriteOn
0 commit comments