OpenVox Training › Class 3 of 3

OpenVox Architect

For the person who designs the estate, the migration, and the 3 a.m. restore.

Overview

Architect is half lecture and lab, half scenario studio. Students size and build a split CA and compiler topology, operate OpenVoxDB, design data and classification, plan Puppet 7 → OpenVox 8 and Puppet Enterprise → OpenVox migrations, and write the runbooks. Then groups work realistic customer scenarios and defend their designs in front of the room.

At a glance

Who it is for
Platform owners and principal engineers
Prerequisites
OpenVox Journeyman, or equivalent production experience plus a placement check (roles/profiles/Hiera, an r10k-deployed Puppetfile, lookup --explain, known PE → OpenVox gaps).
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–8 students, in table groups of 2–3 for scenarios. 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,750 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 — Pattern 1, estate math, and OpenVoxDB

Sizing math (check-ins, compile time, JRuby, headroom); the four topologies; hardening a single-server estate; OpenVoxDB, PostgreSQL and PQL; tuning server instances.

Day 2 — Pattern 2: compilers behind a load balancer

Adding a compiler and splitting the CA; load-balancer and certificate design; moving the database off-box (dedicated PostgreSQL or managed cloud); code deploy across many compilers; hot site and multi-site patterns.

Day 3 — Very large estates, CA failover, and multi-site

Compilation clusters; CA backup, restore and failover design; database high availability; CI/CD that prevents surprises, with catalog-diff canaries. Design studios, not full cluster builds.

Day 4 — Delivery engineering and scenario studio

Extending r10k and a CI pipeline skeleton; a migration and data-design briefing (Puppet 7 and Puppet Enterprise to OpenVox, tiers, secrets, classification choices); scenario studio: groups present a target design to a mock platform board, followed by an individual written addendum.

Hands-on labs

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

  1. Sizing worksheet
  2. Single-server hardening
  3. PQL pack
  4. Tuning max-active-instances
  5. Second compiler with ca_server
  6. Moving the database off-box
  7. r10k on multiple compilers
  8. CA backup and restore
  9. CA failover design studio
  10. PostgreSQL HA design
  11. Multi-site design
  12. catalog-diff canary
  13. CI skeleton
  14. Scenario studio and presentations

What students get

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

After the series, the natural next step is applying it to your own estate: a health check or migration sprint. See Services.

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 Architect

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.

Ask about OpenVox Architect Free 15-minute intro call

info@ssconsultinggroup.net · 912-549-0272