Email this issue
Send issue summary in email
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
If I want to have more than one image in a virtual app solution, it can be annoying and confusing to have two images with the same name.
In order to minimize this problem, when a virtual machine is dragged and dropped to the Visio, it should create automatically a new name for the image following this pattern:
1) First virtual machine in the virtual app, same name as virtual image.
2) Next virtual machine in the virtual app, same name as virtual image PLUS an incremental number. Example: Centos-1, Centos-2, Centos-N
The user should be able to open the virtual machine and change the name if it is not descriptive enough.
Virtual Machine names MUST be UNIQUE in every Virtual Appliance.
|
|
Description
|
If I want to have more than one image in a virtual app solution, it can be annoying and confusing to have two images with the same name.
In order to minimize this problem, when a virtual machine is dragged and dropped to the Visio, it should create automatically a new name for the image following this pattern:
1) First virtual machine in the virtual app, same name as virtual image.
2) Next virtual machine in the virtual app, same name as virtual image PLUS an incremental number. Example: Centos-1, Centos-2, Centos-N
The user should be able to open the virtual machine and change the name if it is not descriptive enough.
Virtual Machine names MUST be UNIQUE in every Virtual Appliance. |
Show » |
Sort Order:
|
Improvement
Closed
Major
Everytime a virtual machine is created, it should have a name derived from the virtual image name