OpenVox Training › Class 2 of 3

OpenVox Journeyman

For the people who will write and own the estate: modules, tests, Hiera 5 data, roles and profiles, the control repo, r10k, OnceOver and Beaker.

Overview

Journeyman takes students from writing a class to shipping code a team can maintain: a tested, Forge-shaped module, Hiera 5 data, a role built from profiles, an r10k-deployed control repo, and OpenBolt for the work that has to happen right now. It finishes with a heritage-code cleanup clinic. Lab time is 40–50% of the clock.

At a glance

Who it is for
The people who will own modules, data and the control repo
Prerequisites
OpenVox User, or pass a short placement check: you can already sign an agent and write a class.
Length
Four days (Monday–Thursday), about 26–27 contact hours (about 6.5–7 hours a day, roughly half of it hands-on lab)
Format
On-site: regional public class (open enrollment) or a private class at your location. Live remote also available.
Class size
5–10 students. Sizes get smaller at each level because there is more hands-on and scenario work.
Assessment
Hands-on practical; pass at 80%

Price: regional public class $2,500 per student, minimum 5 students to run a class. Private corporate class for a single company: $16,500 per class week, minimum 5 students, and the customer covers instructor travel. Class dates: ask us.

Who should attend

What you will be able to do

Course outline

Day 1 — Development tooling as a day job

The OpenVox DevKit and bundle exec; scaffolding modules with Jig; lint, syntax and metadata checks; rspec-puppet unit tests; a custom fact.

Day 2 — Control repo and r10k

The control repository; Puppetfile and r10k deploys; feature-branch environments; pinning modules; environments (code) vs tiers (data); OnceOver compile tests for the control repo.

Day 3 — Data, roles, a console, and OpenBolt

Hiera 5 and lookup(); merge strategies; roles and profiles; openvox-gui (with Foreman compared); OpenBolt fundamentals: commands, tasks and plans, inventory with targets and groups, SSH and WinRM transports.

Day 4 — OpenBolt at work, then prove it

OpenBolt tasks and plans in a module, apply blocks, r10k and CI; OpenBolt plugins and writing a small one; connecting OpenBolt to OpenVoxDB to target nodes by fact; Beaker and fleet tooling overview; heritage-cleanup review; practical exam (90 minutes, Git repo) plus oral.

Hands-on labs

Every concept is followed by time at the keyboard on a real lab estate.

  1. Ruby and voxpupuli-test on a clone
  2. Scaffold a new module with Jig
  3. Lint and lint fix
  4. Write the spec you wish existed
  5. Custom fact and spec
  6. Control repo from the official template
  7. r10k install and first deploy
  8. Feature branch isolation
  9. OnceOver smoke test
  10. Puppetfile pinning
  11. hiera.yaml and --explain
  12. Merge: unique vs a broken deep merge
  13. A role and two profiles
  14. openvox-gui
  15. OpenBolt project, inventory and first runs
  16. An OpenBolt task and plan, with an apply block
  17. Write a small OpenBolt inventory plugin
  18. Target nodes by fact from OpenVoxDB
  19. Heritage cleanup pull request (pairs, as homework)
  20. Beaker idempotency and VoxBox lint (optional)
  21. Practical exam (90 minutes, submitted as a Git repo)

What students get

Every student who completes the class receives a certificate of completion. A formal certification program is planned.

Next: OpenVox Architect, where you move from shipping a module to defending an estate.

OpenVox is built and maintained by the OpenVox community under Vox Pupuli. Product facts in this class follow the official OpenVox documentation. S & S Consulting Group designs and teaches the course.

Ask about OpenVox Journeyman

Tell us how many people, where they are today, and what you need them to own afterwards. We will tell you which class fits and what it takes to run it for your team.

info@ssconsultinggroup.net · 912-549-0272