Customizing the AtScale YAML File
This article describes how you can customize the YAML file, depending on what you want to accomplish in the AtScale topology. Basically, we can split most of the services into a different host, remap ports, and utilize a load balancer.
Caution: AtScale only accepts local hostname as part of the host entry. If you have a VM that keeps on changing the hostname, you could have a potential problem during startup because some processes in AtScale do an update in the modeler.
-- default engine |
To counter that, in the yaml file, you can add internal and external hosts, but only for the load balancer DNS mapping.
override: |
This setting will allow you to extend the AtScale internal host vs. external load balancer with separate ports in the load balancer vs internal.
Here is the working customization of AtScale with two load balancers with two ports mapped on 10500 to 80 and 10502 to 80:
installation_location: "/opt/atscale" |
The following is a complete customization of what you can do in atscale.yaml
engine: |