Table of Contents |
---|
...
Operation | Method | URL | Example | ||
---|---|---|---|---|---|
Authenticate | POST | http://host/en/omk/admin/login | http://uburnto.opmantek.net/en/omk/opHA/login
|
...
If we want to create a node in a remote cluster, we should indicate the remote cluster id in configuration.pollers: Cluster cluster_id
.
cluster_id
is the uuid of which opHA server the node belongs to.
E.x.
Create Remote | POST | http://host/en/omk/admin/api/v2/nodes.json | http://uburnto.opmantek.net/en/omk/admin/api/v2/nodes.json
|
...
Update a remote Node
If we want to create update a node in a remote cluster, we just need to should indicate the remote cluster id in configuration.pollers: cluster_id
.
cluster_id
:is the uuid of which opHA server the node belongs to.
E.x.
Create Remote | PUT | http://host/en/omk/admin/api/v2/nodes/node_uuid.json | http://volla.opmantek.net:6042/en/omk/admin/api/v2/nodes/6ce5fd5c-d703-4d03-b36c-b8e01439a9f2.json
|
...
- opHA needs to be pulling that peer. This is because the peer sends the API url to update the remote in the registry data. And this information should be updated at least once a day.
- The peer has to be online.
If we should want to edit the remote node locally for some reason, we should use opnode_admin cli tool.
...