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

Limits (quotas) for projects #6169

Open
stgraber opened this issue Sep 9, 2019 · 0 comments

Comments

@stgraber
Copy link
Member

commented Sep 9, 2019

Projects as they are today are a great way to segment a LXD host, having its own containers, images and profiles (depending on configuration). Combined with RBAC, it's then possible to have some users/groups only have access to specific projects.

But right now, access to a project means you still get to create as many containers as you want, use as much CPU and memory as you want, potentially running the host system out of resources.

We shouldn't try to fix all of this in one shot, but need to put some infrastructure in place for such limits to be implemented. The easiest would be to use the existing project configuration mechanism, adding more configuration keys like:

  • limits.containers (total number of containers that can be held by the project)
  • limits.cpu (maximum number of CPUs that can be assigned to a container OR range of CPUs that may be used)
  • limits.memory (total amount of memory usable by the project)
  • limits.processes (total number of processes usable by the project)

I suggest we do this initial set as a way to prove the concept, we can then add more as we see demand.

@stgraber stgraber added the Feature label Sep 9, 2019
@stgraber stgraber added this to the soon milestone Sep 9, 2019
@stgraber stgraber pinned this issue Sep 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.