udlm-dcm-split: separate the UDLM substrate from DCM#58
Draft
croadfeldt wants to merge 1 commit into
Draft
Conversation
Concept gate for the UDLM/DCM split: the boundary rule, the wire-compatibility model, what moves, and repo mechanics. Concept-first; no files move until this lands agreement. Signed-off-by: Chris Roadfeldt <chris@roadfeldt.com>
croadfeldt
force-pushed
the
enh/udlm-dcm-split
branch
from
0d0eb52 to
a07fcce
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
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.
Concept gate for splitting
dcminto a wire-compatible substrate (UDLM) and a realization (DCM). Asks for agreement on the boundary rule and the compatibility model before any files move.Key points: the "could a peer choose differently?" boundary test; wire-compatible (not implementation-portable) — the K8s API+CRDs vs controllers precedent; 22/18/21 + 7-new classification;
dcm-project/udlmalready exists, so this is alignment, not creation.Follows the repo's discuss-first norm — draft, pending team re-engagement. Authored with the Red Hat FlightPath team.