Allow clubs to create cloud resources #104
Labels
No Label
priority
high
priority
low
priority
medium
priority
very high
BUG
Feature
High Priority
Low Priority
Medium Priority
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: public/pyceo#104
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Allow club reps to create cloud accounts for clubs. The resources should be deleted or disabled when the club no longer has any active club reps.
Should all club reps be allowed to create cloud accounts owned by themselves, or somehow under the "club name"?
Resource limitations?
The cloud account should be under the club name. CloudStack allows us to create groups of people who can share resources (called "projects"). Harbor (our Docker image registry) also has projects. For Kubernetes, we can create a new namespace for their club.
Should probably be the same as the limits for a regular member, I think. If they need more they can always ask.