Node Rollout

Each node should use an individual secret and write report.yaml to its local service directory.

Reporting Model

Each node stores:

version: 1
targets:
  - id: 1
    url: https://dash.example.com/api/node/metrics
    key: node-secret
    server_install_id: dash-install-id

report install calls sibling /api/node/identity, reads server_install_id, and writes config with atomic rename and 0600 permissions.

Create Nodes

Before creating nodes in Dash, prepare:

• Node name.
• Group.
• Guest visibility.
• Reporting secret.
• Traffic billing participation.
• P95 setting.
• Node-level billing cycle override, if required.

Batch rollout can use a table:

Host	OS	Arch	Group	NIC	secret
web-01	Linux	amd64	web	eth0	unique
db-01	Linux	arm64	db	ens3	unique

Linux Nodes

curl -fsSL https://dash.example.com/deploy/linux/install.sh -o install_node.sh
sudo bash install_node.sh dash.example.com 443 '<node-secret>' 3 --net eth0

Installed paths:

Item	Path
Service user	ithiltir
Data directory	/var/lib/ithiltir-node
Current version	/var/lib/ithiltir-node/current
Config file	/var/lib/ithiltir-node/report.yaml
systemd unit	/etc/systemd/system/ithiltir-node.service

Checks:

systemctl status ithiltir-node.service
journalctl -u ithiltir-node.service -n 100 --no-pager
/var/lib/ithiltir-node/current/ithiltir-node report list

LVM thinpool collection is handled by the script and cron:

Item	Path
Collector	/opt/node/collect_thinpool.sh
cron	/etc/cron.d/ithiltir-node-thinpool
Cache	/run/ithiltir-node/thinpool.json

The script enables this only when LVM/LVM-thin is detected. On apt-get systems it installs cron automatically. Hosts without LVM skip this path and remove old collector entries.

SMART cache is refreshed by a root-side systemd timer:

Item	Path
Cache	/run/ithiltir-node/smart.json
Helper	/usr/local/libexec/ithiltir-node/smart-cache
Service	/etc/systemd/system/ithiltir-node-smart-cache.service
Timer	/etc/systemd/system/ithiltir-node-smart-cache.timer

The script attempts to install smartmontools. If installation fails, smartctl is missing, or the cache is stale, the node keeps reporting base metrics and exposes SMART state through disk.smart.status.

macOS Nodes

curl -fsSL https://dash.example.com/deploy/macos/install.sh -o install_node.sh
sudo bash install_node.sh dash.example.com 443 '<node-secret>' 3

macOS currently supports arm64 only.

Checks:

sudo launchctl print system/com.ithiltir.node
tail -n 100 /var/log/ithiltir-node.log /var/log/ithiltir-node.err

Windows Nodes

Administrator PowerShell:

Invoke-WebRequest -Uri "https://dash.example.com/deploy/windows/install.ps1" -OutFile ".\install_node.ps1"
powershell -ExecutionPolicy Bypass -File .\install_node.ps1 dash.example.com 443 "<node-secret>" 3

Paths:

Item	Path
runner	%ProgramFiles%\Ithiltir-node\ithiltir-runner.exe
node	%ProgramData%\Ithiltir-node\bin\ithiltir-node.exe
Config	%ProgramData%\Ithiltir-node\report.yaml
Service	ithiltir-node

Check:

Get-Service ithiltir-node

Windows self-update works only when the node is managed by runner. Direct node push does not process update manifests.

Linux and macOS also process update manifests when using the /var/lib/ithiltir-node/releases/<version> and /var/lib/ithiltir-node/current install layout. Direct binaries outside that layout do not self-update.

Automatic update delivery from the Dash admin console requires the current node version to be 0.2.1 or later. For older versions, rerun the install command.

Network Interface Selection

By default, the node collects all visible network interfaces. To collect business interfaces only:

--net eth0,eth1

Rules:

• Comma-separated.
• Empty values are ignored.
• Nonexistent interfaces are logged as warnings.
• Push and Local modes both support --net.

Strict HTTPS

To require HTTPS:

sudo bash install_node.sh dash.example.com 443 '<node-secret>' 3 --require-https

--require-https rejects non-HTTPS targets and disables HTTP fallback. Do not use it for internal HTTP deployments.

Rotate Secret

Update local key:

/var/lib/ithiltir-node/current/ithiltir-node report update <id> '<new-secret>'
sudo systemctl restart ithiltir-node.service

report update changes only the existing target key. When the URL changes, run:

/var/lib/ithiltir-node/current/ithiltir-node report install https://dash.example.com/api/node/metrics '<new-secret>'

Validation

A successful node rollout should satisfy:

• Node service is running.
• report list shows the target URL.
• Dash admin console shows the node online.
• /metrics history has new points.
• Static hardware info includes CPU, memory, disk, and system fields.
• Selected NIC traffic counters keep increasing.