Projects and Quota

From bwCloud-OS
Revision as of 11:29, 17 October 2025 by Admin (talk | contribs) (Created page with "{{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> <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> <li>Instances cannot be '''moved between...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
In a Nutshell
  • Each bwCloud-OS project has predefined quotas for vCPU, RAM, storage, and networks. Quota increases can be requested via the bwSupportPortal
  • 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.
  • Instances cannot be moved between projects directly. Use snapshots and volume transfer as described here.


General

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 Support Portal:

SUBJECT:        NEW_QUOTA
MOTIVATION:     TEXT
USER_UUID:      UUID
PROJECT_UUID:   UUID (or ask for a new one) 
NUMBER_VM::     INTEGER
RAM_GB:         INTEGER
VCPU:           INTEGER
STORAGE_GB:     INTEGER
SPECIAL_QUOTA:  TEXT
CUT_OFF_DATE:   dd.mm.yyyy

We will check your request and, if possible, grant the request.

Group Projects

For which situations is a group project useful?

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.

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 ~/.ssh/authorized_keys. A group project is then not necessary.

How can I get a group project?

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:

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

Write us a Ticket. We will check your request and, if possible, grant the request.

Are the group members alterable?

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:

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

Write us a Ticket. We will check your request and, if possible, grant the request.

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.

The target region and project can be choosen via the button at the top left of the dashboard.

File:Select project region.png

Is the specification of a group owner necessary? Why?

The data of the person who will be entered as the owner of the group project is necessary for the following reasons:

  • 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?

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?

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.

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.

How do I move an instance to another project?

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
  1. Create a Snapshot/ a shadow copy of the instance. -> Snapshot appears under 'Images'.
  2. Under Images from the snapshot create a Volume. -> The volume appears under Volumes.
  3. Under Volumes create a Transfer for the volume and note the Transfer ID and the Authorization Key.
Target Project
  1. Under Volumes select Accept transfer.
  2. Specify the saved Transfer ID and Authorization Key.-> The volume appears under Volumes.
  3. Convert/upload the volume to an Image. -> The image appears under Images (, this may take some time).
  4. Under Images start the image.

Special information for users at the University of Stuttgart

Special rules apply to users at the University of Stuttgart, which are explained in more detail here.