Backlog #3176

Saving VM to template do not store changed parameters

Added by EOLE Team almost 7 years ago. Updated over 6 years ago.

Status:ClosedStart date:09/05/2014
Priority:HighDue date:
Assignee:-% Done:


Target version:-



Trying to use the VDC feature, I found that saving VM to template do not store the new capacity, nor the new networks.

Step to reproduce, as VDCadmin:

  1. Select the green + to create a new machine
  2. Select a template
  3. Change capacity
  4. Add a network
  5. Create the VM
  6. When running, poweroff the VM
  7. When powered off, save the VM to template

The new template do not use the new capacity nor the new network.

I think this is a problem:

  • Users in oneadmin group create basic, shared to everybody, resources
  • VDC admins can tweak these resources to fit the VDC, for example replace a common network with a dedicated one
  • Users in the VDC just need to instanciate the VM without bothering about details

The save VM to template wizard could ask for parameters to store.


Related issues

Related to Feature #2051: Clone a VM Closed 05/15/2013


#1 Updated by Ruben S. Montero almost 7 years ago

  • Tracker changed from Request to Backlog
  • Priority changed from Normal to High

#2 Updated by Daniel Molina over 6 years ago

#3 Updated by Daniel Molina over 6 years ago

  • Status changed from Pending to Closed

This issue wil be fixed with Clone VM functionality

Also available in: Atom PDF