Versions Compared

Version Old Version 9 New Version 10
Changes made by

Josune Cordoba

John Sinclair

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In opHA 3, each server has a role in the system to keep the data synchronised between the network. 

Several roles have been introduced since opHA 3.3, in In the following table you can see all the roles and their functions. 

FunctionsServer Roles
ScreenActionMain PrimaryPrimaryStandalonePollerMirror
IndexView(tick)(tick)(tick)(error)(error)
LogsView(tick)(tick)(tick)(error)(error)
Configuration filesView(tick)(tick)(tick)(error)(error)
Edit(tick)(error)

(tick) 

(Only local files)

(error)(error)
PeersView(tick)(tick)(error)(error)(error)
Edit(tick)(error)(error)(error)(error)
Pull(tick)(tick)(error)(error)(error)
Peers GroupsView/Edit(tick)(error)(error)(error)(error)
RolesSet peers role(tick)(error)(error)(error)(error)
Set own role(tick)(tick)(tick)(tick)(tick)
Node ManagementView(tick)(tick)(tick)(tick)(tick)
Edit local nodes(tick)(error)(tick)(error)(error)
Edit remote nodes(tick)(error)(error)(error)(error)


opHA Server Roles

Term

Meaning

Main Primary

server instance running opHA with role = 'Main Primary'

Secondary Primary

server instance running opHA with role = 'Primary'

Peer

server instance running opHA with role = 'poller' or 'mirror'. It can optionally be of type 'streaming' which means that it is linked to an ophad instance.

Poller

server instance running opHA with role = 'poller'

Mirror

server instance running opHA with role = 'mirror'. It is paired with a poller and polls the same devices as that poller, however its data is not sync'd with primary unless the poller is offline.