/controller/register
POST
Registers a Controller
- A Controllers consists of a standalone instance or cluster with primary and secondary nodes.
- This resource adds a Controller to JOC Cockpit. Updates Controller instance information such as the URL.
Parameters in the POST body schema
Name | Type | Description | Example | Default |
---|---|---|---|---|
controllerId |
optional, string | Controller ID (can be empty if and only if a new Controller (Cluster) will be registered) | scheduler | |
controllers |
required, array | Controllers of a cluster or one standalone Controller each Controller has the following fields |
||
url |
required, string | URL of the Controller instance | ||
clusterUrl |
optional, string | Only for a Cluster: A URL that the Controller instances use to connect to each other | url |
|
role |
required, string | Role (STANDALONE, PRIMARY or BACKUP) of the Controller | ||
title |
optional, string | A title that is used when displaying the Controller in JOC Cockpit | ||
auditLog |
optional, object | Object that contains comment , timeSpent and ticketLink . |
{ "comment": "Operational requirement!", "timeSpent": 2 } |
|
comment |
optional, string | Field in auditLog to comment this action, e.g. the reason. |
||
timeSpent |
optional, integer | Field in auditLog to enter the time spent in minutes. |
||
ticketLink |
optional, string | Field in auditLog to enter a link to a corresponding ticket. |
Request