Identify the Deployment Nodes
Identify the nodes that will host the RegattaDB modules. For each node, prepare:- Internal IP addresses for cluster communication.
- External IP addresses for client application access (if required).
Deploy the SM
RegattaDB uses a single SM (System Manager) module.- Select the node that will host the SM.
- Install the SM package.
- Start the SM service.
Deploy the SNA
Deploy an SNA on every node that will host one or more Operational Modules.- Install the SNA package.
- Start the SNA service.
Plan Module Placement
Determine which Operational Modules will run on each node. A single node may host one or more modules. Each deployment requires:- Exactly one DCM
- Exactly one Sequencer
- Exactly one GDD
- One or more RDB modules
Install the Operational Modules
Install the RPM packages corresponding to the assigned module roles on each node.Enter SETUP State
Install the RegattaDB CLI, which is included in the software package. The CLI may be installed on any node that has network connectivity to the SM. Transition the system from the DOWN state to the SETUP state to enable configuration operations.Define the Infrastructure
Register the cluster nodes using their host names and configured IP addresses.Configure Storage
Register the storage devices assigned to each node by specifying a unique name and the local device path for each storage device.Add the Operational Modules
Register each module, assign it to its designated node, and associate it with the appropriate storage device.By default, RegattaDB automatically allocates memory according to the requirements of each module. Because the RDB is designed to consume all remaining available memory, it should always be provisioned after the other modules. This ensures it receives the memory that remains after the fixed allocations for the other modules have been reserved. Although RegattaDB supports manual memory allocation on a per-module basis, the default allocation should be used unless your sizing analysis requires otherwise.