Projects and Quota: Difference between revisions

From bwCloud-OS
Jump to navigation Jump to search
No edit summary
 
(87 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{InANutshell|<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>
<span id="In-a-Nutshell"></span>
<li>'''Group projects''' allow shared access to resources. Members  can manage instances collaboratively. Quotas can be assigned in multiple regions. Every group project requires a named '''owner''' as the primary contact. </li>
{{InANutshell|
<li>Instances cannot be '''moved between projects''' directly. Use snapshots and volume transfer as described
<li>'''(Group-)Projects''' allow shared access to resources. Project members  can manage instances collaboratively. A designated '''project owner''' is required to manage the project and act as the main contact.</li>
  [[Storage#Download_Volumes_or_Images{{!}}here]].</li>
<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>
}}
<li>Quotas can be assigned to a project in multiple [[Registration#Regions|regions]].</li>
<li>Instances cannot be moved between projects directly. Use snapshots and '''volume transfer''' instead, as described
  [[#Instance-Transfer|here]].</li>}}




__TOC__
__TOC__
= (Group) Projects =
'''➡️ More information in the guide about [[Guide: Project and Quota|Project and Quota]].'''


== In which situations is a new (group) project useful? ==
<span id="Group-Project"></span>


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


=Group Projects =
* '''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 [[Registration#Regions|regions]]'''


== For which situations is a group project useful? ==
Such collaboration is also supported through the use of '''access tokens''' ([[Programmatic Access and Automation#Application Credentials|Application Credentials]]).
In group projects, several users can share its resources. Group projects are therefore suitable for
* Joint administration of servers with an operational character,
* Part of teaching and learning scenarios in which several students or participants are to carry out joint exercises etc.
* Projects in which users from several bwCloud-OS regions work together and
* long-term project where the person in charge may change.


This is also possible through the use of access tokens.
'''📌''' '''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'''.


If only several people need to be able to access an instance of the bwCloud-OS, it is '''sufficient to store the SSH keys''' in <code>~/.ssh/authorized_keys</code>. A group project is then not necessary.
== What does resource administration look like in a project? ==
<span id="Group-Project-Administration"></span>


== How can I get a group project? ==
OpenStack uses a basic role and rights model:
Only a bwCloud registered user can be part of the project. Moreover, please refer to the information about the project owner.
 
Answer the points below and use that template for your request:
* There is the role of '''“'''Administrator'''”''', which is reserved exclusively for members of the bwCloud-OS operations team.
<pre>
* All regular users have the same standard user permissions.
SUBJECT:        NEW_PROJECT
 
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 (group) project? ==
 
=== Gen2: ===
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:
 
* 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 [[Projects and Quota#Group-Project-Owner|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:
<pre>SUBJECT:        NEW_PROJECT
MOTIVATION:    TEXT
REGION:        NAME
REGION:        NAME
MOTIVATION:     TEXT
PROJECT_NAME:   NAME
OWNER_UUID:    UUID
OWNER_UUID:    UUID
PROJECT_NAME:  NAME (maximum 16 characters)
MEMBER_UUIDS:  UUID, UUID, ...
MEMBER_UUIDS:  UUID, UUID, ...
NUMBER_VM::    INTEGER
NUMBER_VM:     INTEGER
RAM_GB:        INTEGER
RAM_GB:        INTEGER
VCPU:          INTEGER
VCPU:          INTEGER
STORAGE_GB:    INTEGER
STORAGE_GB:    INTEGER
SPECIAL_QUOTA:  TEXT
CUT_OFF_DATE:  dd.mm.yyyy</pre>'''📌''' '''Note:''' Members of the '''University of Stuttgart''' are subject to '''special rules''', which are explained in detail [[Custom Rules|here]].
=== '''Gen3:''' ===
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:
* Only users who are already '''registered in bwCloud-OS''' can be [[Projects and Quota#Can project members be changed?|added as '''project members''']].
* For granting [[Guide: Project and Quota|project quota]] you need a respective [[Entitlement & Eligibility#How can I find out which entitlements I am owning?|eligibility]].
* [[Entitlement & Eligibility#How can I find out which entitlements I am owning?|Check for holding the eligibility]].
* The owner of the eligibility will become the project owner.
Please use the following '''template''' when submitting your request:
<pre>SUBJECT:        "Request new project"
MOTIVATION:    TEXT
REGION:        NAME
MEMBER_UUIDS:  UUID, UUID, ...
QUOTA_FLAVOR:  NAME
SPECIAL_QUOTA:  TEXT
CUT_OFF_DATE:  dd.mm.yyyy</pre>
== Why is it necessary to specify a project owner? ==
<span id="Group-Project-Owner"></span>
The person designated as the '''project owner''' is needed for several important reasons:
# '''Billing and accountability''':  [[Guide: 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.
# '''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.
The project owner is always a member of the project.
== 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'''.
== How can I change the eligibility and ownership of a project? ==
=== Gen2 ===
If you currently own the project, you can request this via a [https://bw-support.scc.kit.edu/ ticket]. The new owner needs to respond within the ticket as well.
=== Gen3 ===
To request the change of the [[Entitlement & Eligibility#How can I find out which entitlements I am owning?|eligibility]] assigned to the project, please provide the following information in a [https://bw-support.scc.kit.edu/ Ticket]. Please note:
* [[Entitlement & Eligibility#How can I find out which entitlements I am owning?|Check for holding the new eligibility]].
* The owner of the new eligibility will be the (new) owner of the project.
* If you currently own the project and are holding additional [[Guide: Entitlement & Eligibility|eligibility]], you can request this. If a second user is holding the new eligibility, the second user needs to respond within the ticket as well.
Please use the following '''template''' when submitting your request:<pre>
SUBJECT:        "Change eligibility"
MOTIVATION:    TEXT
OWNER_UUID:    UUID
PROJECT_UUID:  UUID
QUOTA_FLAVOR:  NAME
SPECIAL_QUOTA:  TEXT
SPECIAL_QUOTA:  TEXT
CUT_OFF_DATE:  dd.mm.yyyy
CUT_OFF_DATE:  dd.mm.yyyy
</pre>
</pre>The [[Guide: Project and Quota#Example project and eligibility 1|Project-Eligibiity link]] will be updated afterward.
Write us a [https://bw-support.scc.kit.edu/ Ticket]. We will check your request and, if possible, grant the request.
 
== Can project members be changed? ==
<span id="Group-Project-Member-Change"></span>
 
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.


== Are the group members alterable? ==
To request member changes, please submit a [https://bw-support.scc.kit.edu/ support ticket] and provide the following information using this '''template''':<pre>
At bwCloud-OS registered users can be added to a group project. Members can also be removed from the project. Requests to change group members can only be made by the group owner.  
Answer the questions below and use the template for your request:
<pre>
SUBJECT:        MEMBER_PROJECT
SUBJECT:        MEMBER_PROJECT
NEW_OWNER:      UUID
NEW_OWNER:      UUID
Line 52: Line 127:
MEMBERS_REMOVE:  UUID, UUID, ...
MEMBERS_REMOVE:  UUID, UUID, ...
</pre>
</pre>
Write us a [https://bw-support.scc.kit.edu/ Ticket]. We will check your request and, if possible, grant the request.


== How can I switch between projects? ==
== How can I switch between projects? ==
A user can be a member of several group projects. The quota of a project is bound to exactly one bwCloud-OS region.
<span id="Project-Selection"></span>


The target region and project can be choosen via the button at the top left of the dashboard.
A user can be a member of multiple projects, and projects can have quotas in multiple bwCloud-OS [[Registration#Regions|regions]].


[[File:Select project region.png|center|thumb|551x551px]]
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]]


== Is the specification of a group owner necessary? Why? ==
== Can I move an instance to another project? ==
The data of the person who will be entered as the owner of the group project is necessary for the following reasons:
<span id="Instance-Transfer"></span>
* If we introduce a service and cost allocation, the invoice of this group project will be sent to the location of the group owner. The group owner(s) can of course be changed in the further course.
* The group owner(s) serves as contact person for us in case of incidents, inquiries etc.
* The group owner(s) communicates with us regarding member administration and authorizes the addition / removal of persons (otherwise, we cannot decide whether another person is authorized to do so — also because all group members have the same administrative rights)
* Each member of this group project has the same rights (start, stop, delete VMs etc).


== Can the group owner be a functional account? ==
Instances cannot be directly moved between projects. However, you can use the following workaround, provided the target project has sufficient available quota:
No, all identifiers must be assigned to individual persons. This applies to both: the group owner(s) and the members of the group project. Group projects are no exception in this respect, the same rules apply here as for individual user projects.


== What does the administration of resources (instances, images, etc.) look like in a group project? ==
'''In the Source Project:'''
OpenStack has a very simple rights and role model: there is the role of "Administrator:in", who is allowed to do everything and see everything, and there is the normal user:in. The "Administrator" role is reserved for members of the bwCloud-OS operating group. Members of bwCloud-OS have the normal standard permissions.
# Create a '''snapshot''' of the instance. The snapshot will appear under '''Images'''.
# From the snapshot, create a '''volume'''. The volume will appear under '''Volumes'''.
# Create a '''transfer''' for the volume and record the '''Transfer ID''' and '''Authorization Key'''.
'''In the Target Project:'''
# Go to '''Volumes''' and select '''Accept Transfer'''.
# Enter the recorded '''Transfer ID''' and '''Authorization Key'''. The volume will now appear under '''Volumes'''.
# 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.


A group project is therefore no different from a personal user:in project. There are only more than one person assigned to this project. This also means that any member of a group project can see all resources (running instances, security groups, images, etc.), create new resources, edit or delete them. A group project is therefore particularly suitable for scenarios in which several people look after resources on an equal footing, for example for the operation of web servers.
= Project Quota =
'''➡️ More information in the guide about [[Guide: Project and Quota|Project and Quota]].'''


== How do I move an instance to another project? ==
== How can I request an additional quota? ==
An instance cannot be moved to another project per se. However, the following work around is possible. rerequisite is appropriate quota in the target project.
; Source Project
# Create a Snapshot/ a shadow copy of the instance. -> Snapshot appears under 'Images'.
# Under Images from the snapshot create a Volume. -> The volume appears under Volumes.
# Under Volumes create a Transfer for the volume and note the Transfer ID and the Authorization Key.
; Target Project
# Under Volumes select Accept transfer.
# Specify the saved Transfer ID and Authorization Key.-> The volume appears under Volumes.
# Convert/upload the volume to an Image. -> The image appears under Images (, this may take some time).
# Under Images start the image.


 
=== '''Gen2:''' ===
= Quota =
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''':
 
== Project Quota ==
'''Quota''' refers to the resource limits assigned to a project – such as '''vCPUs''', '''RAM''', '''networks''', and '''storage'''. There are two types of projects:
* '''Private User Project:''' Owned by a single individual; no additional members can be added. Quotas depend on the region and the assigned entitlements.
* '''Group Project:''' Multiple users collaborate and can flexibly allocate (quota) resources.
 
== Request Quota increase ==
Answer the points below and use that template for your request via our [https://bw-support.scc.kit.edu/ Support Portal:]


<pre>
<pre>
Line 104: Line 163:
MOTIVATION:    TEXT
MOTIVATION:    TEXT
USER_UUID:      UUID
USER_UUID:      UUID
PROJECT_UUID:  UUID (or ask for a new one)
PROJECT_UUID:  UUID  
NUMBER_VM::    INTEGER
NUMBER_VM:     INTEGER
RAM_GB:        INTEGER
RAM_GB:        INTEGER
VCPU:          INTEGER
VCPU:          INTEGER
Line 111: Line 170:
SPECIAL_QUOTA:  TEXT
SPECIAL_QUOTA:  TEXT
CUT_OFF_DATE:  dd.mm.yyyy
CUT_OFF_DATE:  dd.mm.yyyy
</pre>
</pre>📌 '''Note:''' 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.


We will check your request and, if possible, grant the request.
=== Gen3: ===
= Specific rules for individual  Institutions  =
To request additional quota please request the [[Projects and Quota#How can I change the eligibility and ownership of a project?|change of the eligibility]]. Please note:


Special rules apply to users at the University of Stuttgart, which are explained in more detail [[Stuttgart university quota|here]].
* For the [[Guide: Project and Quota|project quota]] you need a respective [[Entitlement & Eligibility#How can I find out which entitlements I am owning?|eligibility]].

Latest revision as of 16:20, 2 February 2026

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


(Group) Projects

➡️ More information in the guide about Project and Quota.

In which situations is a new (group) 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 (group) project?

Gen2:

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

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

Gen3:

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

Please use the following template when submitting your request:

SUBJECT:        "Request new project"
MOTIVATION:     TEXT
REGION:         NAME
MEMBER_UUIDS:   UUID, UUID, ...
QUOTA_FLAVOR:   NAME
SPECIAL_QUOTA:  TEXT
CUT_OFF_DATE:   dd.mm.yyyy

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.

The project owner is always a member of the project.

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.

How can I change the eligibility and ownership of a project?

Gen2

If you currently own the project, you can request this via a ticket. The new owner needs to respond within the ticket as well.

Gen3

To request the change of the eligibility assigned to the project, please provide the following information in a Ticket. Please note:

  • Check for holding the new eligibility.
  • The owner of the new eligibility will be the (new) owner of the project.
  • If you currently own the project and are holding additional eligibility, you can request this. If a second user is holding the new eligibility, the second user needs to respond within the ticket as well.

Please use the following template when submitting your request:

SUBJECT:        "Change eligibility"
MOTIVATION:     TEXT
OWNER_UUID:     UUID
PROJECT_UUID:   UUID 
QUOTA_FLAVOR:   NAME
SPECIAL_QUOTA:  TEXT
CUT_OFF_DATE:   dd.mm.yyyy

The Project-Eligibiity link will be updated afterward.

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 switch between projects?

A user can be a member of multiple projects, and projects can have quotas 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.

Project Quota

➡️ More information in the guide about Project and Quota.

How can I request an additional quota?

Gen2:

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

📌 Note: 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.

Gen3:

To request additional quota please request the change of the eligibility. Please note: