How virtualcable/openuds works
Project type and purpose
• OpenUDS is a multi‐repo, full‐stack, microservice‐style connection broker for virtual desktops (VDI), app virtualization and desktop service consolidation.
• Top‐level submodules:
• actor – a background agent (“actor”) that polls the server and instantiates user sessions/transports
• client – CLI or library for issuing REST calls to the server
• guacamole-auth-uds – Apache Guacamole authentication plugin
• server – the main Django web/API application, containing REST handlers, core business logic, plugins, workers
• tunnel-server – a minimal tunnel‐proxy service
File structure
• server/src/server – Django project (manage.py, settings.py.sample, wsgi/asgi, urls.py)
• server/src/uds – the main Django app, with subpackages:
• REST – HTTP/JSON API dispatchers & handlers (business → serializers → models → managers)
• admin, web/views/templates/static – presentation layer (Django templates + modern SPA assets)
• auths, mfas, notifiers – plugin points for authentication, multi-factor, notification backends
• core – central abstractions (auth factory, jobs scheduler, messaging, managers, util)
• services – connectors to external virtualization backends (OpenStack, Xen, Proxmox, OVirt, etc.)
• osmanagers – OS‐level user provisioning managers (Linux, Windows domain, test stub)
• transports – code and per‐OS scripts to launch RDP, VNC, SSH, X2Go sessions
• workers – internal task runners (stats collection, cleanup, scheduler housekeepers)
• Configuration files (.pylintrc, mypy.ini, pytest.ini) and CI workflows (.github/workflows)
README
• Confirms it is an open‐source, Python 3.10+ Django project, split across multiple repositories.
• Master is under development; stable branches use v4.0.