Skip to content

Commit 7b7d2de

Browse files
committed
Added services
1 parent 1e44e86 commit 7b7d2de

7 files changed

Lines changed: 123 additions & 2 deletions

File tree

‎_includes/home_services.html‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ <h2 class="section-heading"><a href="{{ site.url }}/services/">Puppet Consulting
1414
<li><b><a href="{{ site.url }}/services/puppet-health-check/">Puppet Health Check</a></b> for infrastructure optimization</li>
1515
<li><b><a href="{{ site.url }}/services/puppet-infrastructure-kickstart/">Puppet Infrastructure Kickstart</a></b> for a production-ready foundation</li>
1616
<li><b><a href="{{ site.url }}/services/ansible-migration/">Ansible / Puppet Migration</a></b> for IaC tool transitions</li>
17-
<li><b>Puppet Enterprise / OpenVox migration</b> in both directions</li>
18-
<li><b><a href="{{ site.url }}/pabawi/">Pabawi support</a></b> for installation, integrations, and development</li>
17+
<li><b><a href="{{ site.url }}/services/openvox-pe-migration/">Puppet Enterprise / OpenVox migration</a></b> in both directions</li>
18+
<li><b><a href="{{ site.url }}/services/pabawi-support/">Pabawi support</a></b> for installation, integrations, development, and sponsorship</li>
1919
</ul>
2020
</div>
2121
</div>

‎_includes/services_openvox.html‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
<article id="openvox" class="service-card">
2+
<p class="eyebrow">Distribution transition</p>
3+
<h3><a href="{{ site.url }}/services/openvox-pe-migration/">OpenVox ↔ Puppet Enterprise Migration</a></h3>
4+
<p>Move between Puppet Enterprise and OpenVox in either direction, with certificate, PuppetDB, and RBAC continuity checked before cutover.</p>
5+
<a class="card-link" href="{{ site.url }}/services/openvox-pe-migration/">Migration approach <span aria-hidden="true">→</span></a>
6+
</article>

‎_includes/services_pabawi.html‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
<article id="pabawi" class="service-card">
2+
<p class="eyebrow">Open source Pabawi</p>
3+
<h3><a href="{{ site.url }}/services/pabawi-support/">Pabawi Support and Sponsorship</a></h3>
4+
<p>Installation, integrations, and custom development for Pabawi, plus sponsorship options for teams that depend on it in production.</p>
5+
<a class="card-link" href="{{ site.url }}/services/pabawi-support/">Support and sponsorship <span aria-hidden="true">→</span></a>
6+
</article>

‎_includes/services_splash.html‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ <h2>Flexible, focused consulting, training, and development for real infrastruct
1717
<a href="{{ site.url }}/services/puppet-health-check/">Health check <span>→</span></a>
1818
<a href="{{ site.url }}/services/puppet-infrastructure-kickstart/">Infrastructure kickstart <span>→</span></a>
1919
<a href="{{ site.url }}/services/ansible-migration/">Ansible / Puppet migrations <span>→</span></a>
20+
<a href="{{ site.url }}/services/openvox-pe-migration/">OpenVox / PE migration <span>→</span></a>
21+
<a href="{{ site.url }}/services/pabawi-support/">Pabawi support <span>→</span></a>
2022
</nav>
2123
</div>
2224
</div>

‎_layouts/services.html‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ <h2 id="service-directory-title" class="section-page-title">Focused help for eac
2020
{% include services_health.html %}
2121
{% include services_kickstart.html %}
2222
{% include services_ansible.html %}
23+
{% include services_openvox.html %}
24+
{% include services_pabawi.html %}
2325
</div>
2426
</div>
2527
</section>

