Matthias Riegler ed3dbd2a7f chore: remove prerelease
the agent has been stable for a few weeks, config options are missing
still

Signed-off-by: Matthias Riegler <matthias.riegler@ankorstore.com>
2023-09-04 20:00:57 +02:00
2023-07-26 18:10:34 +02:00
2023-09-04 20:00:57 +02:00
2023-07-19 18:19:21 +02:00
2023-07-26 18:10:34 +02:00

computeblade-agent

⚠️ this is WIP & just had its first alpha release. APIs/configuration/... is subject to change!

The computeblade-agent is an OS agent interfacing with the ComputeBlade hardware. It controls fan speed, LEDs and handles common events e.g. to identify/find an individual blade in a server rack.

In addition, it exposes hardware- and agent-related metrics on a Prometheus endpoint (hardcoded on port 9666 right now).

Components

computeblade-agent

The agent is an event-loop handler that's reacting on system events such as button presses, API calls or temperature changes (eventually). It also exposes a prometheus endpoint.

bladectl - interacting with the agent

The bladectl interacts with the node-local API exposed by the computeblade-agent. You can e.g. identify the blade in a rack using bladectl identify --wait, which will block & make the edge-LED blink until the button is pressed.

Or change the fan-speed to 80% by invoking bladectl fan set-percent 80.

Install Instructions

At this point, there are no easy-to-use install instructions but the goal is to integrate this as a default component on any computeblade.

Debian, RPM and archlinux packages are released and can be installed after downloading, e.g. using dpkg -i <whateveristhelatestversion>.deb

The computeblade-agent also ships with a systemd unit which can be enabled using systemd enable computeblade-agent.service --now. bladectl is available within the PATH, but has to be executed as sudo since the socket (hardcoded on /tmp/computeblade-agent.sock) has no permissions configured yet.

Description
Languages
Go 97%
Shell 2.5%
Makefile 0.4%
Dockerfile 0.1%