OpenVox User Training — Class 1 of 3

Overview

OpenVox is not a scripting language. It is a promise about a machine. This class teaches desired state from the ground up: resources, facts, classes, ordering, templates, and the conversation between an agent and an OpenVox server. Lab time is 40–50% of the clock.

At a glance

Who it is for

Sysadmins and operators who will consume OpenVox and write small, local fixes

Prerequisites

Linux command-line comfort: edit a file, use systemctl, journalctl and sudo. No programming degree required.

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–12 students; pairing on labs is allowed. 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

Sysadmins and operators who will consume OpenVox and write small, local fixes
Junior SREs
Puppet Enterprise users who only ever ran puppet agent -t

What you will be able to do

Explain declarative desired state versus a shell script, and why idempotence matters
Install openvox-agent from the Vox Pupuli repos and verify it two ways
Write manifests with package, file, service, user and notify
Use OpenFact structured facts ($facts[...]) instead of legacy facts
Apply locally with puppet apply, inspect with puppet resource, preview with --noop
Join an agent to an OpenVox server: CSR, sign, puppet agent -t
Read a run report and its exit codes
Fix the boring failures: paths, permissions, duplicate resources, time skew, wrong server=
Know what not to touch yet (Hiera rewrites, the CA, autosign, editing code on the server)

Course outline

Day 1 — Describe the machine, don’t script it

Why desired state beats a bootstrap script; what OpenVox is; resources and the RAL; your first manifest; users, groups, packages and services; a little Git; editor and Jig setup; facts with OpenFact; previewing with --noop and reading exit codes.

Day 2 — Names, groups, and order

Variables and data types; classes and module layout; relationships and ordering (why the service did not restart); exec as a guarded last resort; EPP templates.

Day 3 — Two machines, one conversation

Why a server and an agent; building two lab VMs; installing the OpenVox server; installing the agent and joining it (CSR, sign, puppet agent -t).

Day 4 — Read the result, fix the boring failures

Node definitions and run reports; a break/fix rotation through common failures; module paths; practical exam (60 minutes, open notes).

Hands-on labs

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

Editor and Jig setup
Replace a bootstrap script with resources
Validate and lint
puppet resource, users, and duplicates
Facts
--noop and exit codes
A typed class
Module layout
Restart on file change
One guarded exec
EPP template
Two virtual machines
Server install
Agent join
One node definition and a report
Four broken stations (break/fix)
Jig paths
Practical exam (60 minutes, open notes)

What students get

User Lecture Manual and Lab Manual
Your own lab work (the manifests you write)
Structured-facts pocket card
Reading list of official OpenVox docs and VoxDocs
Certificate of completion for OpenVox User

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

Next: OpenVox Journeyman for the people who will write the 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.

OpenVox User