Vidispine Server Agents¶
Vidispine server agents (VSAs) are typically handled with the vidispine-admin and vidispine-agent-admin shell tool. A few API commands are available for control, though.
New in version 4.6.
Managing VSAs¶
Retrieve all Vidispine server agents¶
-
GET
/vxa
¶ Returns all VSAs.
Produces: - application/xml, application/json – A VXAListDocument
Role: _vxa_read
Retrieve a specific Vidispine server agent¶
-
GET
/vxa/
(uuid)¶ Retrieves a specific VSA. As an alternative to the UUID, the name of the VSA can be used instead. The name syntax only works if the name is unique among the VSAs.
Produces: - application/xml, application/json – A VXADocument
Role: _vxa_read
Retrieve the VSA configuration¶
-
GET
/vxa/
(uuid)/configuration
¶ Returns the client-side configuration of the VSA.
Produces: - application/json – A JSON object with the settings and current status of the VSA.
Role: _vxa_read
Add a VSA node¶
-
PUT
/vxa/enable-ssh
¶ Registers a new VSA node in the system.
Query Parameters: - vsip – The address to which the VSA should connect. Can be specified multiple times for a cluster configuration.
- vsport – The port to which the VSA should connect. Can be specified multiple times for a cluster configuration.
- ws – The URI to the API endpoint. Used to enable websocket tunneling, as an alternative to vsip/vsport. Can be specified multiple times for a cluster configuration. (New in 4.14.)
- uuid – Optional, the UUID of the VSA. If not set, Vidispine will assign a UUID.
- vxaname – Optional, the name of the VSA.
Produces: - text/plain – A text configuration to be added on the VSA’s configuration.
Role: _administrator