App Deployments (4c-i): per-service resources + footprint + namespace quota#221
Merged
Conversation
… quota
Capacity increment (part 1): make each deployment carry real resource
requests and cap its namespace.
lnvps_compose:
- Service gains resources: { cpu, memory } (k8s quantities; defaults
250m / 256Mi).
- Compose::footprint() sums service cpu/memory + volume sizes into
Footprint { cpu_milli, memory_bytes, storage_bytes }; parse_cpu_milli /
parse_bytes parse k8s quantity strings. 15 unit tests.
lnvps_operator:
- Containers now set requests == limits from resources (Guaranteed QoS,
1:1 / no overcommit).
- The per-namespace ResourceQuota is now applied, sized from
compose.footprint(), so a deployment can't exceed what was provisioned.
Order-time capacity admission (cluster capacity columns + capacity service)
is the next increment. Part of work/app-deployments.md.
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
1 participant
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.
First half of capacity management. Makes each deployment carry real resource requests and caps its namespace at what was provisioned.
lnvps_composeServicegainsresources: { cpu, memory }(Kubernetes quantities; defaults 250m / 256Mi).Compose::footprint()→Footprint { cpu_milli, memory_bytes, storage_bytes }= Σ service cpu/memory + Σ volumesize.parse_cpu_milli(500m/2/1.5) andparse_bytes(512Mi/2Gi/1G/bytes) quantity parsers. 15 unit tests.lnvps_operatorresources(Guaranteed QoS, 1:1 / no overcommit as decided).compose.footprint(), so a misbehaving app can't exceed what it was provisioned (and billed) for.Next (4c-ii)
Order-time admission:
appfootprint columns + staticapp_cluster.capacity_*columns + anAppClusterCapacityService(available = capacity − Σ active footprints) for the customer ordering flow (3b) to accept/reject and pick a cluster in the chosen region.