microsoft / microsoft/AzureTRE
User Resource Quota
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
I want to limit the number of user resources that can be created in a workspace by all users and by a single user
Questions:
How does this work with other services, AML compute instance?
Do we need a "points" system, where a user resource has a quota_points, so that we can say, say a 4 core VM, is twice as much as a 2 core VM.
How does this work with workspace services? Do they need a quota?
Would need to prevent parameters that invalidate quota, such as VM size, each one would have to be a new user resource template.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Clarify whether quotas cover user resources, workspace services, and AML compute instances, and agree on whether resource sizes require a points-based model before implementation; done means an agreed quota design and its enforcement scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100