Administrators can set repository limits to restrict usage of Apps library disk space (NFS repository storage) for an enterprise and for an enterprise in a datacenter. When users perform repository operations, the platform tests repository limits as described in the following table, adding the size of the disks or the estimated size of the disks to the currently used space.
|Templates added by enterprise|
|Instances created by enterprise|
Estimated instance size is based on the template disk size in the Abiquo database.
|Conversions to other hypervisor formats||Users cannot control the number of conversions|
|Public cloud and Docker templates||These are not stored in the Abiquo repository|
|Shared templates belonging to the enterprise|
|Shared templates belonging to another enterprise|
|Promoted templates||A copy of an existing template is made|
|Capturing a VM||Limits are not tested during capture because no template is added to the repository at this time. |
Any VM template operations based on a captured machine (e.g. instances) are tested
|Unavailable (Deleted) templates||Unavailable templates do not have a disk file, so they are not counted in repository limit calculations|
Examples of creating instances
For example, an enterprise has an NFS hard limit of 500 GB and a soft limit of 475 GB in a datacenter. They have used 481 GB and received a message about exceeding the soft limit. A user belonging to the enterprise creates an instance. The template disk for the VM being instanced occupies 18 GB. However, the real size of the VM disk is 22 GB. The instance creation succeeds because the used space plus the template disk size is lower than the limit. But the Enterprise has now exceeded their hard limit (502 GB > 500 GB), so they cannot create any more instances.