Request #2044
Expand VMID
| Status: | Closed | Start date: | 05/14/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Pull request: |
Related issues
History
#1
Updated by Ricardo Duarte about 8 years ago
Expand $VMID variable when instantiating templates.
Use case:
1. User creates a template with NAME = one-$VMID
2. The resulting instance (ex.: 100) will have name = one-100
#2
Updated by Javi Fontan about 8 years ago
When NAME is not specified the VM already gets the name one-<vmid>. Could you give use some other example? Is there something that should be dependant on the VMID?
#3
Updated by Ricardo Duarte about 8 years ago
Javi Fontan wrote:
When NAME is not specified the VM already gets the name one-<vmid>. Could you give use some other example? Is there something that should be dependant on the VMID?
It was not the best example (but at least on 4.0 beta it would fall-back to template name, and not one-VMID).
Say I want to call my instances i-$VMID (actually that is what I'm doing, but had to patch the code).
#4
Updated by Ruben S. Montero over 7 years ago
- Status changed from Pending to Closed
This will be implemented as part of #2590.
Thanks for your feedback!
#5
Updated by Ruben S. Montero over 7 years ago
- Related to Backlog #2590: General user inputs in templates added