| Summary: | RFE: Allow setting custom connection row name | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | leonardo |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | berrange, crobinso, freznice, 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: | 2015-04-11 17:53:31 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
leonardo
2012-01-23 18:21:28 UTC
I don't think we should auto resolve a passed IP address to a hostname, by default we should show what the user gave us. But I do like the idea of allowing the user to set a custom connection name/string etc. Let's use this bug to track that feature. Hello Cole, I understand that, usually, if I choose to use an IP wouldn't want the system to replace it with a hostname, but take this case for example: I don't have a domain name (or fqdn) for several hosts, but I would like to be able to distinguish them by their local hostname, so I don't need to remember or look for the IP in a table. As I can't use the local hostname to connect to them from virt-manager, I had to use the IP. I'm not saying we should replace the IP for the hostname or resolve it to a fqdn, but maybe post the local hostname next to the IP. As "the machine name". Anyway, this was just to clarify in case my (poor) English was in the middle of the idea. I would be more than happy with the custom field alone. Regards, Leonardo *** Bug 1040908 has been marked as a duplicate of this bug. *** Fixed upstream now:
commit 3d2afbaf6f634cca5deeec12eb704340502720ed
Author: Cole Robinson <crobinso>
Date: Sat Apr 11 13:39:25 2015 -0400
connection: Allow setting a custom 'pretty name' (bz 784701)
We've had multiple requests over the years for something similar. People
might have to connect to multiple IP addresses, or really large hostnames,
that become difficult to distinguish in the UI.
Add a field in the host details page that allows setting a custom name,
and store it in gsettings.
|