Automation assets deployment by using the Platform UI

You must complete these prerequisites before you create an Automation assets instance. An Integration Specialist should carry out these tasks:

• The operator for Automation assets is already installed. See Installing the operators with the OpenShift console or Installing the operators with the CLI.

• You must deploy Automation assets in the namespace where the Platform UI is already deployed. If is is not deployed in the same namespace as Platform UI, it will not function properly.

• If you are using the IBM Entitled Registry, a pull secret must exist in the namespace containing an entitlement key. See Applying your entitlement key using the UI (online installation).

• You have provided two different types of storage class for use by the Automation assets:

  • Asset data storage - This requires a File RWX volume. For IBM Cloud File the ibmc-file-gold-gid storage class must be used (specifically the gid variant).

  • Asset metadata storage - This requires a Block RWO volume that meets POSIX requirements and has other characteristics as required by CouchDB persistence storage. For IBM Cloud Block, the ibmc-block-gold storage class must be used. For more information on storage classes in OpenShift, see Understanding persistent storage or Cluster storage.

1. Log in to Platform UI.

2. Click Integration instances.

3. Click Create an instance.

4. Click Automation assets, then click Next.

5. Click the tile for your desired deployment option, then click Next.

6. Set the following fields to configure Automation assets. The UI form perspective is selected by default; it opens a form that lets you view or modify the resource configuration.

   1. In the Name field, enter a name for your instance of Automation assets.

   2. From the Namespace list, select the namespace that contains your Platform UI instance. Automation assets must be deployed in the same namespace as Platform UI to function properly.

   3. For License accept, read through the license agreement and click the toggle if you agree.

   4. For License LI, the correct license is selected by default. For details about specific licenses, see the "Table of license versions" section in Licensing.

   5. From the Asset data storage class list, select one of the compatible Matching storage classes.

   6. From the Asset metadata storage class list, select one of the compatible Matching storage classes.

   7. For Version, the optimal channel is selected by default. For more information on operator and resource version compatibility, see Operator channel versions for this release.

   If you need advanced configuration options, consult Using Automation assets. The Advanced settings toggle is not needed for most common installations.

7. Click Create to initiate deployment. You are redirected to the "“Integration instances" page. Automation assets begins installing and is initially in the Pending state. Click Pending to check the progress of the deployment. When the deployment completes, the status changes to Ready.

   

When ready, click the name of the instance you need to access. Your Automation assets is auto-initialized with a catalog.

To learn what you can do with Automation assets, see Using Automation assets.

For information about known issues, workarounds, and troubleshooting information, see Known Limitations.