Skip to content

Commit 301d884

Browse files
committed
Updates
1 parent 3160cf2 commit 301d884

3 files changed

Lines changed: 6 additions & 6 deletions

File tree

content/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/assess-compatibility.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ If SSH is missing, please use [Install SSH](https://learn.arm.com/install-guides
3838
Now that the host device is prepared, we will setup the target. On the host device, connect to your target with SSH.
3939

4040
```bash
41-
ssh user@your-target
41+
ssh user@my-target
4242
```
4343

4444
Once connected to the target, use the following commands to verify both Docker and `lscpu` are installed:
@@ -66,7 +66,7 @@ If you are using your host device simultaneously as your target, use `topo healt
6666
topo health --target user@my-target
6767
```
6868

69-
The output should appear similar to:
69+
The output should appear similar to the example from a heterogeneous SoC below, but will differ depending on your hardware:
7070

7171
```output
7272
Host

content/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/deploy-workload.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,10 +94,10 @@ The LLM chatbot application will appear as below:
9494

9595
![LLM Chatbot](llm_chatbot.png)
9696

97-
Depending on the permissions you have setup with your target device, you may not be able to use the IP address directly. In this case, you may need to forward to a local port and view at `http://localhost:port_number` instead:
97+
Depending on the permissions you have setup with your target device, you may not be able to use the IP address directly. In this case, you may need to forward to a local port and view at `http://localhost:<port_number>` instead:
9898

9999
```bash
100-
ssh -L 3000:localhost:3000 user@my-target
100+
ssh -L <port_number>:localhost:<port_number> user@my-target
101101
```
102102

103103
To stop a deployed Topo application on the target, run `topo stop` on the host:

content/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/overview-and-setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ layout: learningpathall
88

99
## What is Topo?
1010

11-
[Topo](https://github.com/arm/topo) is an open-source command-line tool, developed by Arm. Topo connects from a host device (e.g., your development laptop) to an Arm-based Linux target (e.g., a Raspberry Pi) over SSH, detects hardware capabilities, and allows the user to deploy compatible containerized workloads with ease. Topo builds container images on the host, transfers them to the target, and starts the services on the target. Building and deploying on target is also possible. Topo also showcases several sample templates defining workloads you can deploy, including a "Hello World" webpage, an LLM Chatbot, and a SIMD Benchmark comparing Scalar, Neon, and the Scalable Vector Extension (SVE).
11+
[Topo](https://github.com/arm/topo) is an open-source command-line tool, developed by Arm. Topo connects from a host device (e.g., your development laptop) to an Arm-based Linux target (e.g., a Raspberry Pi) over SSH, detects hardware capabilities, and allows the user to deploy compatible containerized workloads with ease. Topo builds container images on the host, transfers them to the target, and starts the services on the target. Building and deploying on the target is also possible. Topo also showcases several sample templates defining workloads you can deploy, including a "Hello World" webpage, an LLM Chatbot, and a SIMD Benchmark comparing Scalar, Neon, and the Scalable Vector Extension (SVE).
1212

1313
[Topo templates](https://github.com/arm/topo-template-format) are based on the [Compose Specification](https://github.com/compose-spec/compose-spec), extended with `x-topo` metadata that describes requirements such as CPU features and build arguments. The Compose Specification is a standard, YAML-based format for describing how to run multi-container applications. Instead of manually starting containers one-by-one, you define everything in a single file that includes which services to run, what images to use, how they connect, and what configuration they need.
1414

@@ -21,7 +21,7 @@ The optional heterogeneous deployment with `remoteproc-runtime` requires a heter
2121
Topo streamlines deploying containerized workloads to Arm-based Linux devices.
2222
If you have an heterogeneous device (e.g. Cortex-A + Cortex-M SoC such as the i.MX 93), Topo enables you to use it fully, deploying both firmware and application as containerized workloads through standard container tooling.
2323

24-
Once a template is defined, use of Topo removes the need to deal with low-level setup and compatibility issues manually. Topo first assesses the system to identify processor features such as SVE or Neon on CPU, then advises which templates are appropriate for the device, before automating the end to end deployment, for which Topo deals with all the low-level instructions.
24+
Once a template is defined, use of Topo removes the need to deal with low-level setup and compatibility issues manually. Topo first assesses the system to identify processor features such as SVE or Neon on CPU, then advises which templates are appropriate for the device. Finally, it automates the end to end deployment, dealing with all the low-level instructions.
2525

2626
Topo can also be leveraged by AI Agents to further streamline and automate.
2727

0 commit comments

Comments
 (0)