correct framing: ovn-central metal-internal binding is architecturally right and STAYS; cert bug separate
Operator: ovn-central IS a metal-internal service by the plane's intended purpose.
D-052 explicitly categorizes OVN NB/SB DB (ovsdb*) under metal-internal;
ovn-central has no public/admin API endpoint and all functional endpoints already
bind metal-internal, so the '' default belongs there too. The metal-admin default
was an API-charm convention mis-inherited by a non-API service.

What was wrong was ONLY my premise that the rebind would fix the cert bug -- it
does not. The binding (correct categorization) and the cert failure (charm
LP #2044324, server-cert request/response) are SEPARATE. The D-052 amendment
stands on architectural grounds; the binding is retained.

CURRENT-STATE and the D-052 amendment corrected accordingly. Next: bounce the
certificates relation to force a fresh exchange against the correct single-plane
baseline.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf
1 parent ff8e0d5 commit 580fc067a002f9d486045d6d2c76f6f9c3079c08
@JANeumatrix JANeumatrix authored 2 hours ago
Showing 2 changed files
View
docs/CURRENT-STATE.md
View
docs/design-decisions.md