Categories

Category cover

Automation
155 posts

Category cover

Learning paths
119 posts

Category cover

CISO
22 posts

Category cover

Security
20 posts

Category cover

Notes
19 posts

Category cover

Personal Security
18 posts

Category cover

Infrastructure
12 posts

Category cover

OT/ICS
5 posts

Category cover

Books
3 posts

Category cover

UNetLab
3 posts

Category cover

Write-up
3 posts

Category cover

OSInt
2 posts

Category cover

My life
1 posts

UNetLab v3 architecture

Andrea Dainese
October 23, 2024
Post cover

UNetLab’s architecture involves several components that need to interact with each other and report task progress to the user. We can identify the following components:

  • The web interface allows users to interact with UNetLab, manage users, and labs.
  • Proxmox hosts manage the nodes and networks of the labs according to instructions received from users and notify the status of the nodes.
  • The orchestrator, which is the engine that manages tasks and input received from the user through the web interface and from the hosts via a specific agent.

The orchestrator

At first glance, we can imagine a Redis server collecting input from users (via the web interface) and from hosts. The orchestrator receives messages from Redis and forwards them, transforming them, to the web interface or to agents running on the hosts.

Continue reading the post on Patreon .