In Abiquo, users can download templates from remote template repositories. A remote template repository exposes a list of the templates it contains. Effectively it is an HTML file (ovfindex.html) and a collection of templates.
A remote template repository is indexed by a template definition list in the Abiquo API.
When you download a template definition to the datacenter, a virtual machine template is created, which means, for example, that the virtual machine system disk will stored in the Apps library (NFS repository).
The PUT on a template definition is only designed for creating template definition lists. A template definition is created in Abiquo to provide users with information about the templates they have access to. When users select a template to add to their Apps Library, that template will be downloaded using the links to the template components. This means that changes to the values stored for the template in Abiquo are not made to the template in the remote template repository.
You can simulate a download from a remote repository to the appliance library by exposing a template disk via HTTP.
The post to create a virtual machine template definition takes a link to an OVF file. The API will retrieve this OVF file and download the associated files (disk file, icon).
For example to change the name of a template.