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
To successfully deploy, the {ProductShortName} Operator requires 3 RWO persistent volumes (PVs) used by different components. If the `rwx_supported` configuration option is set to `true`, the {ProductShortName} Operator requires an additional 2 RWX PVs that are used by Maven and the hub file storage. The PVs are described in the table below:
19
+
To successfully deploy, the {ProductShortName} Operator requires 2 RWO persistent volumes (PVs) used by different components. If the `rwx_supported` configuration option is set to `true`, the {ProductShortName} Operator requires an additional 2 RWX PVs that are used by Maven and the hub file storage. The PVs are described in the following table:
20
20
21
21
.Required persistent volumes
22
22
[cols="25%,25%,25%,25%", options="header"]
@@ -41,17 +41,13 @@ To successfully deploy, the {ProductShortName} Operator requires 3 RWO persisten
41
41
|RWO
42
42
|Keycloak back end database
43
43
44
-
|`pathfinder postgresql`
45
-
|1 GiB
46
-
|RWO
47
-
|Pathfinder back end database
48
-
49
44
|`cache`
50
45
|100 GiB
51
46
|RWX
52
47
|Maven m2 cache; required if the `rwx_supported` configuration option is set to `true`
53
48
|====
54
49
50
+
[id="installing-mta-operator-and-ui_{context}"]
55
51
== Installing the {ProductName} Operator and the {WebName}
56
52
57
53
You can install the {ProductName} ({ProductShortName}) and the {WebName} on Red Hat OpenShift versions 4.13-4.15.
== Memory requirements for running {ProductShortName} on Red Hat OpenShift Local
214
211
215
212
When installed on https://developers.redhat.com/products/openshift-local/overview[Red Hat OpenShift Local], {ProductShortName} requires a minimum amount of memory to complete its analysis. Adding memory makes the analysis process run faster. The table below describes the {ProductShortName} performance with varying amounts of memory.
@@ -220,7 +217,6 @@ When installed on https://developers.redhat.com/products/openshift-local/overvie
220
217
|Memory (GiB)
221
218
|Description
222
219
223
-
224
220
|`10`
225
221
|{ProductShortName} cannot run the analysis due to insufficient memory
226
222
@@ -264,25 +260,81 @@ To prevent out-of-memory events and protect nodes, use the `--eviction-hard` set
264
260
265
261
The amount of memory available for running pods on this node is 28.9 GiB. This amount is calculated by subtracting the `system-reserved` and `eviction-hard` values from the overall capacity of the node. If the memory usage exceeds this amount, the node starts evicting pods.
266
262
267
-
263
+
[id="rhsso-overview-mta_{context}"]
268
264
== Red Hat Single Sign-On
269
-
{ProductShortName} delegates authentication and authorization to a
Hat Single Sign-On] (RHSSO) instance managed by the {ProductShortName} operator. Aside from controlling the full lifecycle of the managed RHSSO instance, the {ProductShortName} operator also manages the configuration of a dedicated
272
-
https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6/html/server_administration_guide/configuring_realms[realm] that contains all the roles and permissions that {ProductShortName} requires.
265
+
{ProductShortName} delegates authentication and authorization to a https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6[Red Hat Single Sign-On] (RHSSO) instance managed by the {ProductShortName} operator. Aside from controlling the full lifecycle of the managed RHSSO instance, the {ProductShortName} operator also manages the configuration of a dedicated https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6/html/server_administration_guide/configuring_realms[realm] that contains all the roles and permissions that {ProductShortName} requires.
273
266
274
-
If an advanced configuration is required in the {ProductShortName} managed RHSSO instance, such as https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6/html/server_administration_guide/user-storage-federation#adding_a_provider[adding
275
-
a provider for User Federation] or https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6/html/server_administration_guide/identity_broker[integrating
276
-
identity providers], users can log into the RHSSO https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6/html/server_administration_guide/configuring_realms#using_the_admin_console[Admin
277
-
Console] through the `/auth/admin` subpath in the `{LC_PSN}-ui` route. The admin credentials to access the {ProductShortName} managed RHSSO instance can be retrieved from the `credential-mta-rhsso` secret available in the namespace in which the {WebName} was installed.
267
+
If an advanced configuration is required in the {ProductShortName} managed RHSSO instance, such as https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6/html/server_administration_guide/user-storage-federation#adding_a_provider[adding a provider for User Federation] or https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6/html/server_administration_guide/identity_broker[integrating identity providers], users can log into the RHSSO https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6/html/server_administration_guide/configuring_realms#using_the_admin_console[Admin Console] through the `/auth/admin` subpath in the `{LC_PSN}-ui` route. The admin credentials to access the {ProductShortName} managed RHSSO instance can be retrieved from the `credential-mta-rhsso` secret available in the namespace in which the {WebName} was installed.
278
268
279
269
A dedicated route for the {ProductShortName} managed RHSSO instance can be created by setting the `rhsso_external_access` parameter to `True` in the *Tackle CR* that manages the {ProductShortName} instance.
https://access.redhat.com/documentation/en-us/red_hat_single_sign-on/7.6/html/server_administration_guide/red_hat_single_sign_on_features_and_concepts[Red Hat Single Sign-On features and concepts].
{ProductShortName} makes use of three roles, each of which corresponds to a persona:
279
+
280
+
.Roles and personas
281
+
[cols="50%,50%", options="header"]
282
+
|====
283
+
|Role
284
+
|Persona
285
+
286
+
|`tackle-admin`
287
+
|Administrator
288
+
289
+
|`tackle-architect`
290
+
|Architect
291
+
292
+
|`tackle-migrator`
293
+
|Migrator
294
+
|====
295
+
296
+
The roles are already defined in your RHSSO instance. You do not need to create them.
297
+
298
+
If you are an {ProductShortName} administrator, you can create users in your RHSSO and assign each user one or more roles, one role per persona.
299
+
300
+
[id="mta-roles-personas-ui-views_{context}"]
301
+
==== Roles, personas, and access to {WebName} views
302
+
303
+
Although a user can have more than one role, each role corresponds to a specific persona:
304
+
305
+
* Administrator: An 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. Examples: Git credentials, Maven `settings.xml` files.
306
+
307
+
* Architect: A technical lead for the migration project who can run assessments and can create and modify applications and information related to them. An architect cannot modify or delete sensitive information, but can consume it. Example: Associate an existing credential to the repository of a specific application.
308
+
309
+
* Migrator: A user who can analyze applications, but not create, modify, or delete them.
310
+
311
+
As described in xref:mta-ui-interface-views[User interface views], {ProductShortName} has two views, *Administration* and *Migration*.
312
+
313
+
Only administrators can access *Administration* view. Architects and migrators have no access to *Administration* view, they cannot even see it.
314
+
315
+
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.
316
+
317
+
The ability of administrators, architects, and migrators to access the *Administration* and *Migration* views of the {ProductShortName} {WebName} is summarized in the table below:
318
+
319
+
.Roles vs. access to {ProductShortName} views
320
+
[cols=",,,",options="header",]
321
+
|===
322
+
|Menu
323
+
|Architect
324
+
|Migrator
325
+
|Admin
326
+
|Administration
327
+
|No
328
+
|No
329
+
|Yes
330
+
|Migration
331
+
|Yes
332
+
|Yes
333
+
|Yes
334
+
|===
284
335
285
-
=== Roles and Permissions
336
+
[id="mta-roles-permissions_{context}"]
337
+
==== Roles and permissions
286
338
287
339
The following table contains the roles and permissions (scopes) that {ProductShortName} seeds the managed RHSSO instance with:
The {ProductName} ({ProductShortName}) {WebName} has two views:
32
32
33
33
* Administration view
34
34
* Migration view
35
35
36
-
In *Administration* view, you configure the instance environment, working with credentials, repositories, HTTP and HTTPS proxy definitions, custom migration targets, and issue management.
36
+
In *Administration* view, administrators can configure the instance environment, work with credentials and repositories, define HTTP and HTTPS proxies, specify custom migration targets, manage issues, and add custom assessment questionnaires.
37
37
38
-
In *Migration* view, you perform application assessments and analyses, review reports, and add applications for assessment and analysis.
38
+
In *Migration* view, all authorized users can review reports, add applications for assessment and analysis. perform application assessments and analyses, create migration waves, view issues that could potentially impact migration, view the status of analysis and discovery tasks through Task Manager. The permissions of the different user roles -- administrators, architects, and migrators -- vary in this view.
0 commit comments