Bug 753213

Summary: [RFE] Inclusion of virt-manager-tui
Product: [Retired] oVirt Reporter: Perry Myers <pmyers>
Component: ovirt-nodeAssignee: Joey Boggs <jboggs>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: fdeutsch, gouyang, hadong, iheim, jboggs, leiwang, mburns, ovirt-bugs, ovirt-maint, ycui
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.7.0 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-28 14:06:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Perry Myers 2011-11-11 15:58:37 UTC 
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.
Comment 1 Joey Boggs 2011-12-01 14:44:53 UTC 
virt-manager-tui is already on the node now, just need to determine what level of integration in the setup ui/etc?
Comment 2 Perry Myers 2011-12-01 15:33:42 UTC 
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?
Comment 3 Fabian Deutsch 2013-11-28 14:06:41 UTC 
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.