Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Who is the Quota Operator? #32

Closed
ultrasaurus opened this issue Jun 29, 2018 · 4 comments
Closed

Who is the Quota Operator? #32

ultrasaurus opened this issue Jun 29, 2018 · 4 comments
Assignees
Labels
usecase/personas Related to usecases and personas of CN security

Comments

@ultrasaurus
Copy link
Member

ultrasaurus commented Jun 29, 2018

What was the original intent of this persona? it seems like it might be more of a cluster of use cases that belongs to another role, rather than a job unto itself.

From reading the use cases, it seems like it is someone who works in the IT org and is responsible for managing the quota settings for their org --- in my experience, this person is sometimes responsible for checking budgets (at least understanding costs) and potentially recommending a increasing capacity

@dshaw notes that in the public cloud, as a developer you run into situations where you need to request additional quota (from what seems like a human, but could be a bot) -- is that a different Quota Operator role?

Discussed in today's SAFE meeting, see notes

@ultrasaurus
Copy link
Member Author

ultrasaurus commented Jun 29, 2018

@sreetummidi @rcolline @ckemper67 what do you think?

@dshaw dshaw assigned dshaw and sreetummidi and unassigned dshaw Jul 13, 2018
@ckemper67
Copy link
Contributor

The intent of the persona was to go beyond restricting SAFE to pure authorization scenarios.

Note that quota is not necessarily a cost control measure. A more important use of quota is to protect your service from abuse. By setting a quota you can make sure that a single customer cannot bring down the service for everybody else (either intentionally or unintentionally). We have seen services that do not implement proper exponential backoff and a simple quota enforcement in front of your service can reduce the impact of the repeated request on the rest of your infrastructure.

The quota for cost control (i.e. a budget) is also interesting and these cost control measures could actually be administered by a different persona. I believe in GCP we call them Billing Administrators and they may have a financial, rather than an engineering background

ultrasaurus added a commit to ultrasaurus/cncf-sig-security that referenced this issue Dec 2, 2018
@ultrasaurus
Copy link
Member Author

Thanks @ckemper67 for your insights on this. I've submitted a PR based on your comment.

Related to this, in the last WG meeting, we discussed proposal to validate personas with some research -- anyone viewing this, may also be interested in commenting on: #109

@lumjjb
Copy link
Contributor

lumjjb commented May 30, 2019

Resolved by #113

@lumjjb lumjjb closed this as completed May 30, 2019
@lumjjb lumjjb added the usecase/personas Related to usecases and personas of CN security label May 30, 2019
Michael-Susu12138 pushed a commit to Michael-Susu12138/tag-security that referenced this issue Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usecase/personas Related to usecases and personas of CN security
Projects
None yet
Development

No branches or pull requests

5 participants