OpsCenter 4.0 User Guide

JavaScript must be enabled in order to use this site.

Please enable JavaScript in your browser and refresh the page.

Configuring for multiple regions

OpsCenter can operate in multiple regions or IP forwarding deployments. Use the
following approach for deployments where a public IP forwards to a private IP on the agent,
but that machine is not aware of (that is, can't bind to) the public IP.

To configure DataStax agents for multiple regions or IP forwarding:

Procedure

Open the address.yaml file for editing.

Packaged installs:

/var/lib/opscenter-agent/conf
directory

Tarball installs:

<install_location>/conf
directory

Add the following option to the address.yaml file:

local_interface: (Optional) The
IP used to identify the node. If broadcast_address is
set in cassandra.yaml, this should be the same as
that; otherwise, it is typically the same as
listen_address in
cassandra.yaml. A good check is to confirm that
this address is the same as the address that nodetool ring
outputs.

agent_rpc_interface: The IP
that the agent HTTP server listens on. In a multiple region deployment,
this is typically a private IP.

agent_rpc_broadcast_address: The IP that the central
OpsCenter process uses to connect to the DataStax agent.

Repeat the above steps for each node.

Example

here is the configuration for a three node cluster that spans two
regions: