feat(paas): provisioning plane + full gap register (Nocalhost/BlueMix, box-by-box) - #34
Merged
Merged
Conversation
…ol-plane seam Closes the biggest gap the diagrams expose: we had the substrate but not the server control plane a developer/admin touches. Nocalhost calls it Web+API+Dep; BlueMix calls it SSO+Entitlement+Broker+ Token+BSS. Unified, k8s-native, open, governed. tools/provisioning.py — an Open-Service-Broker-shaped surface: - provision: create a tenant = isolated DevSpace + entitlement tier (quota + backend allowlist), sealed. - bind: issue access — namespace + endpoint (twin default / box) + session. - deprovision: teardown. meter: BSS billing from the admission usage ledger. me: tenant profile. Portal gains /api/me (Watson '/me'-style). Fail-closed on unknown tenant. docs/PAAS_GAP_REGISTER.md — every box OCR'd off the four diagrams (Nocalhost Sidecar + How-It-Works; BlueMix Gen3 + DW-DevOps Gen4), mapped to our stack, graded have/partial/GAP. Names ALL remaining gaps (IDE plugin, remote terminal, SSO, dep-operator, LB+RM-A/B HA, ELK/Grafana, landing page) so nothing hides. Plus the Cloud Foundry / BlueMix analysis: CF invented the buildpack/`cf push` ergonomic but was a non-k8s parallel stack (Diego/Garden/BOSH) buried under BlueMix proprietary lock-in -> community consolidated on k8s (Porter, CNB). Ours is best-of-all: CF's ergonomic (open CNB) + Porter's k8s-native + governance/mesh/sovereign-inference none of them have. capd/provisioning-plane.mesh.capd.json. Tests: +5 provisioning +1 portal = 168 tools tests green.
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.
Closes the biggest gap the four diagrams expose: we had the substrate but not the server control plane a developer/admin touches.
tools/provisioning.py— the unified control planeAn Open-Service-Broker surface: provision (tenant = isolated DevSpace + entitlement tier) → bind (namespace + endpoint twin/box + session) → deprovision; plus meter (BSS billing from the usage ledger) and /me (tenant profile). Portal gains
/api/me. Fail-closed, sealed receipts. Nocalhost's Web+API+Dep and BlueMix's SSO+Entitlement+Broker+Token+BSS — unified, k8s-native, open, governed.docs/PAAS_GAP_REGISTER.md— every box, gradedOCR'd all four diagrams box-by-box → mapped to our stack →
have/partial/GAP. Names all remaining gaps (IDE plugin, remote terminal, SSO, dep-operator, LB+RM-A/B HA, ELK/Grafana, landing page). Plus the Cloud Foundry/BlueMix analysis and why our design is best-of-all.168 tools tests green (+6).