Connections

System Connections And APIs

Choose an adapter, discover readings and expose only the controls you need.

Open System Connections → Connect System. Choose Server Controller (Redfish), Legacy Controller (IPMI) or Custom API, enter the management address and credentials, and choose Connect Through: the panel or an enrolled site collector. Save and test. Passwords/tokens remain encrypted beside media sources in MariaDB and are excluded from workspace exports. URLs remain visible. Sysavia manages storage and backups for the hosted service.

Hardware

Redfish discovers the controller's advertised systems and managers. Select the system, then Use This System. Refresh to read model, serial, power and overall health. Power actions are validated against the controller's advertised reset capabilities. Support depends on the actual firmware implementation, not simply the brand badge. TLS verification remains enabled; the execution host must trust the controller's certificate.

IPMI uses ipmitool on the panel or selected collector, with IPMI 2.0 LANPlus. It reads power state and sensors and supports on/off/cycle/reset/soft commands. The platform operator installs the IPMI runtime once; customers configure controller addresses and credentials in the panel. Passwords are passed through the child environment, not shell arguments. No arbitrary IPMI command entry is accepted.

Enable explicit control actions only on connections intended for management. Manual controls require a confirmation; automation actions use that saved permission. Site collectors also require management permission selected during enrollment. The legacy ENABLE_LIVE_ACTIONS setting continues to govern legacy endpoint/script/HTTP actions, not the new per-connection permission. This is still the requested unauthenticated lab panel, not a multi-tenant authorization boundary.

Power responses mean a command was accepted. Use the existing recovery verification/failure path with a fresh Connected System check to verify completion rather than assuming a restart succeeded.

API operations

For APIs with OpenAPI 3 or Swagger 2 JSON, Import OpenAPI reads a specification path (default /openapi.json), imports named draft operations and opens review. Importing never runs a write operation. Review paths, required parameters, bodies and value mappings before saving. YAML and external $ref resolution are not implemented.

For other APIs, Edit Operations → + Operation defines a named request. Choose a method, relative path, response format and value path. JSON and XML are supported; for example data.status or probe.stream.0.bitrate. XML attributes appear as @name, repeated elements as arrays, and mixed text as #text. DTD/entity declarations and external references are rejected. Responses are limited to 1 MiB. Requests remain on the configured origin and do not follow redirects with credentials.

Authentication supports none, basic, bearer and custom API-key headers. Credentials are entered in the connection editor; no environment variable is needed. The older API Integrations library remains for backward compatibility with existing checks and rules.

Refresh Readings executes a GET/HEAD operation. Writes have a separate Run control and confirmation. Monitor This Reading attaches a selected read operation or hardware reading to equipment, sets a healthy-value comparison and optionally publishes a Live Value. These checks feed the same grid colors, service triggers, alerts and recovery verification as other monitoring. In the automation builder, choose Run connected system action, select a saved connection, then select an API operation or power command.

Private networks and consoles

Enroll an agent under Site Collectors, select whether it may run management jobs or relay VNC, and download its one-time profile. Install the application dependencies on that machine and run node agent.mjs collector.json. All subsequent connections/checks are assigned through the panel. The profile credential is individual and revocable; no shared legacy agent token is required for collector-only mode. See Site Collectors.

For a private VNC server, create a VNC desktop Media Source and choose its site collector under Connect Through. Place it with + Playback. The agent establishes outbound WebSockets; no inbound port is required at the site. The hosting proxy must support the collector upgrade routes in deploy/nginx-media.conf.

IPMI/Redfish control support does not imply universal graphical KVM compatibility. Media Sources includes Dell VNC discovery with verified TLS, Supermicro fresh native-console launch URLs, and HPE interactive native-console launching. HPE/Supermicro native viewers open separately and require browser-to-controller reachability; they are not embedded grid feeds. VNC, Proxmox and compatible browser gateways remain available. See Vendor Console Adapters. No vendor licensing is bypassed.

Current boundaries

This implements the connection/collector foundation, not a claim of universal device compatibility. WireGuard/OpenVPN lifecycle management and SNMP trap ingestion are available under Network Tools. Browser dashboard relaying, remote media transcoding through collectors, universal proprietary KVM embedding, comprehensive sensor discovery, customer organizations/RBAC and durable offline job history are not implemented. An agent cannot infer undocumented APIs or proprietary console protocols. Protocol fixtures and local endpoints are tested; actual vendor hardware acceptance testing is still required.