Aleksei Sviridkin 02d1264cdc feat(api): check GPU budgets when a VM or a worker pool is written
A tenant's GPU budget is declared per class as
<class>.gpuclass.cozystack.io/devices and over every class as
gpuclass.cozystack.io/devices. These keys are not pod resources, so no
ResourceQuota enforces them. The proposal hands the check to the
pool-wide admission gate that counts declared sizes; until that gate
is on, the Cozystack API server does it for GPU keys only, with the
inputs and the pool arithmetic that gate reads, so the switch changes
no verdict.

On a VMInstance or KubernetesNodes create or update, every class entry
reserves its count, times maxReplicas for a worker pool, read from the
chart-defaulted values. The tenant pool arithmetic is applied to the
declared resourceQuotas and these entries. Only growth is checked on
an update, so shrinking and unchanged entries pass even in a pool that
is already over budget. Like the gate it stands in for, this is a
read-check-write without a transaction.

The tenant declaration gate already treats GPU keys like any other;
it now reads their pool usage from the class entries, since the
ResourceQuota it reads for other keys never carries them. It also
refuses a key in the GPU budget domain that is not a budget key: the
tenant chart keeps such a key out of the ResourceQuota, so nothing
would enforce it.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-11-03 06:10:08 +03:00
2025-10-08 09:43:34 +05:00
2024-02-08 12:04:32 +01:00

Cozystack Cozystack

GitHub Release Apache-2.0 License Commit activity OpenSSF Best Practices OpenSSF Scorecard CLOMonitor Support

Cozystack

Cozystack is a free and open-source platform and framework for building clouds.

Cozystack is a CNCF Sandbox project that was originally built and sponsored by Ænix.

With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.

Use Cozystack to build your own cloud or provide a cost-effective development environment.

Cozystack user interface

Use-Cases

Documentation

The documentation is located on the cozystack.io website.

Read the Getting Started section for a quick start.

If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.

Versioning

Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.

Contributions

Contributions are highly appreciated and very welcomed!

In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.

You are welcome to take on the fix yourself. Commits are used to generate the changelog, and their author will be referenced in it.

If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.

Community

You are welcome to join us in #cozystack, on either CNCF Slack (get an invite) or Kubernetes Slack (get an invite), in our Telegram group, and at our community meetings. Add them to your Google Calendar or iCal for convenience.

Project documents

Document What it covers
Governance How decisions are made and who makes them
Contributor Ladder How to grow from contributor to maintainer
Maintainers Who maintains the project
Code of Conduct What we expect of each other
Security Policy Reporting a vulnerability, and which releases get fixes
Adopters Who runs Cozystack in production
Roadmap Where the project is going

License

Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.

Commercial Support

A list of companies providing commercial support for this project can be found on official site.

Languages
Go 48%
Shell 37%
TypeScript 6.9%
Go Template 5.3%
Makefile 1.4%
Other 1.2%