Roadmap & Limitations

Mesh Hypervisor is a Minimum Viable Product (MVP)—a solid core with room to grow. This section covers its current limits and planned enhancements. For usage, see Usage.

Current Limitations

Mesh Hypervisor’s MVP status means some trade-offs:

  • Security: No encryption—root SSH uses default keys (toor). Configs and data transfer over HTTP are unencrypted.
  • Workloads: KVM-only for now—other virtualization (e.g., Xen, containers) isn’t supported yet.
  • Networking: Manual VXLAN setup; no dynamic routing or GUI management.
  • Interface: CLI-only on the central node—no TUI or web dashboard.
  • Storage: Diskless by default; local RAID/LUKS needs manual config (e.g., storage group).

These keep Mesh Hypervisor simple and deterministic but limit its polish.

Roadmap

Future releases aim to address these:

  • Encryption: Add SSH key management, HTTPS for APKOVLs, and VXLAN encryption (e.g., IPSec).
  • Virtualization: Support Xen, LXC, or Docker alongside KVM for broader workload options.
  • Network Automation: Dynamic VXLAN config, IPv6 routing, and bridge management tools.
  • User Interface: Introduce a curses-based TUI for the central node, with a web UI later.
  • Storage: Simplify RAID/LUKS setup with prebuilt groups or scripts.
  • User Management: Replace root-only access with role-based accounts.

No timelines yet—focus is on stability first. Feedback drives priorities.

Notes

Mesh Hypervisor’s MVP trades features for simplicity—security and flexibility are next. For current workarounds, see Configuring Nodes and Network Configuration. Questions? Check FAQ.