1. Singular Deployment

When you deploy OpenBT for the first time, you're likely thinking of deploying a single instance without any load balancing. This is the simplest possible deployment. To achieve this, you must configure that instance of OpenBT as a ROOT, MASTER and SLAVE -- the default configuration.

Make the following changes to config.ini:

[config]
root = true
master = true or false
slave = true or false 

2. Clustered Deployment

If the load on a single instance becomes too heavy, there is always the option of deploying other instances and linking them together in a hierarchical cluster. Following the physical deployment of a new OpenBT instance, you must identify the MASTER instance that this new instance will report to. Next, configure your new instance as a SLAVE.

Make the following changes to config.ini on the SLAVE (new instance):

[config]
root = false
master = false
slave = true

[hosts]
master = 192.168.1.3

3. Cloud Deployment

If you're here, you're really in search for serious compute power. If you've exhausted all resources on one cluster, you may be looking to chain together two or more clusters. This option was built into OpenBT from the very beginning and thus explains the concept of a ROOT instance. Just keep in mind that security policies between two or more physical compute clusters may present an issue here. To allow a MASTER on cluster B to communicate with a ROOT on cluster A, take the following steps:

On the MASTER instance, make the following changes to config.ini:

[config]
root = false
master = true
slave = true | false

[hosts]
root = 123.456.789.10