Projects and Quota: Difference between revisions

From bwCloud-OS
Jump to navigation Jump to search
← Older edit
VisualWikitext
No edit summary
Remove private, user and group project notation
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<span id="In-a-Nutshell"></span>
<span id="In-a-Nutshell"></span>{{InANutshell|<li>Each bwCloud-OS project has predefined '''quotas''' for vCPU, RAM, storage, networks, etc. Quota increases can be requested via the  [https://bw-support.scc.kit.edu/ bwSupportPortal].</li>
{{InANutshell|
<li>'''(Group-)Projects''' allow shared access to resources. Project members can manage instances collaboratively.</li>
<li>Each bwCloud-OS project has predefined '''quotas''' for vCPU, RAM, storage, and networks. Quota increases can be requested via the  [https://bw-support.scc.kit.edu/ bwSupportPortal].</li>
<li>Quotas can be assigned to a project in multiple [[Registration#Regions|regions]].</li>
<li>'''Group projects''' allow shared access to resources. Members can manage instances collaboratively. Quotas can be assigned in multiple [[Registration#Regions|regions]]. A designated '''project owner''' is required to manage membership and act as the main contact. </li>
<li>A designated '''project owner''' is required to manage the project and act as the main contact.</li>}}Cloud resources are encapsulated into different projects.
<li>Instances cannot be moved between projects directly. Use snapshots and '''volume transfer''' instead, as described
[[#Instance-Transfer|here]].</li>
}}


=== Project owner ===
Each project has an [[Entitlements in bwCloud-OS|eligibility]] assigned to it. The owner of the eligibility is always the owner of the project. Only the project owner can request via [https://bw-support.scc.kit.edu/ Ticket] changes on the project. The owner can be changed later if needed.
__TOC__
Quota


__TOC__
(Project-)Quota defines the resource limits allocated to a project, such as vCPUs, RAM, networks, storage, etc.


= Projects =
= FAQ =


== How can I switch between projects? ==
== How can I switch between projects? ==
<span id="Project-Selection"></span>
A user can be a member of multiple projects, and projects can have quota in multiple bwCloud-OS [[Registration#Regions|regions]].
A user can be a member of multiple projects, and projects can have quota in multiple bwCloud-OS [[Registration#Regions|regions]].


To switch between projects and regions, use the '''project/region selector''' button located at the '''top left of the [https://portal.bw-cloud.org/auth/login/?next=/ Dashboard]'''. This allows you to choose the target project and corresponding region for your current session.
To switch between projects and regions, use the project/region selector button located at the top left of the '''[https://portal.bw-cloud.org/ Dashboard]'''. This allows you to choose the target project and corresponding region for your current session.
[[File:Project selection.png|center|thumb|551x551px]]
[[File:Project selection.png|center|thumb|551x551px]]


Line 31: Line 30:
# Go to '''Volumes''' and select '''Accept Transfer'''.
# Go to '''Volumes''' and select '''Accept Transfer'''.
# Enter the recorded '''Transfer ID''' and '''Authorization Key'''. The volume will now appear under '''Volumes'''.
# Enter the recorded '''Transfer ID''' and '''Authorization Key'''. The volume will now appear under '''Volumes'''.
# Convert or upload the volume to an '''image'''. ''This process may take some time''.
# Convert or upload the volume to an '''image'''. The image will appear under '''Images'''''. This process may take some time''.
# Launch a new instance from the image in the target project.
# Launch a new instance from the image in the target project.


=Group Projects =
== In which situations is a new project useful? ==
 
Projects allow multiple users to share and jointly manage resources within a single bwCloud-OS project. This is particularly useful for:
== In which situations is a group project useful? ==
<span id="Group-Project"></span>
Group projects allow multiple users to share and jointly manage resources within a single bwCloud-OS project. This is particularly useful for:


* '''Collaborative administration''' of servers with a '''long-term or operational''' purpose
* '''Collaborative administration''' of servers with a '''long-term or operational''' purpose
Line 46: Line 42:
Such collaboration is also supported through the use of '''access tokens''' ([[Programmatic Access and Automation#Application Credentials|Application Credentials]]).
Such collaboration is also supported through the use of '''access tokens''' ([[Programmatic Access and Automation#Application Credentials|Application Credentials]]).


* '''Note:''' If the only goal is to allow multiple users to connect to the same virtual machine, you can simply add their '''SSH public keys''' to the <code>~/.ssh/authorized_keys</code> file on the VM. In that case, a group project is '''not required'''.
* '''Note:''' If the only goal is to allow multiple users to connect to the same virtual machine, you can simply add their '''SSH public keys''' to the <code>~/.ssh/authorized_keys</code> file on the VM. In that case, a new project is '''not required'''.


== What does resource administration look like in a group project? ==
== What does resource administration look like in a project? ==
<span id="Group-Project-Administration"></span>
OpenStack uses a basic role and rights model:


OpenStack uses a very simple role and rights model:
* There is the role of '''“'''Administrator'''”''', which is reserved exclusively for members of the bwCloud-OS operations team.
 
* All regular users have the same standard user permissions.
* There is the role of '''“Administrator”''', which is reserved exclusively for members of the '''bwCloud-OS operations team'''.
* All regular users — including those in group projects — have the same '''standard user permissions'''.
 
This means that a group project functions the same as a personal project, with one key difference: '''multiple users''' are assigned to the same project.


As a result:
As a result:


* Every group member can '''see all shared resources''' (instances, images, security groups, etc.).
* Every project member can '''see all shared resources''' (instances, images, security groups, etc.).
* All members can '''create, modify, or delete''' resources.
* All members can '''create, modify, or delete''' resources.
* There are '''no internal role distinctions''' within a project — all members have '''equal rights'''.
* There are '''no internal role distinctions''' within a project — all members have '''equal rights'''.


== How can I request a group project? ==
== How can I request a new project? ==
<span id="Group-Project-Application"></span>
To create a new project, you need to submit a [https://bw-support.scc.kit.edu/ Ticket] with specific information about your request. Please note:
To create a group project, you need to submit a [https://bw-support.scc.kit.edu/ support ticket] with specific information about your request. Please note:


* Only users who are already '''registered in bwCloud-OS''' can be added as '''project members'''.
* Only users who are already '''registered in bwCloud-OS''' can be added as '''project members'''.
Line 90: Line 81:
=== Notes ===
=== Notes ===
<span id="Group-Project-Notes"></span>
<span id="Group-Project-Notes"></span>
* Users from the '''University of Stuttgart''' are subject to '''special rules''', which are explained in detail [[Custom Rules|here]].
* Members of the '''University of Stuttgart''' are subject to '''special rules''', which are explained in detail [[Custom Rules|here]].
 
== Why is it necessary to specify a group project owner? ==
<span id="Group-Project-Owner"></span>


== Why is it necessary to specify a project owner? ==
The person designated as the '''project owner''' is needed for several important reasons:
The person designated as the '''project owner''' is needed for several important reasons:


# '''Billing and accountability''':  If cost allocation is introduced in the future, any billing or formal communication related to the group project will be directed to the project owner's institution or department. (Note: The owner can be changed later if needed.)
# '''Billing and accountability''':  [[Charging|Cost allocation]] is introduced with bwCloud-OS (Gen3), any billing or formal communication related to the project will be directed to the project owner's institution.
# '''Primary contact for the bwCloud-OS team''': The project owner acts as the main contact person for the bwCloud-OS team — for operational issues, incidents, and support inquiries.
# '''Primary contact for the bwCloud-OS team''': The project owner acts as the main contact person for the bwCloud-OS team — for operational issues, incidents, and support inquiries.
# '''User and membership management''': The owner is responsible for managing group membership. We can only accept requests to add or remove members from the owner (or a designated replacement), since all group members have the same technical permissions. Otherwise, we cannot verify who has the authority to manage membership.
# '''User and membership management''': The owner is responsible for managing project membership. We can only accept requests to add or remove members from the owner (or a designated replacement), since all project members have the same technical permissions. Otherwise, we cannot verify who has the authority to manage membership.


== Can the project owner be a functional or shared account? ==
== Can the project owner be a functional or shared account? ==
<span id="Group-Project-Owner-Personal"></span>
No. All accounts and identifiers used in bwCloud-OS — including those for '''project owners''' and '''project members''' — must be assigned to '''individual, identifiable persons'''.
No. All accounts and identifiers used in bwCloud-OS — including those for '''project owners''' and '''project members''' — must be assigned to '''individual, identifiable persons'''.


Group projects are '''not an exception''' to this rule. The same identity and accountability requirements apply as for personal projects.
== Can project members be changed? ==
Yes, members of a project can be '''added or removed''' at any time.


== Can group members be changed? ==
'''Only the''' '''project owner''' is authorized to request changes to the project membership.
<span id="Group-Project-Member-Change"></span>


Yes, members of a group project can be '''added or removed''' at any time.


'''Only the''' '''project owner''' is authorized to request changes to the group membership.


To request member changes, please submit  a [https://bw-support.scc.kit.edu/ support ticket] and provide the following information using this '''template''':<pre>
To request member changes, please submit  a [https://bw-support.scc.kit.edu/ support ticket] and provide the following information using this '''template''':<pre>
Line 122: Line 107:
MEMBERS_REMOVE:  UUID, UUID, ...
MEMBERS_REMOVE:  UUID, UUID, ...
</pre>
</pre>
 
== How can I request an additional quota? ==
 
= Project Quota =
Quota defines the resource limits allocated to a project, such as vCPUs, RAM, networks, and storage. Quotas differ depending on the type of project:
 
* '''Private User Projects''' receive initial quotas based on the [[Registration#Regions|region]] and the user's assigned [[Registration#Entitlements|entitlements]].
* '''Group Projects''' allow multiple users to share and flexibly manage the allocated quotas collectively.
 
== How can I request additional quota? ==
<span id="Quota-Increase-Request"></span>
 
To request additional quota, please provide the following information and submit your request via the [https://bw-support.scc.kit.edu/ Support Portal] using the following '''template''':
To request additional quota, please provide the following information and submit your request via the [https://bw-support.scc.kit.edu/ Support Portal] using the following '''template''':


Line 149: Line 124:


=== Notes ===
=== Notes ===
<span id="Project-Quota-Notes"></span>
* The values you provide must represent the '''total desired quota''' for your project '''after''' the increase, '''not''' the additional amount to be added on top of your current quota.
* The values you provide must represent the '''total desired quota''' for your project '''after''' the increase, '''not''' the additional amount to be added on top of your current quota.

Latest revision as of 16:11, 8 January 2026

In a Nutshell
  • Each bwCloud-OS project has predefined quotas for vCPU, RAM, storage, networks, etc. Quota increases can be requested via the bwSupportPortal.
  • (Group-)Projects allow shared access to resources. Project members can manage instances collaboratively.
  • Quotas can be assigned to a project in multiple regions.
  • A designated project owner is required to manage the project and act as the main contact.

Cloud resources are encapsulated into different projects.

Project owner

Each project has an eligibility assigned to it. The owner of the eligibility is always the owner of the project. Only the project owner can request via Ticket changes on the project. The owner can be changed later if needed.

Quota

(Project-)Quota defines the resource limits allocated to a project, such as vCPUs, RAM, networks, storage, etc.

FAQ

How can I switch between projects?

A user can be a member of multiple projects, and projects can have quota in multiple bwCloud-OS regions.

To switch between projects and regions, use the project/region selector button located at the top left of the Dashboard. This allows you to choose the target project and corresponding region for your current session.

Can I move an instance to another project?

Instances cannot be directly moved between projects. However, you can use the following workaround, provided the target project has sufficient available quota:

In the Source Project:

  1. Create a snapshot of the instance. The snapshot will appear under Images.
  2. From the snapshot, create a volume. The volume will appear under Volumes.
  3. Create a transfer for the volume and record the Transfer ID and Authorization Key.

In the Target Project:

  1. Go to Volumes and select Accept Transfer.
  2. Enter the recorded Transfer ID and Authorization Key. The volume will now appear under Volumes.
  3. Convert or upload the volume to an image. The image will appear under Images. This process may take some time.
  4. Launch a new instance from the image in the target project.

In which situations is a new project useful?

Projects allow multiple users to share and jointly manage resources within a single bwCloud-OS project. This is particularly useful for:

  • Collaborative administration of servers with a long-term or operational purpose
  • Teaching or training scenarios, where students or participants need to collaborate
  • Projects that involve users from multiple bwCloud-OS regions

Such collaboration is also supported through the use of access tokens (Application Credentials).

  • Note: If the only goal is to allow multiple users to connect to the same virtual machine, you can simply add their SSH public keys to the ~/.ssh/authorized_keys file on the VM. In that case, a new project is not required.

What does resource administration look like in a project?

OpenStack uses a basic role and rights model:

  • There is the role of “Administrator”, which is reserved exclusively for members of the bwCloud-OS operations team.
  • All regular users have the same standard user permissions.

As a result:

  • Every project member can see all shared resources (instances, images, security groups, etc.).
  • All members can create, modify, or delete resources.
  • There are no internal role distinctions within a project — all members have equal rights.

How can I request a new project?

To create a new project, you need to submit a Ticket with specific information about your request. Please note:

  • Only users who are already registered in bwCloud-OS can be added as project members.
  • The project must have a designated owner. Please review the role of the project owner, who is responsible for managing the project and its quota usage.
  • The project name should be no longer than 16 characters.

Please use the following template when submitting your request: 

SUBJECT:        NEW_PROJECT
MOTIVATION:     TEXT
REGION:         NAME
PROJECT_NAME:   NAME 
OWNER_UUID:     UUID
MEMBER_UUIDS:   UUID, UUID, ...
NUMBER_VM:      INTEGER
RAM_GB:         INTEGER
VCPU:           INTEGER
STORAGE_GB:     INTEGER
SPECIAL_QUOTA:  TEXT
CUT_OFF_DATE:   dd.mm.yyyy

Notes

  • Members of the University of Stuttgart are subject to special rules, which are explained in detail here.

Why is it necessary to specify a project owner?

The person designated as the project owner is needed for several important reasons:

  1. Billing and accountability: Cost allocation is introduced with bwCloud-OS (Gen3), any billing or formal communication related to the project will be directed to the project owner's institution.
  2. Primary contact for the bwCloud-OS team: The project owner acts as the main contact person for the bwCloud-OS team — for operational issues, incidents, and support inquiries.
  3. User and membership management: The owner is responsible for managing project membership. We can only accept requests to add or remove members from the owner (or a designated replacement), since all project members have the same technical permissions. Otherwise, we cannot verify who has the authority to manage membership.

Can the project owner be a functional or shared account?

No. All accounts and identifiers used in bwCloud-OS — including those for project owners and project members — must be assigned to individual, identifiable persons.

Can project members be changed?

Yes, members of a project can be added or removed at any time.

Only the project owner is authorized to request changes to the project membership.


To request member changes, please submit a support ticket and provide the following information using this template:

SUBJECT:         MEMBER_PROJECT
NEW_OWNER:       UUID
PROJECT:         UUID
MEMBERS_ADD:     UUID, UUID, ...
MEMBERS_REMOVE:  UUID, UUID, ...

How can I request an additional quota?

To request additional quota, please provide the following information and submit your request via the Support Portal using the following template: 

SUBJECT:        NEW_QUOTA
MOTIVATION:     TEXT
USER_UUID:      UUID
PROJECT_UUID:   UUID 
NUMBER_VM:      INTEGER
RAM_GB:         INTEGER
VCPU:           INTEGER
STORAGE_GB:     INTEGER
SPECIAL_QUOTA:  TEXT
CUT_OFF_DATE:   dd.mm.yyyy

Notes

  • The values you provide must represent the total desired quota for your project after the increase, not the additional amount to be added on top of your current quota.
Retrieved from "https://wiki.bwcloud-os.de/index.php?title=Projects_and_Quota&oldid=1587"