Qewig Feature List

Feature Description
User Roles Restricts user ability based on role
Realtime Lab Multi-Access Labs belong to groups and multiple users can access the same lab concurrently. Users can communicate directly while inside a lab and all lab changes are made in realtime to all users connected.
User Limit No user limits
Clientless All functions, including uploading of node templates, labs, and software images can be done through an html5 browser
API driven While a html5 gui is available, it's also possible to configure everything trhough a documented API.
Node templates Users can create an upload node templates. Templates contain everything needed to add a new node type
Multichassis labs Labs can span across multiple physical servers to allow for greater scale
Link styles Links can be colored, and stylized with a label, dashes,etc
Node Limit A warning will be presented when resources are low but no limit in software is imposed
Ports Ports are chosen at random when node starts. It's possible to contain ports for nodes to a given range.
Multi console access Nodes can have multiple console ports on different ports E.G. serial 1/2
Docker support Docker container support
Hot add interfaces Links be connected or disconnected from running nodes
Docker wireshark capture User can set a docker node as a capture node and then mirror ports from any running devices
Seperation of functions Qewig has two functional roles(Controller and Handler). The controller role is the frontend including the gui and api. The Handler role listens for requests from a controller and launches and interconnects nodes. One controller can controll multiple handlers.
Database support All lab objects are stored in a database.
Advanced statistics Amount of memory per running lab, memory savings by ksm/uksm