Connections

Redfish And IPMI Controllers

Connect server management controllers and understand what each adapter can do.

hardware.mjs provides execution-host operations used by the connection controller and collectors. It does not authorize callers: the controller must enforce connection scope, action permission and live-action policy before invoking write functions. Credentials belong in the encrypted connection store, never the project or job logs.

ExportInputResult
discoverRedfish(config){url, username, password} or {url, token}Systems with resource paths, identity, health, memory, CPU count and advertised power actions; manager firmware and console protocol hints
readRedfishSystem(config, path)Discovered /redfish/v1/... resourceCurrent normalized system summary
redfishPower(config, path, action)Advertised ResetType such as GracefulShutdown{accepted:true, action, detail}; acceptance is not verification of resulting state
readIpmi(config){host, port:623, username, password}Chassis power state and sensor names/readings/units/status
ipmiPower(config, action)on, off, cycle, reset, or softAccepted request; check power state afterward

Redfish follows advertised resource links and ActionInfo, restricts every request to the configured controller origin and /redfish/v1/, does not follow redirects, retains normal certificate verification and bounds response size, request time and discovery collection sizes. Trust private controller CAs on the execution host. No certificate bypass is provided.

IPMI uses the ipmitool executable on the selected execution host, lanplus, argument arrays without a shell and the IPMI_PASSWORD subprocess environment variable rather than a command-line password. Its executable can be dependency-injected by the host integration; users cannot supply arbitrary commands. Missing tooling produces an actionable error. The default command deadline is 15 seconds.

These adapters do not provide universal KVM. An IPMI sensor/power interface is not a video protocol. Redfish graphical-console hints are reported, and Media Sources provides Dell VNC, Supermicro native launch and HPE interactive native launch adapters. See Vendor Console Adapters. HPE/Dell/Supermicro support depends on controller generation, firmware, licensing and advertised capabilities; no live vendor hardware was available for acceptance testing.

Validation uses a local HTTP Redfish fixture, ActionInfo and cross-origin credential guards, and an injected IPMI process runner to verify command restrictions and credential handling.