diff --git a/index.html b/index.html index 14ddd3c..fa78f8e 100644 --- a/index.html +++ b/index.html @@ -397,19 +397,112 @@

Configuration drift is silent… until it isn't.

Prod breaks on a Tuesday. You can't reproduce the bug locally. You can't scale reliably. You can't onboard a new server without fear.

+ + + + T0 + T1 + T2 + + + + + + + + + ALL IDENTICAL + + + + + + DRIFTING… + + + + + + + ! + + ! + + ! + CHAOS +

What if your infrastructure was just… code?

Yes, even your AI assistant can write it. But you still need to understand what it deploys.

+ + + + + + + + { } + + + + + + + deploy + + + + + + + + +

Configuration as Code

Managing infrastructure through machine-readable files, stored in version control.

-

Reproducible  ·  Versionable  ·  Auditable

+ + + + + + + + + Reproducible + Same input → same result + + + + + + + + + + + + Versionable + Track every change + + + + + + + + + + + Auditable + Who changed what & when +
@@ -429,6 +522,43 @@

HCL: HashiCorp Configuration Language.

Declarative, human-readable — and pure JSON works too.
terraform plan previews  ·  terraform apply creates  ·  terraform destroy removes.

+ + + + + + + + + + + + + + + HCL Code + + + + + + + + plan + + + + + + apply + + + + + + Resources + WRITE → PLAN → APPLY + @@ -437,6 +567,66 @@

The .tfstate file maps code to real-world resources. Store it remotely.
Depending on what you manage, it can contain plaintext sensitive values — credentials, tokens, secrets.
Handle it with care. Don't feed it to your LLM.

+ + + + + + + + + + main.tf + + + + network.tf + + + + dns.tf + + Configuration + + + + + + + + + + + + + .tfstate + state mapping + + + + + + + Source of Truth + + + + + + + + VM + + + + VNet + + + + DNS Zone + + Real Resources + @@ -505,9 +695,41 @@ resource "ovh_domain_zone_record" "web" {

YAML playbooks run tasks in order, across any number of hosts.
No daemon. No certificate authority. Just Python + SSH.
Idempotent modules ensure the same playbook can run safely again and again.

- It just works + + + + + + + + + + >_ + + Control Node + + + PUSH + + + + + + + + + SSH + + + + + + + + + Managed Hosts + no agent required + @@ -575,6 +797,40 @@ resource "ovh_domain_zone_record" "web" {

Pull, not push. Agents, not SSH.

Every 30 minutes, each puppet-agent polls the Puppet Server, compiles a catalog, and enforces it.
Drift is corrected automatically — without anyone lifting a finger.

+ + + + + + + + + + + + catalog + Puppet Server + + + + + every 30 min + + + + + + + + pull + + agent + agent + agent + agent + agent + Managed Nodes + @@ -606,9 +862,37 @@ class webserver {

Puppet noticed. Puppet fixed it.
Continuous compliance — not just at deploy time. Every. 30. Minutes.
No more gardening your servers by hand.

- Automated maintenance + + + + + + + + + + ! + Drift + detected + 1 + + + + + Agent + applies catalog + 2 + + + + Compliant + 3 + + + + + continuous enforcement loop + @@ -632,9 +916,37 @@ class webserver {

They're not competing. They're complementary.

Each one solves a different layer of the same problem.

- Assembling + + + + + + + + + Terraform + — Provision + VMs, networks, cloud resources + Day 0 + + + + + Ansible + — Configure + packages, services, app deployment + Day 1 + + + + + + + Puppet + — Enforce + continuous compliance, drift correction + Day 2+ +