This is an automated email from the ASF dual-hosted git repository. wu-sheng pushed a commit to branch feat/service-internal-topology in repository https://gitbox.apache.org/repos/asf/skywalking-horizon-ui.git
commit 879ec78b2b50262955cb417a638ba6cad75b0b53 Author: Wu Sheng <[email protected]> AuthorDate: Tue Jun 9 16:54:56 2026 +0800 fix(mock): lifecycle agent calls the next tier's MAIN container hot's lifecycle agent -> warm's main data container, warm's -> cold's (was sibling -> sibling). Demonstrates a sibling-hex -> main-hex edge. --- apps/bff/src/logic/layers/mock-internal-topology.ts | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/apps/bff/src/logic/layers/mock-internal-topology.ts b/apps/bff/src/logic/layers/mock-internal-topology.ts index 44c4d0a..4143969 100644 --- a/apps/bff/src/logic/layers/mock-internal-topology.ts +++ b/apps/bff/src/logic/layers/mock-internal-topology.ts @@ -31,8 +31,9 @@ * - 3 data PODs — hot / warm / cold tiers — each a pod of 3 containers: * data [main] + lifecycle-agent + fodc-agent (bundled siblings). * - liaison → data calls (main → main). - * - lifecycle-agent calls ACROSS tiers: hot → warm → cold (sibling → sibling, - * so the edge connects the small attached hexes, not the mains). + * - lifecycle-agent calls ACROSS tiers: a tier's lifecycle agent (a sibling + * hex) calls the MAIN data container of the next tier — hot → warm → cold + * (sibling → main, so the edge runs from a small attached hex to a main). * * Attributes carried per instance (the 3 rules key off these): * - `node_role` liaison | data → clusterBy (the dashed boxes) @@ -129,9 +130,10 @@ export function buildMockInternalTopology(serviceId: string, serviceName: string call('liaison-0-liaison', 'data-cold-data', SC), call('liaison-1-liaison', 'data-hot-data', SC), call('liaison-1-liaison', 'data-warm-data', SC), - // lifecycle agent across tiers (sibling → sibling) - call('data-hot-lifecycle', 'data-warm-lifecycle', ['SERVER']), - call('data-warm-lifecycle', 'data-cold-lifecycle', ['SERVER']), + // lifecycle agent across tiers: a tier's lifecycle agent (a SIBLING hex) + // calls the MAIN data container of the next tier — hot → warm → cold. + call('data-hot-lifecycle', 'data-warm-data', ['SERVER']), + call('data-warm-lifecycle', 'data-cold-data', ['SERVER']), ]; // serviceId/serviceName ride through on the response wrapper; nodes keep // their own mock service identity so the graph reads as one cluster.
