There are two main ways to save your changes to virtual machines in Abiquo, which are to create:
An instance is a snapshot copy of a virtual machine system disk. An instance does not save the virtual machine configuration from the virtual machine.
In an Abiquo datacenter, in the Apps Library, Abiquo creates instances with a copy of the same template definition as the original master template the virtual machine was originally deployed from.
In public cloud regions, instances are independent of the original master template.
When you create an instance of a virtual machine, the virtual machine disk is saved but the virtual machine definition, with values such as CPU and RAM, is copied from the master template. When you create a virtual machine (in a virtual appliance in a virtual datacenter), the saved disk and the instance's virtual machine definition from the Apps Library are used to create a new virtual machine. You can edit the instance template and change the virtual machine definition for use in virtual machines that you create from that time onward. Changes in the Instance template virtual machine definition will not affect the Master template.
Diagram: Working with instances in Datacenters - original components are shown in blue and changed components are shown in violet.
If you know that you will need to use a virtual machine in a datacenter over a period of time and perhaps even undeploy the machine and then deploy it again at a later date, then you can create a persistent virtual machine.
A persistent virtual machine has the system disk on a volume of external storage not on the hypervisor datastore, so the system disk is not deleted when you undeploy. You can make and save changes to the virtual machine definition in the Apps Library.
When you add a persistent template to a virtual appliance, the saved disk image and definition are used to create the virtual machine.