‎_services/openvox-pe-migration.md‎

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
layout: service
3+
title: OpenVox and Puppet Enterprise Migration
4+
short_title: OpenVox ↔ PE Migration
5+
description: "Move between Puppet Enterprise and OpenVox in either direction, with a compatibility assessment, staged rollout, and a working rollback plan."
6+
summary: "A distribution migration, not a package swap: certificates, PuppetDB, RBAC, module compatibility, and support expectations are all part of the plan."
7+
eyebrow: Puppet distribution migration
8+
service_type: OpenVox and Puppet Enterprise migration consulting
9+
delivery: Remote or onsite project
10+
best_for: Distribution transitions and EOL exposure
11+
order: 7
12+
image: /img/background-services.jpg
13+
last_modified_at: 2026-07-10
14+
---
15+
16+
## Choosing, or changing, your Puppet distribution
17+
18+
Since open-source Puppet stopped being maintained past 8.10 and Perforce moved ongoing development into the commercial Puppet Core line, teams running Puppet have a real platform decision to make, not just a version bump. Puppet Enterprise remains the fully supported commercial path, with its console, orchestrator, and RBAC. OpenVox is the community-maintained continuation of the open-source implementation, compatible with the Puppet language but distributed under different package names and repositories.
19+
20+
Both directions show up in practice: organizations moving from Puppet Enterprise to OpenVox to control licensing and stay open-source, and organizations moving from OpenVox (or unmaintained open-source Puppet) to Puppet Enterprise to get commercial support, console tooling, and RBAC. Some estates end up consolidating a mixed OpenVox/PE environment left over from a previous decision.
21+
22+
{% assign migration_guide_post = site.posts | where: "slug", "puppet-7-to-8-migration-guide" | first %}
23+
{% if migration_guide_post %}
24+
If the trigger is a Puppet 7-to-8 upgrade rather than a distribution change, see the [Puppet 7 to 8 migration guide]({{ site.url }}{{ migration_guide_post.url }}) first — distribution choice and version upgrade are related but separate decisions.
25+
{% endif %}
26+
27+
## What actually changes
28+
29+
- **Packages and repositories.** OpenVox and Puppet Enterprise ship under different package names, repository URLs, and installer paths. Existing install scripts, CI images, and provisioning code that hardcode Puppet Inc. or Perforce repositories need updating.
30+
- **Certificate Authority and agent trust.** The CA can often be preserved across the migration, but this must be verified and tested, not assumed. A CA rebuild is a separate, riskier decision from the distribution change itself.
31+
- **PuppetDB and reporting.** Compatibility between the PuppetDB version, the terminus, and the target Puppet Server/OpenVox Server build needs checking before cutover, not after.
32+
- **Console, RBAC, and orchestrator.** Moving to OpenVox means losing the PE console, node classifier UI, and RBAC — that functionality has to be replaced with Hiera-driven classification, an external tool, or accepted as a deliberate trade-off. Moving to Puppet Enterprise means gaining them, with a migration of existing classification logic into the classifier.
33+
- **Module and Puppetfile compatibility.** Most Puppet-language modules work unchanged, but anything depending on PE-specific facts, functions, or the orchestrator API needs review.
34+
- **Support model.** Puppet Enterprise carries a commercial support agreement with Perforce. OpenVox support comes from the community and, where needed, from a consulting relationship like this one.
35+
36+
## Delivery phases
37+
38+
1. **Assessment:** current distribution and version, module inventory, CA and certificate state, PuppetDB and reporting setup, console/RBAC usage if migrating away from PE, and any code that assumes a specific distribution.
39+
2. **Target design:** package sources, CA continuity plan, replacement (or introduction) of classification and RBAC, and a rollback path that doesn't depend on the migration succeeding.
40+
3. **Pilot:** migrate a small, representative set of infrastructure and agent nodes; verify catalog compilation, certificate handling, and reporting end to end.
41+
4. **Staged rollout:** move infrastructure components first, then agent cohorts, with explicit checks between each stage.
42+
5. **Verification and handover:** confirm reports, PuppetDB queries, and (if applicable) console/RBAC behavior match expectations, and document the new operating model for the team.
43+
44+
## What reduces migration risk
45+
46+
- Decide the distribution first, separately from any version upgrade that might be riding along with it.
47+
- Test CA and certificate continuity in a non-production copy before touching real agents.
48+
- Don't discover console or RBAC dependencies during the cutover — inventory them up front.
49+
- Keep a tested path back to the previous distribution until the new one has run through a full reporting and compliance cycle.
50+
51+
<div class="service-inline-cta">
52+
<h2>Considering a move between Puppet Enterprise and OpenVox?</h2>
53+
<p>Share your current distribution, version, estate size, and what's driving the change.</p>
54+
<a class="btn btn-primary" href="{{ site.url }}/#contact">Assess the migration</a>
55+
</div>

