Install Release on OpenShift Cluster

This section describes the procedure of fresh installation of the Release application on OpenShift cluster using operator-based installer. You can install Release on the following platforms:

  • OpenShift cluster on AWS
  • OpenShift cluster on VMWare vSphere

Intended Audience

This guide is intended for administrators with cluster administrator credentials who are responsible for application deployment.

Before You Begin

The following are the prerequisites required to migrate to the operator-based deployment:

  • Docker version 17.03 or later
  • The Openshift oc tool
  • Access to an OpenShift cluster version 4.5 or later
  • Kubernetes cluster configuration

Step 1—Create a folder for installation tasks

Create a folder on your workstation from where you will execute the installation tasks, for example, ReleaseInstallation.

Step 2—Download the Operator ZIP

  1. Download the file from the Deploy/Release Software Distribution site.
  2. Extract the ZIP file to the ReleaseInstallation folder.

Step 3—Update the platform information

To deploy the Release application on the OpenShift cluster, update the Infrastructure file parameters (infrastructure.yaml) in the folder where you extracted the ZIP file with the parameters corresponding to the OpenShift Cluster Configuration (kubeconfig) file as described in the table. You can find the OpenShift cluster information in the default location ~/.kube/config. Ensure the location of the kubeconfig configuration file is your home directory.

Note: The deployment will fail if the infrastructure.yaml is updated with wrong details.

Infrastructure File Parameters OpenShift Cluster Configuration File Parameters Parameter Value
serverUrl server Enter the server URL.
openshiftToken openshiftToken This parameter defines the access token to access your OpenShift cluster.

Step 4—Update the Custom Resource Definitions (dairelease_cr.yaml)

  1. Run the following command to retrieve StorageClass values for Server, Postgres and Rabbitmq:

    oc get sc
  2. Run the keytool command below to generate the RepositoryKeystore:

    keytool -genseckey {-alias alias} {-keyalg keyalg} {-keysize keysize} [-keypass keypass] {-storetype storetype} {-keystore keystore} [-storepass storepass]


    keytool -genseckey -alias deployit-passsword-key -keyalg aes -keysize128 -keypass deployit -keystore /tmp/repository-keystore.jceks -storetype jceks -storepass test123
  3. Convert the Release license and the repository keystore files to the base64 format:

    • To convert the xlrLicense into base64 format, run:

      cat <License.lic> | base64 -w 0
    • To convert RepositoryKeystore to base64 format, run:

      cat <repository-keystore.jceks> | base64 -w 0


    keytool -genseckey -alias deployit-passsword-key -keyalg aes -keysize128 -keypass deployit -keystore /tmp/repository-keystore.jceks -storetype jceks -storepass test123

    Note: The above commands are for Linux-based systems. For Windows, there is no built-in command to directly perform Base64 encoding and decoding. However, you can use the built-in command certutil -encode/-decode to indirectly perform Base64 encoding and decoding.

  4. Update the dairelease_cr file with the mandatory parameters as described in the following table:

    Note: For deployments on test environments, you can use most of the parameters with their default values in the dairelease_cr.yaml file.

    Parameters Description
    KeystorePassphrase The passphrase for repository-keystore file
    Persistence.StorageClass PVC Storage Class for volume
    RepositoryKeystore Convert the repository-keystore file content to Base 64 format.
    ingress.hosts DNS name for accessing UI of Release.
    postgresql.Persistence.StorageClass PVC Storage Class for Postgres
    rabbitmq.Persistence.StorageClass PVC Storage Class for Rabbitmq
    xlrLicense Release license

    Note: For deployments on production environments, you must configure all the parameters required for your Openshift production setup in the dairelease_cr.yaml file. The table in Step 4.5 lists these parameters and their default values, which can be overridden as per your setup requirements and workload. You can override the default parameters, and specify the parameter values.

  5. Update the default parameters as described in the following table based on your requirements:

    Note: The following table describes the default parameters in the dairelease_cr.yaml file. If you want to use your own database and messaging queue, refer Using Existing DB and Using Existing MQ topics, and update the dairelease_cr.yaml file. For information on how to configure AWS RDS with Release, see Configuring AWS RDS.

    Fields to be updated in dairelease_cr.yaml Description Default Values
    AdminPassword The administrator password for Release admin
    ImageRepository Image name xebialabs/xl-release
    ImageTag Image tag 10.2
    Resources CPU/Memory resource requests/limits. User can change the parameter accordingly. NA
    postgresql.install postgresql chart with single instance. Install postgresql chart. If you have an existing database deployment, set install to false. TRUE
    postgresql.postgresqlUsername PostgreSQL user (creates a non-admin user when postgresqlUsername is not postgres) postgres
    postgresql.postgresqlPassword PostgreSQL user password postgres
    postgresql.replication.enabled Enable replication false
    postgresql.postgresqlExtendedConf.listenAddresses Specifies the TCP/IP address(es) on which the server is to listen for connections from client applications *
    postgresql.postgresqlExtendedConf.maxConnections Maximum total connections 500
    postgresql.initdbScriptsSecret Secret with initdb scripts contain sensitive information
    Note: The parameter can be used with initdbScriptsConfigMap or initdbScripts. The value is evaluated as a template.
    postgresql.service.port PostgreSQL port 5432
    postgresql.persistence.enabled Enable persistence using PVC TRUE
    postgresql.persistence.size PVC Storage Request for PostgreSQL volume 50Gi
    postgresql.persistence.existingClaim Provide an existing PersistentVolumeClaim, the value is evaluated as a template. NA
    postgresql.resources.requests CPU/Memory resource requests/limits. User can change the parameter accordingly. cpu: 250m
    Memory: 256Mi
    postgresql.nodeSelector Node labels for pod assignment {}
    postgresql.affinity Affinity labels for pod assignment {}
    postgresql.tolerations Toleration labels for pod assignment []
    UseExistingDB.Enabled If you want to use an existing database, change postgresql.install to false. false
    UseExistingDB.XL_DB_URL Database URL for xl-release NA
    UseExistingDB.XL_DB_USERNAME Database User for xl-release NA
    UseExistingDB.XL_DB_PASSWORD Database Password for xl-release NA
    rabbitmq.install Install rabbitmq chart. If you have an existing message queue deployment, set install to false. TRUE
    rabbitmq.extraPlugins Additional plugins to add to the default configmap rabbitmqjmstopic_exchange
    rabbitmq.replicaCount Number of replica 3
    rabbitmq.rbac.create If true, create & use RBAC resources TRUE
    rabbitmq.service.type Type of service to create ClusterIP
    rabbitmq.persistence.enabled If true, persistent volume claims are created TRUE
    rabbitmq.persistence.size Persistent volume size 8Gi
    UseExistingMQ.Enabled If you want to use an existing Message Queue, change rabbitmq-ha.install to false false
    UseExistingMQ.XLD_TASK_QUEUE_USERNAME Username for xl-deploy task queue NA
    UseExistingMQ.XLD_TASK_QUEUE_PASSWORD Password for xl-deploy task queue NA
    UseExistingMQ.XLD_TASK_QUEUE_URL URL for xl-deploy task queue NA
    UseExistingMQ.XLD_TASK_QUEUE_DRIVER_CLASS_NAME Driver Class Name for xl-deploy task queue NA
    HealthProbes Would you like a HealthProbes to be enabled TRUE
    HealthProbesLivenessTimeout Delay before liveness probe is initiated 60
    HealthProbesReadinessTimeout Delay before readiness probe is initiated 60
    HealthProbeFailureThreshold Minimum consecutive failures for the probe to be considered failed after having succeeded 12
    HealthPeriodScans How often to perform the probe 10
    nodeSelector Node labels for pod assignment {}
    tolerations Toleration labels for pod assignment []
    Persistence.Enabled Enable persistence using PVC TRUE
    Persistence.Annotations Annotations for the PVC {}
    Persistence.AccessMode PVC Access Mode for volume ReadWriteOnce
    Persistence.XldMasterPvcSize XLD Master PVC Storage Request for volume. For production grade setup, size must be changed 10Gi
    Persistence. XldWorkPvcSize XLD Worker PVC Storage Request for volume. For production grade setup, size must be changed 10Gi
    satellite.Enabled Enable the satellite support to use it with Deploy false

