Guide: Project and Quota: Difference between revisions

Revision as of 12:11, 2 February 2026

➡️ Back to the FAQ for Projects and Quota.

For quota project to be assigned to a project, this need to be granted in advance by assigning an entitlement/ eligibility to the owner.

Each project is associated with an eligibility hold by the owner of the project.
The maximal quota a user can request is restricted by the quota flavor of his/her eligibility.

The supported quota packages are described in the table below.

List of supported quota flavors
quota flavor	Note
empty	Default case. User can’t generate costs. See empty eligibility.
tiny_1
xtiny_1
medium_1
xmedium_1
large_1
xlarge_1
custom	User can choose the quota to be requested.

Each quota flavor is associated with resources granted to projects.

Resources associated with each quota flavor
quota flavor	instances	cores	ram_gb	volumes	volumes_gb	backups	backups_gb	networks	subnets	routers	floating_ips	security_groups	snapshots
empty	0	0	0	0	0	0	0	0	0	0	0	20	0
tiny_1	1	1	1	10	100	30	300	10	10	1	0	20	10
xtiny_1	2	2	2	10	100	30	300	10	10	1	0	20	10
medium_1	4	4	4	20	200	60	600	10	10	1	1	20	20
xmedium_1	8	8	8	20	200	60	600	10	10	1	1	20	20
large_1	16	16	16	40	400	120	1200	20	20	2	2	20	40
xlarge_1	32	32	32	40	400	120	1200	20	20	2	2	20	40
custom	*	*	*	*	*	*	*	*	*	*	*	*

@@ Line 1: / Line 1: @@
+➡️ '''Back to the FAQ for [[Projects and Quota]].'''
+== Project and eligibilities ==
+For quota project to be assigned to a project, this need to be granted in advance by assigning an [[Guide: Entitlement & Eligibility|entitlement/ eligibility]] to the owner.
+* Each project is associated with an eligibility hold by the owner of the project.
+* The maximal quota a user can request is restricted by the quota flavor of his/her eligibility.
 == List of quota flavors ==