Commands

Mon, 01 Jan 0001 00:00:00 +0000

Server Daemon

Build

make

Produces the cc-node-controller binary in the repository root. Debian and RPM packages can be built with make DEB and make RPM respectively.

Run

./cc-node-controller [options]

The daemon must run on the compute node it controls (it only processes messages matching its own hostname) and requires access to liblikwid.so.

Options

Flag	Default	Description
`-config <path>`	`./config.json`	Path to the JSON configuration file
`-loglevel <level>`	`warn`	Log verbosity: `debug`, `info`, `warn`, `error`
`-pretend`	`false`	Dry-run mode — process messages and log what would happen, but do not apply any hardware changes

Example

./cc-node-controller -config /etc/cc-node-controller/config.json -loglevel info

Signals

cc-node-controller handles the following UNIX signals for graceful shutdown:

Configuration

Mon, 01 Jan 0001 00:00:00 +0000

Configuration is provided as a flat JSON file. The default path is ./config.json in the working directory; an alternative path can be specified with the -config flag.

Fields

Field	Type	Required	Default	Description
`server`	string	yes	—	IP address or hostname of the NATS server
`port`	integer	yes	—	Port of the NATS server
`requestSubject`	string	yes	—	NATS subject to subscribe to for incoming control requests. All `cc-node-controller` instances in a cluster can share the same subject; each daemon only processes messages directed at its own hostname.
`user`	string	no	—	Username for NATS basic authentication
`password`	string	no	—	Password for NATS basic authentication
`credsFile`	string	no	—	Path to a NATS credentials file (for NKey/JWT-based authentication)
`nkeySeedFile`	string	no	—	Path to an NKey seed file
`outstandingMessagesInQueue`	integer	no	`1000`	Size of the internal channel buffer for incoming NATS messages

Minimal Example

{
 "server": "127.0.0.1",
 "port": 4222,
 "requestSubject": "cc-control"
}

Full Example

{
 "server": "nats.example.org",
 "port": 4222,
 "requestSubject": "clustercockpit.control",
 "user": "ccnc-user",
 "password": "s3cr3t",
 "outstandingMessagesInQueue": 500
}

Authentication

cc-node-controller supports three NATS authentication methods. Only one should be configured at a time:

cc-node-controller on ClusterCockpit