What problem does it solve?
This Skill helps you understand how edgion-center acts as the federation hub, turning many Controllers’ published data into a consistent operational view and exposing it via an Admin API, while persisting controller registry state.
Core Features & Use Cases
- Federation hub mental model: Clarifies the reverse-watch flow where Center issues watch requests and Controllers push WatchList/WatchEvent updates back.
- Operational lifecycle & failure modes: Documents startup sequence, registration acceptance rules, heartbeat/timeout behavior, and how offline vs removed controllers are handled.
- Production-grade API surface for operators: Summarizes the Admin HTTP endpoints and the gRPC FederationSync stream protocol, including validation caps and error-handling outcomes.
- State architecture: Explains the division of responsibilities across ResourceAggregator, CenterWatchCache/Registry, CenterMetaDataStore, and the SQLite-based controller registry.
Quick Start
Ask an AI to explain how edgion-center aggregates PluginMetaData from Controllers through its bidirectional gRPC reverse-watch stream and how the Admin API serves the aggregated results.