Request #129
Map hypervisor name with VM Template NAME
| Status: | Closed | Start date: | 07/22/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - | |||
| Pull request: |
Description
The map between a VM at the hypervisor level (i.e. xm list or virsh list) is not straightforward. VMs are labeled with one-<ID> so you have to look to onevm list to find out which VM has id <ID>.
The proposed approach is to use $NAME-<ID> with NAME as specified in the template.
Suggestion by Sebastien Goasguen
History
#1
Updated by Marlon Nerling over 11 years ago
I don't like the ID!
Wenn you are working with 100+ VMs it would make the handling of them more difficult.
Anyhow, the display of onevm list does not show the entire VM name, so if I have say 20 Hardy32-$different_name , with all I see by calling onevm list are 20 'Hardy32-'.
Other side, it is easy to work with virsh if you know the ID of the VM .. use virsh 'command' one-ID !!
#2
Updated by Marlon Nerling over 11 years ago
Marlon Nerling wrote:
I don't like the ID!
I should better say: I like the ID, but I don't like the Idea!
Wenn you are working with 100+ VMs it would make the handling of them more difficult.
Anyhow, the display of onevm list does not show the entire VM name, so if I have say 20 Hardy32-$different_name , with all I see by calling onevm list are 20 'Hardy32-'.
Other side, it is easy to work with virsh if you know the ID of the VM .. use virsh 'command' one-ID !!
#3
Updated by Ruben S. Montero over 11 years ago
- Target version changed from Release 1.4.2 to Release 2.0
#4
Updated by Ruben S. Montero over 11 years ago
- Tracker changed from Bug to Request
#5
Updated by Javi Fontan over 10 years ago
- Target version deleted (
Release 2.0)
#6
Updated by Ruben S. Montero about 8 years ago
- Status changed from New to Closed
We'll keep the current naming.