You can scale the heap memory size of the vRealize Orchestrator server by editing the deployment file.

You can adjust the heap memory size of the vRealize Orchestrator server, so your orchestration environment can manage changing workloads. For example, you can increase the heap memory of your vRealize Orchestrator deployment if you are planning to manage multiple vCenter servers.

Prerequisites

  • Enable SSH access to the vRealize Orchestrator Appliance. See Enable or Disable SSH Access to the vRealize Orchestrator Appliance.
  • Increase the RAM of the virtual machine on which vRealize Orchestrator is deployed up to the next suitable increment. For information on increasing the RAM of a virtual machine in vSphere, see Change the Memory Configuration in vSphere Virtual Machine Administration.

Procedure

  1. Log in to the vRealize Orchestrator Appliance command line over SSH as root.
  2. Navigate to the /opt/charts/vco/templates/ directory.
  3. Back up the deployment.yaml file.
    Caution: When creating the backup of the deployment.yaml file, place the backup in another directory. Keeping the backup in the /opt/charts/vco/templates/ directory can lead to the vRealize Orchestrator environment becoming inoperable.
    cp deployment.yaml /tmp/
  4. By using your preferred editor, edit the deployment.yaml file.
    vi deployment.yaml
  5. Search for lines containing the env string until you find the vco-server-app container.
          - name: vco-server-app
            image: {{ .Values.image.repository }}:{{ .Values.image.tag }}
            env:
            - name: JAVA_PROXY_SCHEMEE
  6. Under the env section, add a JVM_HEAP environment variable with a value, where {DESIRED_HEAP_SIZE} corresponds to the new desired heap memory size, for example 4G.
      - name: vco-server-app
            image: {{ .Values.image.repository }}:{{ .Values.image.tag }}
            env:
            - name: JVM_HEAP
              value: {DESIRED_HEAP_SIZE}
            - name: JAVA_PROXY_SCHEME
  7. Search for lines containing the memory: 5G string in the deployment file.
    Note: The deployment file must have only one memory: 5G string.
    resources:
       limits:
         memory: 5G
       requests:
          memory: 4G
  8. Increase the container limits and requests.
    Caution: The limits: memory: value must have a value that is 2 Gigabytes higher than the JVM_HEAP memory value in step 6. For example, if the value in step 6 is value: 4G, then you must set the limits: memory: value to memory: 6G. The requests: memory value must be 1 Gigabyte higher that the JVM_HEAP memory value in step 6. For example, if the heap value in step 6 is value: 4G, then you must set the requests: memory value to memory: 5G.
    resources:
       limits:
         memory: {Desired heap size + 2G}
       requests:
          memory: {Desired heap size + 1G}
  9. Save your changes to the deployment file, and navigate to the /opt/scripts directory.
    Note: For clustered environments, perform the preceding steps on all nodes of the cluster.
  10. Run the deploy.sh command.
    Note: For clustered environments, run the deployment script on the primary node.

Results

You have changed the heap memory size of your vRealize Orchestrator server.