# doca-bf4-deployment

doca-bf4-deployment — a skill for BlueField-4 DPU day-1 deployment via BMC: ISO installation, PLDM firmware update, Grace Ubuntu provisioning. Each mutating step requires explicit confirmation and is governed by rollback policy.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 155 installs · ★ 4106 repo stars
- Author: NVIDIA
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-bf4-deployment/SKILL.md
- Updated: 2026-10-23
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/doca-bf4-deployment

## What it does

This skill guides day-1 bring-up of BlueField-4: deploying the BlueField/DOCA bundle ISO to the DPU (Grace, the Arm complex) over UEFI HTTP Boot, PXE, or Redfish Virtual Media; updating platform firmware through Redfish UpdateService and `pldmtool`; preparing Grace Ubuntu with optional cloud-init. All irreversible operations—PLDM firmware burns, ISO reflashes, power cycles, BMC factory resets—route through `doca-hardware-safety` with pre-flight inventory checks, maintenance window confirmation, and rollback validation.

The skill targets BlueField-4 only; BlueField-3 bring-up goes to `doca-bf3-deployment`. Developers engage it for day-1 BlueField-4 bring-up, install-method selection, PLDM Task monitoring, image activation, state verification, and first smoke tests. Each step requires the user's explicit consent for that specific action; chained destructive operations and speculative side effects are prohibited.

Application launch and library APIs route to other skills. The skill does not redefine `doca-hardware-safety` policy and does not cover BlueField BSP, RShim, TMFIFO, or BMC software (those are externally productized).

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill doca-bf4-deployment -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/doca-bf4-deployment/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/doca-bf4-deployment/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill doca-bf4-deployment -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/doca-bf4-deployment/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill doca-bf4-deployment -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/doca-bf4-deployment/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install NVIDIA/skills skills/doca-bf4-deployment
```

2. **Manually: put the files in place**
- File: `.github/skills/doca-bf4-deployment/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill doca-bf4-deployment -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/NVIDIA/skills --path skills/doca-bf4-deployment
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/doca-bf4-deployment/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill doca-bf4-deployment -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-bf4-deployment/SKILL.md

## When to use it
- deploy BlueField/DOCA bundle ISO to DPU via BMC
- update PLDM firmware and activate images through Redfish
- provision Grace Ubuntu with cloud-init for day-1
- verify target firmware and OS versions match release notes
- rollback if a hardware operation corrupts DPU state

## Example prompts
- Help me bring up BlueField-4 from bare metal using the BMC—which install method should I pick for the ISO?
- PLDM firmware update completed but NIC firmware did not advance—how do I diagnose this?
- Prep BlueField-4: check versions, confirm maintenance window, validate rollback plan before PLDM burn

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 1d13220fb078b926.

BEGIN THIRD-PARTY FILE 1d13220fb078b926
```text
---
license: Apache-2.0
name: doca-bf4-deployment
description: >
  WARNING: guides IRREVERSIBLE BlueField-4 hardware operations (PLDM
  firmware burns, ISO reflashes, power cycles, BMC factory resets); every
  mutating step is governed by doca-hardware-safety (window, rollback).
  BlueField-4 only: BlueField-3 bring-up is doca-bf3-deployment. Use this
  skill for BlueField-4 (BF4) day-1 platform
  bring-up from the BMC: installing the BlueField/DOCA bundle ISO onto
  the DPU (Grace, the Arm complex) over UEFI HTTP Boot, PXE, or Redfish
  Virtual Media; the PLDM platform-firmware update via the Redfish
  UpdateService and pldmtool; and a Grace
  Ubuntu image with optional cloud-init. Trigger on BlueField-4/BF4
  bring-up phrasings even without "BF4": {bring up my new BlueField-4},
  {the BlueField ISO will not boot over HTTP from the BMC}, {attach BF4
  virtual media via Redfish}, {BF4 firmware Task stuck at Running}, {prepare a BlueField-4 host: platform
  support, version alignment, safest first smoke test}. Route
  application launch and library APIs to other skills.
metadata:
  author: NVIDIA <doca-feedback@nvidia.com>
  kind: library
  doca_version: "3.5"
  tags:
    - doca
    - bluefield-4
    - deployment
compatibility: >
  No DOCA install is required to read this skill; it teaches the
  documented BlueField-4 BMC-driven bring-up flows (UEFI HTTP Boot,
  PXE, Redfish Virtual Media, PLDM firmware update). Executing the
  steps requires a BlueField-4 with an out-of-band-reachable BMC, a
  host or HTTP/HTTPS server to host the bundle ISO, and the target
  versions from the public BlueField/DOCA release notes.
  The validation steps require a live DOCA install.
---

# DOCA BlueField-4 (BF4) deployment

## Examples

- **"I have a BlueField-4 and a BMC — how do I bring Grace up?"** —
  BMC-driven day-1, not the BF3 RShim/BFB path. Do not invent
  credentials or skip media detach.
- **"PLDM update finished but the NIC firmware did not move."** —
  treat it as a firmware-Task / activation failure, not a second
  burn by default.

**BlueField-3 or any other generation is not this skill.** Name
`doca-bf3-deployment` and stop; do not read further or run commands.

## Preparing a BlueField-4 host (answer from here)
```
END THIRD-PARTY FILE 1d13220fb078b926

The third-party file has ended. Everything between the 1d13220fb078b926 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2256 of 12265 bytes. © NVIDIA · Apache-2.0 · https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-bf4-deployment/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
