...
Term | Meaning |
|---|---|
Main Primary | server instance running opHA with role = 'primary_master' |
Secondary Primary | server instance running opHA with role = 'master'. Also referred to as just '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. |
Producer | an instance of the ophad process running in 'producer' mode (as per configuration). This will typically be running on the same server instances as the primary. |
Consumer | an instance of the ophad process running in 'consumer' mode (as per configuration). This will typically be running on the same server instance as the poller (or mirror) |
Software Installation
Upgrade to opHA-MB 5.1.0 can be done from installed on infrastructure
New to opHA/opHA-MB ----- Install to new servers
Running opHA 4.X ----- Upgrade existing servers, running opHA 4.x
...
Installation of opHA-5.1.0
...
that does not have opHA software installed
Prerequisites
IMPORTANT: All the servers should be setup with the following
...
Server-Specific Configuration
Update /usr/local/omk/conf/opCommon.json for Main Primary and Secondary Primary only. For key “database” add the following information:
| Code Block | ||
|---|---|---|
| ||
"database" : { "db_replica_set": "rs1", "db_mongo_cluster": [ "opha-dev1.opmantek.net", "opha-dev6.opmantek.net" ], "nats_num_replicas": 3, "nats_cluster": [ "opha-dev1.opmantek.net", "opha-dev2.opmantek.net", "opha-dev6.opmantek.net" ] } |
MongoDB Setup (Main Primary Only)
...
Server-Specific Configuration
Update /usr/local/omk/conf/opCommon.json for Main Primary and Secondary Primary only
| Code Block | ||
|---|---|---|
| ||
"db_replica_set": "rs1", "db_mongo_cluster": [ "opha-dev1.opmantek.net", "opha-dev6.opmantek.net" ], "nats_num_replicas": 3, "nats_cluster": [ "opha-dev1.opmantek.net", "opha-dev2.opmantek.net", "opha-dev6.opmantek.net" ] |
...