Enable Orchestration Pipelines runtime on a remote physical location

Tech preview This is a technology preview and is not supported for use in production environments. Enable use of Orchestration Pipelines runtime by updating the Orchestration Pipelines custom resource (CR) on the primary cluster side.

Before you begin

Best practice: You can run the commands in this task exactly as written if you use set up environment variables for the remote physical location in addition to the installation environment variables script. For instructions, see Setting up environment variables for a remote physical location.
Before you run the commands in this task, ensure that you source the environment variables for:
  • The primary cluster
  • The remote physical location

You must have installed the Orchestration Pipelines runtime on a remote physical location.

Procedure

  1. Log the cpd-cli in to the Red Hat® OpenShift® Container Platform cluster on the primary cluster side: 
    ${REMOTE_CPDM_OC_LOGIN}
    Remember: REMOTE_CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command when you are connecting to a remote cluster.
  2. Update Orchestration Pipelines CR: 
    cpd-cli manage update-cr \
--components=ws_pipelines \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--patch='{\"enableTaskRunManager\":True}'
    Orchestration Pipelines is upgraded when the update-cr command returns:
    [SUCCESS]... The update-cr command ran successfully

What to do next

Now that you've enabled the remote Orchestration Pipelines flag in CR, you're ready to set Orchestration Pipelines environments that are the same as DataStage. See Setting Pipelines environment definitions.