Guide: Project and Quota: Difference between revisions

From bwCloud-OS
Jump to navigation Jump to search
← Older edit
VisualWikitext
As1844 (talk | contribs)
intern, Administrators
237 edits
No edit summary
Admin (talk | contribs)
Bureaucrats, Interface administrators, intern, Suppressors, Administrators, translationadmin, translator
883 edits
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
➡️ '''Back to the FAQ for [[Projects and Quota]].'''
➡️ '''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 ==
== Project and eligibility ==
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.
Before a quota can be set for a project, in advance an [[Guide: Entitlement & Eligibility|entitlement/ eligibility]] needs to be granted to the project owner.


* Each project is associated with an eligibility hold by the owner of the project.
* Each project is associated with an eligibility hold by the owner of the project.
Line 14: Line 16:
|-
|-
|empty
|empty
|Default case. User can’t generate costs. See [[Guide: Entitlement & Eligibility#Empty eligibility|empty eligibility.]]
|Fallback. Every user owns this. User can’t generate costs. See [[Guide: Entitlement & Eligibility#Empty-eligibility|empty-eligibility.]]
|-
|-
|tiny_1
|tiny_1
Line 35: Line 37:
|-
|-
|custom
|custom
|User can choose the quota to be requested.
|User can choose the quota to be requested. See  [[Guide: Entitlement & Eligibility#Custom-eligibility|custom-eligibility]].
|}
|}
Each quota flavor is associated with resources granted to [[Projects and Quota|projects]].
Each quota flavor is associated with resources granted to [[Projects and Quota|projects]].
Line 45: Line 47:
!'''ram_gb'''
!'''ram_gb'''
!'''volumes'''
!'''volumes'''
! style="border-right: 3px solid #a2a9b1;" | BEH/day
!'''volumes_gb'''
!'''volumes_gb'''
!'''backups'''
!'''backups'''
Line 60: Line 63:
|0
|0
|0
|0
| style="border-right: 3px solid #a2a9b1;" |
|0
|0
|0
|0
Line 75: Line 79:
|1
|1
|10
|10
| style="border-right: 3px solid #a2a9b1;" | 4
|100
|100
|30
|30
Line 90: Line 95:
|2
|2
|10
|10
| style="border-right: 3px solid #a2a9b1;" | 7
|100
|100
|30
|30
Line 105: Line 111:
|4
|4
|20
|20
| style="border-right: 3px solid #a2a9b1;" | 14
|200
|200
|60
|60
Line 120: Line 127:
|8
|8
|20
|20
| style="border-right: 3px solid #a2a9b1;" | 26
|200
|200
|60
|60
Line 135: Line 143:
|16
|16
|40
|40
| style="border-right: 3px solid #a2a9b1;" | 52
|400
|400
|120
|120
Line 150: Line 159:
|32
|32
|40
|40
| style="border-right: 3px solid #a2a9b1;" | 100
|400
|400
|120
|120
Line 165: Line 175:
|*
|*
|*
|*
| style="border-right: 3px solid #a2a9b1;" |
|*
|*
|*
|*
Line 173: Line 184:
| valign="top" |*
| valign="top" |*
|*
|*
|
|*
|}
 
 
Below is the basic translation for calculating Booking Units (BEH). For full details and the complete calculation basis, please refer to the [https://wiki.bwcloud-os.de/index.php/Booking_Units Booking Units page].
 
{| class="wikitable"
|+
! Resource
! BEH/Day
|-
| 1 vCPU
| 1
|-
| 1 GB RAM
| 2
|-
| 10 GB Disk
| 1
|}
|}


Line 185: Line 214:
# 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.
# 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 [[Projects and Quota#How can I request an additional quota?|request for quota change]] more quota is granted, and the link for the associated eligibility is updated.
# Later on, the user holds an additional and larger ''Eligibility B'', granted by his/her home organization. After a [[Projects and Quota#How can I request an additional quota?|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 [[Projects and Quota#Can project members be changed?|request for a new project member]], ''User II'' is also able use compute resources.
# ''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 [[Projects and Quota#Can project members be changed?|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.


[[File:Example project eligibility.drawio.png|thumb|Relationship between project and eligibility.]]
[[File:Example project eligibility.drawio.png|thumb|Relationship between project and eligibility.]]

Latest revision as of 08:18, 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.

List of supported quota flavors
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.

Resources associated with each quota flavor
quota flavor instances cores ram_gb volumes BEH/day 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
medium_1 4 4 4 20 14 200 60 600 10 10 1 1 20 20
xmedium_1 8 8 8 20 26 200 60 600 10 10 1 1 20 20
large_1 16 16 16 40 52 400 120 1200 20 20 2 2 20 40
xlarge_1 32 32 32 40 100 400 120 1200 20 20 2 2 20 40
custom * * * * * * * * * * * * *


Below is the basic translation for calculating Booking Units (BEH). For full details and the complete calculation basis, please refer to the Booking Units page.

Resource BEH/Day
1 vCPU 1
1 GB RAM 2
10 GB Disk 1

Examples

Project and eligibility examples

Example project and eligibility 1

In the illustration is a life cycle for a project presented.

  1. 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.
  2. 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.
  3. 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.
Relationship between project and eligibility.
Retrieved from "https://wiki.bwcloud-os.de/index.php?title=Guide:_Project_and_Quota&oldid=2273"