Rework slide 29: Puppet enterprise/SaaS positioning
Some checks failed
Deploy presentation / deploy (push) Has been cancelled
Some checks failed
Deploy presentation / deploy (push) Has been cancelled
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
11
index.html
11
index.html
@@ -319,12 +319,11 @@ class webserver {
|
||||
|
||||
<!-- ─── SLIDE 29 : Puppet platforms ─────────────────────────────── -->
|
||||
<section>
|
||||
<h2>Puppet Enterprise, CD4PE, Foreman.</h2>
|
||||
<p>
|
||||
<strong>Puppet Enterprise</strong> — RBAC, reporting, and node management at scale<br>
|
||||
<strong>CD4PE</strong> — CI/CD pipelines for Puppet code (Continuous Delivery for PE)<br>
|
||||
<strong>Foreman</strong> — open-source lifecycle management, integrates with Puppet<br>
|
||||
</p>
|
||||
<h2>Puppet is for large fleets that can't afford drift.</h2>
|
||||
<p>Continuous compliance, auditability, and guaranteed state — at scale.<br>
|
||||
Best suited for enterprises with hundreds or thousands of long-lived servers.<br>
|
||||
<em>Fewer friendly SaaS options than Terraform or Ansible.<br>
|
||||
Puppet Enterprise and Foreman are self-hosted. No managed cloud offering.</em></p>
|
||||
</section>
|
||||
|
||||
<!-- ─── SLIDE 30 : Puppet community ─────────────────────────────── -->
|
||||
|
||||
Reference in New Issue
Block a user