demos: add cloud-burst example manifests - #15
Merged
Conversation
|
Non-conforming commit subjects (expected
Amend with |
Add reference manifests under demos/grid-cloud-burst/example-manifests/ that make the demo's policy concepts concrete and applyable. Copied from the working demo: local sim pools, GridNetwork with composed burst policies, local pool + OpenAI/Bedrock overflow providers, consumer Praxis with token_rate_limit enforcement: soft, provider Praxis, and a README mapping each file to a user story with apply order and placeholder notes. No credentials are included. Signed-off-by: Brent Salisbury <bsalisbu@redhat.com>
nerdalert
force-pushed
the
add-cloud-burst-example-manifests
branch
from
August 25, 2026 19:57
bde399c to
b2782e0
Compare
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.
What
Adds reference manifests under
demos/grid-cloud-burst/example-manifests/so the cloud-burst demo's policy concepts are concrete and applyable, not just described in prose.01-local-sim-pools.yaml02-gridnetwork.yamlscoringPolicy/admissionPolicy(stabilized enter 0.85 / exit 0.70) /selectionPolicy+placementPolicy/routingPolicy. Bursting emerges from composition; there is no dedicated switch03-grid-sites-and-providers.yamlbackendKind: local) + OpenAI overflow (backendKind: api_provider,auth.manual: true) — distinct backend class keeps overflow in its own fallback group04-bedrock-overflow.yaml05-consumer-praxis-soft-quota.yamltoken_rate_limitwithenforcement: soft(over-budget → served + flagged, never 429) alongsideintelligent_route06-provider-praxis.yamlpeer_identity_trust(fail-closed) →provider_route→credential_injectREADME.mdNotes
README.mddocuments apply order and how each file maps to a user story.openai-api-keysecret viaauth.manual: true.demos/grid-cloud-burst/.