System Validation

System Validation

Resonate RFID Reader Management requires certain system specifications to function properly and automatically creates the
trif-user
user and the
microk8s
group.
Server Configuration
Resource
Minimum Requirement
Validation Command
OS
Ubuntu Enterprise 22.04 or 24.04 LTS.
more /etc/os-release
Memory
24 GB in most cases.
16 GB in single-node configuration without many RFID readers.
lsmem | grep “Total online memory”
vCPU
4 vCPUs for single node configuration.
12 vCPUs for multi-node configuration.
lscpu | grep “CPU(s)”
Disk layout and sizing
Extra disk for data storage: 128 GB. In single-node configuration, it should be mounted at
/data
; otherwise, it should not be mounted and should not contain partitions or a file system.
Extra partition for
/var/snap
: 50 GB
Operating system disk: 100 GB.
If mounted, use:
df -h -x overlay
To see all available disks and partitions, whether mounted or not, use either:
  • lsblk
  • sudo fdisk -l
Hostname
Verify the domain is appended.
hostname -f
Resonate user
The
trif-user
user is in the
microk8s
group.
The setup.sh script of the Resonate installer automatically creates the user and group.
groups <trif-user administrative user>
Network Configuration
Resource
Validation Command
DNS name resolution for all systems
Run the nslookup command for each hostname and ensure that each resolves:
nslookup <hostname>
<hostname> = Docker host
<hostname> = NTP server
Time is in sync with the NTP server
Verify time synchronization using:
date
or
chronyc sources
Commands and output can vary. If Chrony is not used as the NTP service, instead of using
chronyc sources
, use the command associated with your NTP service to verify that time is in sync with the NTP server.
MicroK8s Configuration
Resource
Validation Command
Validation Result
MicroK8s
microk8s status
Reports information such as the status of core MicroK8s services and components and the enabled/disabled add-ons.
kubectl get nodes
In a multi-node configuration, it reports information such as:
  • Node status (
    Ready
    or encountering issues)
  • Version of Kubernetes currently running
  • Current node's role (for example, master)
  • Any issues or warnings