Increasing the external orchestrator heap memory in VMware Aria Automation 9.1

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

How to increase or scale out the heap memory for an external VMware Aria Automation Orchestrator server.

Environment

VCF  Automation Orchestrator 9.1

Cause

Specific product documentation detailing the procedure to scale out the heap memory for VMware Aria Automation 9.1 is not currently published.

Resolution

The configuration steps to scale out the heap memory for VMware Aria Automation Orchestrator 9.1 are identical to those used in version 8.18.

To increase the heap memory, perform the steps below:

• Log in the 

  Automation Orchestrator Appliance

   command line over SSH as 

  root

  .
• To create the custom profile directory and the required directory tree that is used when the profile is active, run the following script:

  vracli cluster exec -- bash -c 'base64 -d <<< IyBDcmVhdGUgY3VzdG9tIHByb2ZpbGUgZGlyZWN0b3J5Cm1rZGlyIC1wIC9ldGMvdm13YXJlLXByZWx1ZGUvcHJvZmlsZXMvY3VzdG9tLXByb2ZpbGUvCgojIENyZWF0ZSB0aGUgcmVxdWlyZWQgZGlyZWN0b3J5IHRyZWUgdGhhdCB3aWxsIGJlIHVzZWQgd2hlbiB0aGUgcHJvZmlsZSBpcyBhY3RpdmUKbWtkaXIgLXAgL2V0Yy92bXdhcmUtcHJlbHVkZS9wcm9maWxlcy9jdXN0b20tcHJvZmlsZS9oZWxtL3ByZWx1ZGVfdmNvLwoKIyBDcmVhdGUgImNoZWNrIiBmaWxlIHRoYXQgaXMgYW4gZXhlY3V0YWJsZSBmaWxlIHJ1biBieSBkZXBsb3kgc2NyaXB0LgpjYXQgPDxFT0YgPiAvZXRjL3Ztd2FyZS1wcmVsdWRlL3Byb2ZpbGVzL2N1c3RvbS1wcm9maWxlL2NoZWNrCiMhL2Jpbi9iYXNoCmV4aXQgMApFT0YKY2htb2QgNzU1IC9ldGMvdm13YXJlLXByZWx1ZGUvcHJvZmlsZXMvY3VzdG9tLXByb2ZpbGUvY2hlY2sKCiMgQ29weSB2Uk8gcmVzb3VyY2UgbWV0cmljcyBmaWxlIHRvIHlvdXIgY3VzdG9tIHByb2ZpbGUKY2F0IDw8RU9GID4gL2V0Yy92bXdhcmUtcHJlbHVkZS9wcm9maWxlcy9jdXN0b20tcHJvZmlsZS9oZWxtL3ByZWx1ZGVfdmNvLzkwLXJlc291cmNlcy55YW1sCnBvbHlnbG90UnVubmVyTWVtb3J5UmVxdWVzdDogMTAwME0KcG9seWdsb3RSdW5uZXJNZW1vcnlMaW1pdDogNjAwME0KcG9seWdsb3RSdW5uZXJNZW1vcnlMaW1pdFZjbzogNTcwME0KcG9seWdsb3RSdW5uZXJFcGhlbWVyYWxTdG9yYWdlTGltaXQ6IDIwR2kKcG9seWdsb3RSdW5uZXJFcGhlbWVyYWxTdG9yYWdlUmVxdWVzdDogNEdpCgplcGhlbWVyYWxTdG9yYWdlTGltaXQ6ICIyR2kiCmVwaGVtZXJhbFN0b3JhZ2VSZXF1ZXN0OiAiNTEyTWkiCgpzZXJ2ZXJNZW1vcnlMaW1pdDogNC40RwpzZXJ2ZXJNZW1vcnlSZXF1ZXN0OiAzLjJHCnNlcnZlckp2bU1heFJhbVBlcmNlbnRhZ2U6IDQwCnNlcnZlckp2bU1ldGFzcGFjZU1heDogNTAwbQpFT0YKY2htb2QgNjQ0IC9ldGMvdm13YXJlLXByZWx1ZGUvcHJvZmlsZXMvY3VzdG9tLXByb2ZpbGUvaGVsbS9wcmVsdWRlX3Zjby85MC1yZXNvdXJjZXMueWFtbA== | bash'

  
  

   
• Edit the resource metrics file in your custom profile with the desired memory values.

  vi /etc/vmware-prelude/profiles/custom-profile/helm/prelude_vco/90-resources.yaml

   
• The

  90-resources.yaml

  file should contain the following default properties:
  

  polyglotRunnerMemoryRequest: 1000M
  polyglotRunnerMemoryLimit: 6000M
  polyglotRunnerMemoryLimitVco: 5700M
  polyglotRunnerEphemeralStorageLimit: 20Gi
  polyglotRunnerEphemeralStorageRequest: 4Gi
  
  ephemeralStorageLimit: "2Gi"
  ephemeralStorageRequest: "512Mi"
  
  serverMemoryLimit: 4.4G
  serverMemoryRequest: 3.2G
  serverJvmMaxRamPercentage: 40
  serverJvmMetaspaceMax: 500m

   
• Save the changes to the resource metrics file and run the 

  deploy.sh

   script.

  /opt/scripts/deploy.sh