Step 5—Set up the CLI

  1. Download the XL-CLI libraries.


    Note: For $VERSION, substitute with the version that matches your product version in the public folder.

  2. Enable execute permissions.

    chmod +x xl
  3. Copy the XL binary to a directory in your PATH.

    echo $PATH
    cp xl /usr/local/bin
  4. Verify the Deploy application release version.

    xl version

Step 6—Set up the Deploy container instance

  1. Run the following command to download and run the Deploy instance:

    docker run -d -e "ADMIN_PASSWORD=admin" -e "ACCEPT_EULA=Y" -p 4516:4516 --name xld xebialabs/xl-deploy:10.2
  2. Go the following URL to access the Deploy application:
    http://<host IP address>:4516/

Step 7— Activate the Release Deployment process

  1. Go to the root of the extracted file and run the following command to activate the Release deployment process:

    xl apply -v -f digital-ai.yaml

Step 8—Verify the deployment status

  1. Check the deployment job completion using XL CLI.
    The deployment job starts the execution of various tasks as defined in the digital-ai.yaml file in a sequential manner. If you encounter an execution error while running the scripts, the system displays error messages. The average time to complete the job is around 1 minute.

    Note: The running time depends on the environment.

    Deployment Status

    To troubleshoot runtime errors, see Troubleshooting Operator Based Installer

Step 9—Verify if the deployment was successful

To verify the deployment succeeded, do one of the following:

  • Open the local Deploy application, go to the Explorer tab, and from Library, click Monitoring > Deployment tasks
  • Run the following command in a terminal or command prompt:

    Deployment Status Using CLI Command

To check the deployment status using CLI, run the following command:

oc get pod

Step 10—Perform sanity checks

Open the Release application and perform the required deployment sanity checks.