‎_services/pabawi-support.md‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
layout: service
3+
title: Pabawi Support and Sponsorship
4+
short_title: Pabawi Support
5+
description: "Installation, integration, and custom development for Pabawi, plus sponsorship options for teams that depend on it and want to fund its roadmap."
6+
summary: "Direct access to Pabawi's author for setup, Puppet/OpenVox/Ansible integrations, and custom extensions — or an ongoing sponsorship for teams already running it."
7+
eyebrow: Open source Pabawi
8+
service_type: Pabawi installation, integration, and sponsorship
9+
delivery: Remote, or ongoing sponsorship
10+
best_for: Teams adopting or depending on Pabawi
11+
order: 8
12+
image: /img/pabawi-screenshots.png
13+
last_modified_at: 2026-07-10
14+
---
15+
16+
## Two ways to work with Pabawi
17+
18+
[Pabawi]({{ site.url }}/pabawi/) is a self-hosted, open source web interface for Puppet, OpenVox, Bolt, Ansible, SSH, PuppetDB, Hiera, Proxmox, AWS, and Azure. It's free to run and Apache 2.0 licensed. This service covers the two things that fall outside "download it and read the docs": getting it working in your specific environment, and keeping it maintained if your infrastructure depends on it.
19+
20+
### Support: getting Pabawi running in your environment
21+
22+
- **Installation and first integration.** Setting up Pabawi against your actual PuppetDB, Puppet Server or OpenVox Server, Bolt inventory, Ansible inventory, or SSH estate — not the demo dataset.
23+
- **Multi-source inventory design.** Deciding how nodes from PuppetDB, Ansible, SSH, and cloud/hypervisor sources should merge, group, and deduplicate for your topology.
24+
- **RBAC and command whitelisting.** Setting up per-operation permissions, JWT sessions, and command whitelists so delegated access matches your actual security requirements.
25+
- **Provisioning integrations.** Connecting Proxmox, AWS EC2, or Azure provisioning to the configuration-management side so new nodes land in inventory already managed.
26+
- **Custom extensions and models.** Pabawi's model and extension system is built to be extended; if you need an integration that doesn't exist yet, it can usually be built rather than worked around.
27+
- **Upgrade assistance.** Moving between Pabawi versions without losing custom configuration, extensions, or RBAC setup.
28+
29+
### Sponsorship: for teams that already depend on Pabawi
30+
31+
If Pabawi is already running in your production environment, a sponsorship is a way to fund its continued development instead of treating it as a free dependency with no relationship attached. Sponsorship can take a few shapes:
32+
33+
- **Ongoing sponsorship.** A recurring arrangement that funds maintenance and gives you a direct line for questions and priority attention on issues that affect you.
34+
- **Roadmap sponsorship.** Funding a specific integration or feature — a provisioning target, a monitoring integration, an authentication method — and having it prioritized on the public roadmap.
35+
- **One-time development sponsorship.** A single funded milestone, for example hardening a specific integration for production use ahead of the general release.
36+
37+
None of this changes the license or creates a private fork: sponsored work lands in the open source project, same as everything else.
38+
39+
## What to send
40+
41+
For support requests: what you're running (Puppet or OpenVox, PuppetDB version, Bolt/Ansible if relevant), what you're trying to connect, and what "done" looks like for you.
42+
43+
For sponsorship: roughly how you're using Pabawi today, the scale of your infrastructure, and whether you have a specific roadmap item in mind or want general ongoing support.
44+
45+
<div class="service-inline-cta">
46+
<h2>Need Pabawi set up, extended, or sponsored?</h2>
47+
<p>Share what you're running and what you need — a quick setup call, a custom integration, or an ongoing sponsorship.</p>
48+
<a class="btn btn-primary" href="{{ site.url }}/#contact">Discuss Pabawi</a>
49+
<a class="btn btn-default" href="https://github.com/example42/pabawi">View the source</a>
50+
</div>

0 commit comments

Comments
 (0)