Unit 4: NVUE, REST API, and Ansible Automation

Per-unit concept, checklist, and command drill page

Unit 4 of 14

Objective

Operate Cumulus configuration and automation through NVUE with repeatable staged-change workflows.

Concept Notes

NVUE is a transactional model, not just a command wrapper. Staging and diffing are the controls that reduce change risk in high-scale fabrics where one bad update can affect many racks.

A key exam theme is consistency between manual and automated workflows. You should be able to reason from NVUE CLI intent to REST object state to Ansible execution without losing operational parity.

Coverage Checklist

NVUE command families: show, set/unset, action, config.
Staged workflow: set -> diff -> apply -> save/detach.
Configuration history and targeted filtering.
REST API model and transport semantics.
Automation approach with NVIDIA NVUE Ansible collection.
Operational parity between CLI and API paths.

Practice Outcomes

Use staged config review before any apply operation.
Pull and validate object state via REST before automation rollout.
Adopt idempotent Ansible playbooks for batch operations.

Command Drills

nv config diff

Inspect pending deltas before commit.

nv config apply

Commit staged changes into running state.

nv config detach

Drop staged changes safely before apply.

curl -u 'username:PASSWORD' -k -X GET https://<switch-ip>:8765/nvue_v1/interface/<id>/link/stats

Validate API-driven observability and automation compatibility.

Navigation

Back to Cumulus index Previous: Unit 3 Next: Unit 5