We can also manage nodes using the API.
Operation | Method | URL | Response | Example | |
---|---|---|---|---|---|
Get Nodes | GET | http://host/en/omk/admin/api/v2/nodes.json | http://uburnto.opmantek.net/en/omk/admin/api/v2/nodes.json?requestData=undefined&page=1&per_page=25&sort_by=name&order=asc | ||
Get Node | GET | http://host/en/omk/admin/api/v2/nodes/{node_uuid}.json | http://uburnto.opmantek.net/en/omk/admin/api/v2/nodes/86a82b4c-6ef6-4691-8c8c-1fc8da334d6f.json | ||
Create Node | POST | http://host/en/omk/admin/api/v2/nodes.json To create a remote node in an opHA cluster see below. | The node in json from the recently created node, including the UUID | http://uburnto.opmantek.net/en/omk/admin/api/v2/nodes.json
| |
Update Node | PUT | http://host/en/omk/admin/api/v2/nodes/{node_uuid}.json To update a remote node in an opHA cluster see below. | http://uburnto.opmantek.net/en/omk/admin/api/v2/nodes/b56ba595-69e7-4702-9fe5-49512e1340b0.json
| ||
Delete Node | DELETE | http://host/en/omk/admin/api/v2/nodes/{node_uuid}.json | http://uburnto.opmantek.net/en/omk/admin/api/v2/nodes/b56ba595-69e7-4702-9fe5-49512e1340b0.json |
Important: All these methods are authenticated.
Operation | Method | URL | Response | Example |
---|---|---|---|---|
Authenticate | POST | http://host/en/omk/admin/login |
We should receive a 200 response and a cookie, that we can reuse for next API calls.
If we want to create a node in a remote cluster, we 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 | POST | http://host/en/omk/admin/api/v2/nodes.json | It will return the json node, the same structure that the CREATE. | http://uburnto.opmantek.net/en/omk/admin/api/v2/nodes.json It will return the same output as for a local node:
|
If we want to update a node in a remote cluster, we 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.
Update Remote | PUT | http://host/en/omk/admin/api/v2/nodes/node_uuid.json | It will return the json node, the same structure that the CREATE. | http://volla.opmantek.net:6042/en/omk/admin/api/v2/nodes/6ce5fd5c-d703-4d03-b36c-b8e01439a9f2.json
|
If any operation has a remote cluster id, the API will try to edit in the remote server. If this operation is not possible, it will fail.
In order to succeed:
If we should want to edit the remote node locally for some reason, we should use node_admin cli tool.