doca-bare-metal-deployment

Name: doca-bare-metal-deployment
Author: NVIDIA

2.6kstars297forks

How to install doca-bare-metal-deployment?

nvidia/skills/doca-bare-metal-deployment

$npx -y skills add NVIDIA/skills --skill doca-bare-metal-deployment

Installs into the current project.

Summary

Use this skill for launching, supervising, debugging, OR platform lifecycle on a BlueField — BFB install, RShim/TMFIFO, host PF rebind, post-BFB recovery — taking a DOCA-linked binary to a healthy run directly on hardware (host x86 + BlueField NIC over PCIe, or BlueField Arm bare

Files · 1

View on GitHub

SKILL.md

1	# DOCA bare-metal deployment
2
3	Where to start: This skill is the bundle's home for operating
4	a DOCA-linked application binary directly on hardware — no
5	container, no kubelet, no static-pod manifest. It is the parallel
6	of [`doca-container-deployment`](../doca-container-deployment/SKILL.md)
7	for the non-container path. If the user has a DOCA-linked binary
8	they built (per the canonical workflow in
9	[`doca-programming-guide`](../doca-programming-guide/SKILL.md))
10	and they want to know *how to actually run it on the host or on
11	the BlueField Arm cores correctly*, open
12	[`TASKS.md`](TASKS.md) and start at
13	[`## configure`](TASKS.md#configure). If the question is *what
14	shape does the bare-metal runtime even have and what is the
15	deployment contract*, start at [`CAPABILITIES.md`](CAPABILITIES.md).
16	If the user is not yet sure whether their target system shape is
17	the container path or the bare-metal path, route the recognition
18	step to [`doca-setup`](../doca-setup/SKILL.md) first; only return
19	here once bare-metal is the confirmed shape.
20
21	## Audience
22
23	This skill serves **external DOCA developers and operators who
24	have a DOCA-linked application binary they built and want to run
25	it directly on hardware** — i.e., people who already have:
26
27	- a DOCA-linked application binary they built per
28	[`doca-programming-guide ## build`](../doca-programming-guide/TASKS.md#build),
29	- a real BlueField NIC and a host that talks to it (the **host
30	x86** path — DOCA host install on the host talks to the
31	BlueField NIC over PCIe), OR a BlueField with a console or SSH
32	to the Arm side (the BlueField Arm bare-metal path — DOCA
33	installed on the DPU Arm cores; the binary runs there
34	directly), and
35	- a desire to RUN that binary directly on the hardware, not
36	inside a kubelet-standalone-managed container.
37
38	It is not for:
39
40	- kernel-driver developers contributing to `mlx5_*` or the
41	BlueField OS,
42	- DOCA library contributors (those changes go to the internal
43	DOCA tree, not to a bare-metal deployment),
44	- full-Kubernetes-cluster operators managing a fleet of
45	BlueFields (the bundle covers
46	[`doca-container-deployment`](../doca-container-deployment/SKILL.md)
47	for the single-host kubelet-standalone shape; **fleet/production-scale
48	deployment is fleet-orchestration scope** — route to the orchestration
49	entry-point in
50	[`doca-public-knowledge-map ## Deploying DOCA services at scale`](../doca-public-knowledge-map/references/map.md#deploying-doca-services-at-scale--orchestration-entry-point-personascale-routing)
51	(DPF / Network Operator / Launch Kit), not hand-rolled static-pod loops),
52	- fresh-laptop-no-hardware users with no DOCA install yet — those
53	belong on
54	[`doca-setup ## no-install`](../doca-setup/TASKS.md#no-install).
55
56	The skill teaches the agent the bare-metal-deployment procedure
57	and the rules for quoting documented commands from the public DOCA
58	Programming Guide and the public BlueField / DPU User Manual via
59	[`doca-public-knowledge-map`](../doca-public-knowledge-map/SKILL.md);
60	it does not invent flag names, PCI BDFs, NUMA numbers, devlink
61	paths, representor strings, or systemd `Restart=` mode names from
62	memory.
63
64	## When to load this skill
65
66	Load this skill when the user is doing **hands-on bare-metal
67	deployment of a DOCA-linked application binary** on either of the
68	two supported host modes (host x86 or BlueField Arm), or asking a
69	cross-cutting bare-metal question that is not specific to one
70	library's API. Concretely:
71
72	- Launching a DOCA-linked binary for the first time on a host
73	with a BlueField NIC in a PCIe slot, with DOCA i

People who liked this also viewed

6 picks

Type

doca-bare-metal-deployment

2.6kstars297forks

View on GitHub

How to install doca-bare-metal-deployment?

nvidia/skills/doca-bare-metal-deployment

$npx -y skills add NVIDIA/skills --skill doca-bare-metal-deployment

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# DOCA bare-metal deployment
2
3	Where to start: This skill is the bundle's home for operating
4	a DOCA-linked application binary directly on hardware — no
5	container, no kubelet, no static-pod manifest. It is the parallel
6	of [`doca-container-deployment`](../doca-container-deployment/SKILL.md)
7	for the non-container path. If the user has a DOCA-linked binary
8	they built (per the canonical workflow in
9	[`doca-programming-guide`](../doca-programming-guide/SKILL.md))
10	and they want to know *how to actually run it on the host or on
11	the BlueField Arm cores correctly*, open
12	[`TASKS.md`](TASKS.md) and start at
13	[`## configure`](TASKS.md#configure). If the question is *what
14	shape does the bare-metal runtime even have and what is the
15	deployment contract*, start at [`CAPABILITIES.md`](CAPABILITIES.md).
16	If the user is not yet sure whether their target system shape is
17	the container path or the bare-metal path, route the recognition
18	step to [`doca-setup`](../doca-setup/SKILL.md) first; only return
19	here once bare-metal is the confirmed shape.
20
21	## Audience
22
23	This skill serves **external DOCA developers and operators who
24	have a DOCA-linked application binary they built and want to run
25	it directly on hardware** — i.e., people who already have:
26
27	- a DOCA-linked application binary they built per
28	[`doca-programming-guide ## build`](../doca-programming-guide/TASKS.md#build),
29	- a real BlueField NIC and a host that talks to it (the **host
30	x86** path — DOCA host install on the host talks to the
31	BlueField NIC over PCIe), OR a BlueField with a console or SSH
32	to the Arm side (the BlueField Arm bare-metal path — DOCA
33	installed on the DPU Arm cores; the binary runs there
34	directly), and
35	- a desire to RUN that binary directly on the hardware, not
36	inside a kubelet-standalone-managed container.
37
38	It is not for:
39
40	- kernel-driver developers contributing to `mlx5_*` or the
41	BlueField OS,
42	- DOCA library contributors (those changes go to the internal
43	DOCA tree, not to a bare-metal deployment),
44	- full-Kubernetes-cluster operators managing a fleet of
45	BlueFields (the bundle covers
46	[`doca-container-deployment`](../doca-container-deployment/SKILL.md)
47	for the single-host kubelet-standalone shape; **fleet/production-scale
48	deployment is fleet-orchestration scope** — route to the orchestration
49	entry-point in
50	[`doca-public-knowledge-map ## Deploying DOCA services at scale`](../doca-public-knowledge-map/references/map.md#deploying-doca-services-at-scale--orchestration-entry-point-personascale-routing)
51	(DPF / Network Operator / Launch Kit), not hand-rolled static-pod loops),
52	- fresh-laptop-no-hardware users with no DOCA install yet — those
53	belong on
54	[`doca-setup ## no-install`](../doca-setup/TASKS.md#no-install).
55
56	The skill teaches the agent the bare-metal-deployment procedure
57	and the rules for quoting documented commands from the public DOCA
58	Programming Guide and the public BlueField / DPU User Manual via
59	[`doca-public-knowledge-map`](../doca-public-knowledge-map/SKILL.md);
60	it does not invent flag names, PCI BDFs, NUMA numbers, devlink
61	paths, representor strings, or systemd `Restart=` mode names from
62	memory.
63
64	## When to load this skill
65
66	Load this skill when the user is doing **hands-on bare-metal
67	deployment of a DOCA-linked application binary** on either of the
68	two supported host modes (host x86 or BlueField Arm), or asking a
69	cross-cutting bare-metal question that is not specific to one
70	library's API. Concretely:
71
72	- Launching a DOCA-linked binary for the first time on a host
73	with a BlueField NIC in a PCIe slot, with DOCA i

People who liked this also viewed

6 picks

Type