Deploying HSTS using the IBM Cloud Pak Platform UI

Create a High-Speed Transfer Server instance by using the Platform UI.

Requirements

To create an High-Speed Transfer Server (HSTS) service instance by using the Platform UI:

  • Complete the prerequisites. For more information, see Before you begin.
  • Install Cloud Pak for Integration, including the HSTS operator. For more information, see Installing the operators by using the Red Hat OpenShift console.
  • When deploying multiple HSTS instances, use a unique name for each namespace (project) that you create.
  • If your cluster is not connected to the internet, use a bastion host to mirror the images to a registry in your network-restricted environment. For more information, see Mirroring images for an air-gapped cluster.
  • If your environment does not provide public IP addresses for worker nodes, you must use Aspera Proxy to allow transfers from clients to the HSTS instance, which requires additional configuration of your HSTS instance. See Using Aspera Proxy with HSTS.

Procedure

  1. Log in to Platform UI.
  2. Click Integration Instances.
  3. Click Create an instance.
  4. Select High speed transfer server and click Next.
  5. Select one of the following options: Quick start, Development, or Production and then click Next.
  6. Make sure the UI Form perspective is selected for the configuration option.

    The UI Form view gives the standard configuration options and is selected by default. The YAML view opens an editor where you can add the parameters and values to configure HSTS.

  7. In the Details section:
    1. Add the Instance name.
      Note: The instance name can be changed. If you don't change your instance name, the default name of the instance is the type of configuration template you selected: quickstart, Development, or Production.
    2. Add the Namespace.
      Important: If you selected a single namespace-scoped deployment, the option to change the Namespace for the instance (operand) is disabled.
  8. In the License section:
    1. Enable the Accept License checkbox to accept the conditions of your license.
    2. In the Aspera License field, enter your license.
    3. From the License Use drop-down, select your license use type (for AsperaProduction or AsperaNonProduction use).
      Note: To obtain full HSTS performance, you need an Aspera production environment license.
  9. In the Redis section, add your Redis configuration:
    • If you want to use Redis, Sentinel, Redis tls, or Persistence, enter the configuration information.
      Important: When you need to upgrade Cloud Pak for Integration, you will not be able to perform the upgrade until you perform a backup and restore of the Redis database (in other words, the database needs to be relocated).
  10. In the Storage section, add your storage configuration:
    1. Click the YAML perspective tab to assign the Claim name. This refers to the persistent volume storage used when transferring files. For example,
      claimName: hsts-transfer-pvc
           mountPath: /data/
    2. From the Storage class drop-down menu, select the storage and make sure that the storage supports ReadWriteMany so you can use it for the claim.
    3. Enable the Delete Claim checkbox if you want the claim to be deleted when the instance is deleted.
    4. In the Size field, enter the total amount of storage that is required for this volume.
    5. In the Mount Path field, change the name if you want to use a different one.

      The mountPath specification is required; it defines where the storage is mounted to the pod.

  11. The latest instance version is selected by default. If you want to change to an earlier version, enter a different value. For more information, see High-Speed Transfer Server (HSTS) operator and instance versions.

  12. Add the Node API credentials to your YAML file by switching the configuration option.
    Note: The HSTS operator automatically creates the HSTS Node API credentials. The credentials consist of a unique Node API username and password, which are stored in a secret called your_deployment_name-asperanoded-admin. If you want to change the credentials (username and password) see: Optional: Create an Aspera node credentials secret.
    For example,
    credentials:
        secretName: mySecretName
        user: NODE_USER
        pass: NODE_PASS
  13. Click Create. When the entry in the Status column displays Ready, HSTS is running.

Next

Initiating high-speed transfers