Hide Forgot
Description of problem: Include the TUI version of virt-manager so that a console administrator can perform basic operations like viewing the set of running VMs, and possibly start/stop. The TUI might need to be restricted to a read only libvirt socket for oVirt Engine/vdsm interoperability. But still, read-only virt-manager TUI might be useful for sysadmins who want to see what is going on in the node locally.
virt-manager-tui is already on the node now, just need to determine what level of integration in the setup ui/etc?
Correct. There are a few things: 1. how do we integrate the tui into the existing config ui so that it's easy to transition from that UI to the virt-manager UI 2. make the visibility of the virt-manager TUI configurable so you could not show it if you don't want to 3. make it so the virt-manager tui can be restricted to read-only operations once vdsm is registered with the node, with the option to easily override and provide read-write for emergency situations Make sense?
I wonder if this will ever work with vdsm's libvirt configuration. For now there is virsh which can be used to do the administration. I'm closing this. Please reopen if necessary.