Guide: Project and Quota: Difference between revisions
Jump to navigation
Jump to search
| Line 47: | Line 47: | ||
!'''ram_gb''' | !'''ram_gb''' | ||
!'''volumes''' | !'''volumes''' | ||
!BEH/Tag | ! style="border-right: 3px solid #a2a9b1;" | BEH/Tag | ||
!'''volumes_gb''' | !'''volumes_gb''' | ||
!'''backups''' | !'''backups''' | ||
| Line 63: | Line 63: | ||
|0 | |0 | ||
|0 | |0 | ||
| | | style="border-right: 3px solid #a2a9b1;" | | ||
|0 | |0 | ||
|0 | |0 | ||
| Line 79: | Line 79: | ||
|1 | |1 | ||
|10 | |10 | ||
|4 | | style="border-right: 3px solid #a2a9b1;" |4 | ||
|100 | |100 | ||
|30 | |30 | ||
| Line 95: | Line 95: | ||
|2 | |2 | ||
|10 | |10 | ||
|7 | | style="border-right: 3px solid #a2a9b1;" |7 | ||
|100 | |100 | ||
|30 | |30 | ||
| Line 105: | Line 105: | ||
|20 | |20 | ||
|10 | |10 | ||
|} | |} | ||
== Examples == | == Examples == | ||
Revision as of 08:05, 29 May 2026
➡️ Back to the FAQ for Projects and Quota.
Quota defines the resource limits allocated to a project, such as vCPUs, RAM, networks, and storage
Project and eligibility
Before a quota can be set for a project, in advance an entitlement/ eligibility needs to be granted to the project 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
The supported quota packages are described in the table below.
| quota flavor | Note |
|---|---|
| empty | Fallback. Every user owns this. 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. See custom-eligibility. |
Each quota flavor is associated with resources granted to projects.
| quota flavor | instances | cores | ram_gb | volumes | BEH/Tag | 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 | 4 | 100 | 30 | 300 | 10 | 10 | 1 | 0 | 20 | 10 |
| xtiny_1 | 2 | 2 | 2 | 10 | 7 | 100 | 30 | 300 | 10 | 10 | 1 | 0 | 20 | 10 |
Examples
Project and eligibility examples
Example project and eligibility 1
In the illustration is a life cycle for a project presented.
- First, User I registers for the bwCloud-OS. At this moment, he/she is holding one Eligibility A. Automatic is a start project with a quota created. Only User I is member of this project.
- Later on, the user holds an additional and larger Eligibility B, granted by his/her home organization. After a request for quota change more quota is granted, and the link for the associated eligibility is updated.
- User II holds no eligibility; hence, he/she can login to the bwCloud-OS, but can't use compute resources. User I wants to share the resources of start project I with User II. After the request for a new project member, User II is also able to use compute resources. The former assigned eligibility will be free for use again.
