...
You can rename and change descriptions of any VM template (or instance) in the catalogue, even if the template is used by a virtual appliance in the datacenter (deployed or undeployed)
Any user with the appropriate privileges can create an instance of a template, and the instance will be stored in the user’s enterprise
You cannot remove a master template if there is an instance in any enterprise. As a cloud admin user, you will need to switch to each enterprise and check the repository for instances. Or you can check in the repository file system
You cannot remove scopes to “unshare” a template if it is being used by any virtual appliance in an enterprise in the datacenter
You can remove a template disk from the filesystem to make the template Unavailable to users. If you later replace the template disk with the exact same disk, then the template will become Available againavailable again
When you make a shared template unavailable, other enterprises cannot deploy it, but it may not be marked as unavailable in the catalogue of other enterprises until you refresh your catalogue.
You can update a template disk using the UI or API, and as part of this process, you will update the template definition in Abiquo. Follow the instructions for the Abiquo UI or API. After you update a template disk, users will deploy VMs with the new disks
...