Bug 592697
Summary: | Ability to organize VMs/connections in groups | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Jo-Erlend Schinstad <joerlend.schinstad> |
Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | berrange, crobinso, jon, michaelrclay, xen-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-01-25 02:05:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jo-Erlend Schinstad
2010-05-16 11:06:23 UTC
*** Bug 700407 has been marked as a duplicate of this bug. *** Thinking about it some, I don't think we will ever implement this in virt-manager. For one thing, most users that want grouping features are probably managing a large number of machines and VMs which virt-manager isn't really designed for. Your case is certainly valid but of very limited usage in my experience (most people are using the app to virtualize maybe 1 or 2 vms), so it's not that justifiable to invest development time in a possibly disruptive feature. That said if someone popped up with a patch that implemented this in a nice unobtrusive way I'd consider it. |