Questo contenuto non è disponibile nella lingua selezionata.

Chapter 12. Generating assets for application deployment in user interface


To create different assets (manifests) required to deploy applications from Cloud Foundry (CF) instances to Red Hat OpenShift Container Platform or Kubernetes, use asset generation in MTA user interface.

To generate assets, familiarize yourself with the following entities:

  • Archetypes - Archetypes contain one or more criteria tags to identify technologies such as EAP 6. An archetype helps you to classify applications based on technologies common to them. For asset generation, you can plan your migration paths by archetypes because you configure the other asset generation entities in the archetype (for example, target profiles that contain the generators).
  • Generators - A generator takes a templating engine, such as Helm, along with a set of templates as input configuration. Generators use the templates that are defined for a target platform and a migration path to generate deployment assets. When you run an asset generation process, the generator parses the application discovery manifest to create deployment assets.

    For example, the migration path for an EAP 6 application is EAP 8 and the target platform is Kubernetes. A generator can generate the required assets to migrate the EAP 6 application to EAP 8 that is to be deployed on Kubernetes. The assets are generated by parsing the discovery manifest of the EAP 6 application.

  • Target profiles - A target profile represents the target platform to which you want to migrate. It contains a sequence of generators. Through target profiles, you can run more than one generator, with each generator creating assets for a specific migration path. Thus, a target profile enables you to generate assets for multiple migration path-target platform combinations at the same time for a given archetype.

    For example, if you want to create assets to migrate an EAP 6 application as an OpenJDK 21 application and as an EAP 8 application in OpenShift Container Platform (target platform), you can achieve this through a target profile that has two generators, one for each migration path.

  • Application - The application includes the discovery manifest, tags, and the asset repository.

    The configuration retrieval process generates a discovery manifest that contains the platform and runtime configurations of an application deployed in the source platform (CF) instances. During asset generation, the discovery manifest is parsed by generator templates that produce the final assets for deployment.

    The application also contains tags that you must configure as criteria tags in an Archetype.

    The asset repository is where you find the generated assets for deployment in the target platform.

You can reuse generators in different archetypes.

12.1. Configuring a generator

To get templates required to generate different asset manifests, configure generators that contain a repository with these templates.

Prerequisites

  • You installed MTA 8.0.0 operator to access the web console.
  • You are an administrator with access to the Administration mode in the MTA user interface.
  • As an administrator, you configured a source control credential for the template repository (if applicable).

Procedure

  1. In the Administration view, click Generators.

    On the Generators page, you can create, edit, and delete generators.

  2. Click Create new generator.
  3. Configure the following fields:

    1. In the Name field in the opened dialog, enter a unique name for the generator.
    2. Select Helm as the generator.
    3. Click Template repository to expand the section.

      1. Select a Repository type from Git or Subversion.
      2. Optional: Enter the URL of your repository that contains the Helm templates.
      3. Optional: Enter the Branch of your repository.
      4. Optional: Enter the Root path of your repository.
      5. Select the credentials to access your repository if it is private.
    4. Optional: Click Values and enter the new value for an attribute in the discovery manifest as a key-value pair.

      During asset generation, the generator overrides the value of the matching attribute in the discovery manifest with the value you enter.

    5. Optional: Click Parameters to enter parameters and their default values as a key-value pair.

      Parameter fields require user input before the template can generate assets.

      Note

      During template instantiation, parameters take precedence over values, and values take precedence over the configurations present in the discovery manifest.

  4. Click Save. You can click anywhere on the generator row to open the details view that shows the generator configuration details, parameters, and values.

12.2. Configuring a target profile

Create and track the target profiles for a specific archetype in the migration toolkit for applications (MTA) user interface (UI).

The target profile contains one or more generators. Each generator generates assets for different migration paths.

You can configure more than one target profile for the archetype based on the target platforms to which you want to migrate applications of the specific archetype.

The generators are run in a priority order, in which manifests generated by lower priority generators do not override manifests generated by other generators.

Procedure

  1. In the Migration view, click Archetypes.
  2. Click the Options menu ( kebab ) of an archetype, and select Manage target profiles.

    The Target profiles for <archetype-name> appears.

  3. Click Create new target profile.
  4. In the Name field in the opened dialogue, enter a unique name for the target profile.
  5. Click the Tag category field and select the category tag to associate with the tag.
  6. Select specific generators and click the right arrow to move the generator from the Available generators list to the Chosen generators list.
  7. Click Create.

    You can click on the archetype row to open the archetype detail view where the target profiles for the archetype are listed.

12.3. Configuring an asset repository

Configure an asset repository in the migration toolkit for applications (MTA) user interface (UI) to publish generated assets. If you do not configure the asset repository, the application repository is considered the default location for publishing the generated assets.

When you configure the asset repository for an application, you can also associate the Source Control credentials of the asset repository before generating assets. If you do not configure a Source Control credential for the asset repository, MTA considers the source code repository credential as the default Source Control credential for the asset repository.

Procedure

  1. In the Migration view, click Applications.
  2. Click the edit icon ( icon edit ) to update an imported application.
  3. In the Update application dialog, click Asset repository and configure the following details:

    1. Select the Asset repository type from Git or Subversion.
    2. Enter the asset repository URL in the Asset repository field.
    3. Enter the Branch of your repository.
    4. Enter the Root path of your repository.
  4. Click Save and close the Update application dialog.
  5. Click Manage Credentials from the Options menu ( kebab ) of the application.
  6. Select the asset repository credential on the Manage Credentials dialog and close the dialog.

12.4. Generating deployment assets

To prepare your application for deployment to a container platform, generate deployment assets in the migration toolkit for applications (MTA) user interface (UI).

When you generate assets for an application, the generators render manifests for all the migration paths associated with the archetype of the application.

Prerequisites

  • You generated the discovery manifest.
  • You configured the application tags in an archetype.
  • You configured generators and target profile in the archetype.

Procedure

  1. In the Migration view, click Applications.
  2. Click the Options menu ( kebab ) of an application.
  3. Click Generate assets to open the Generate assets dialog.
  4. Select a target profile and click Next.
  5. Click the toggle button to open the JSON view where you can enter the parameter values.
  6. Click Next to review the configurations to generate assets.
  7. Click Generate assets.

    You can view the generated assets in the asset repository that you configured.

Red Hat logoGithubredditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni sulla documentazione di Red Hat

Aiutiamo gli utenti Red Hat a innovarsi e raggiungere i propri obiettivi con i nostri prodotti e servizi grazie a contenuti di cui possono fidarsi. Esplora i nostri ultimi aggiornamenti.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Theme

© 2026 Red Hat
Torna in cima