Update documentation for per-AZ ProjectQuota, FlavorGroupCapacity, and usage reconciler#833
Merged
Merged
Conversation
…reconciler
Reflect that ProjectQuota is now one CRD per (project × AZ) pair with naming
convention quota-{projectID}-{az}, document the usage reconciler that pre-computes
AssignedInstances and UsedResources into CommittedResource status, and add
FlavorGroupCapacity and ProjectQuota to the apis.md CRD overview.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
mblos
approved these changes
May 11, 2026
Contributor
Test Coverage ReportTest Coverage 📊: 69.1% |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates documentation to reflect recent architectural changes in the committed resource reservation system. The ProjectQuota CRD is now scoped per (project × availability zone) pair rather than one per project, using the naming convention quota-{projectID}-{az}. The Quota API creates one CRD per AZ combination, and a quota controller reconciles TotalUsage and PaygUsage into the status by watching CommittedResource and Hypervisor CRDs. The Report-Usage endpoint now reads pre-computed VM-to-commitment assignments from CommittedResource.Status fields (AssignedInstances, UsedResources, LastUsageReconcileAt, UsageObservedGeneration) populated by a dedicated usage reconciler, rather than computing assignments inline at request time. FlavorGroupCapacity and ProjectQuota CRD descriptions are added to the apis.md CRD overview section to complete the picture of scheduling-related custom resources.