Skip to content

Commit 94de6b5

Browse files
committed
docs: Fix path in arch image
Signed-off-by: Anastassios Nanos <ananos@nubificus.co.uk>
1 parent e82f593 commit 94de6b5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/design/architecture.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ iterative development process characterized by continuous testing and feedback l
2020
mechanisms developed are not only effective in their current context but are also scalable and adaptable to future
2121
technological advancements and operational needs.
2222

23-
<img src="../assets/img/arch.png" width="600"/>
23+
<img src="../../assets/img/arch.png" width="600"/>
2424

2525
The following figure depicts a comprehensive illustration of the MLSysOps hierarchical agent system's placement
2626
and its interactions with two other fundamental subsystems: container orchestration and telemetry. This agent hierarchy
@@ -30,7 +30,7 @@ designated interfaces at each tier. Moreover, the agent system engages with the
3030
integrates plug-in configuration policies that can use ML models at all levels. At every level, agents utilize mechanism
3131
plugins to implement commands for adjusting available configuration and execution mode options.
3232

33-
<img src="../assets/img/high_level_arch.png" width="600"/>
33+
<img src="../../assets/img/high_level_arch.png" width="600"/>
3434

3535
Node-level agents’ interface with local telemetry systems and expose configuration knobs. Cluster-level agents
3636
coordinate resource allocation decisions across groups of nodes. At the top level, the continuum agent handles global

0 commit comments

Comments
 (0)