Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:c:control_plane [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:c:control_plane [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Control Plane ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | The Control Plane supports operational coordination among [[dido: | ||
| + | |||
| + | The Control Plane does not normally carry domain truth. It coordinates how Nodes operate, but it does not replace the Data Plane, Policy and Release Plane, Health and Observability Plane, or Audit and Provenance Plane. | ||
| + | |||
| + | A later implementation profile may realize Control Plane interactions through DDS Topics, service interfaces, message queues, APIs, configuration channels, or other runtime mechanisms. Those mechanisms do not redefine the Control Plane. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //Runtime Plane supporting operational coordination among [[dido: | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from FX Demo Reference Architecture, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | The Control Plane is not a DDS Domain, a DDS Topic, a Kubernetes namespace, a configuration file, a command protocol, or a deployment environment. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A command requesting a [[dido: | ||