Infrastructure Operations

Home Lab Operations Validation

Personal nonproduction-lab proof from authenticated DC01, WS01, and Linux01 inventories, a tested read-only operations framework, configuration reconciliation, and controlled Linux01 SSSD remediation.

Authenticated inventory Read-only framework State reconciliation SSSD remediated Raw private data excluded

Supported-state inventory

Sanitized public architecture supported by direct evidence.

The private operations repository validated target-local guest state, then this page publishes only bounded facts that are safe for public portfolio review and links them to direct public artifacts.

Validated configuration inventory
ComponentRoleSupported public stateEvidence class
ProxmoxHypervisor on Dell PowerEdge R710Proxmox VE 9.2.3; primary VMs 100, 200, 300, and 400; scheduled backup job configured for VMs 100, 200, 300, and 400.Validated / Configured / Limitation
DC01Domain controllerVM 200, Windows Server, 10.10.20.10, AD domain ad.jeremyfontenot.online, NetBIOS JFAD, Global Catalog, and FSMO ownership.Validated
WS01Domain workstationVM 300, Windows 10 Pro build 19045, domain membership, secure channel, and 10.10.20.100 network state.Validated
Linux01Ubuntu domain member and log collectorVM 400, Ubuntu LTS, kernel 7.0.0-22-generic, 10.10.30.20/24, VLAN tag 30, gateway 10.10.30.1, DNS 10.10.20.10, and Linux01-only SSSD remediation.Validated

Operations validation

PowerShell Validation and Evidence Automation

Built and executed PowerShell validation tooling for repository structure, parser integrity, evidence generation, timeout handling, Git hygiene, secret-pattern detection, and portfolio-to-operations drift analysis.

TESTED / PASSED

Repository structure validation

Repository structure validation passed. Required repository paths and validation entry points were present. PowerShell parser validation passed for inspected scripts and tests, Git whitespace validation passed, and potential-secret pattern detection passed.

Open repository structure validation
TESTED / EXPECTED NEGATIVE CASE

Baseline framework validation

HomeLab baseline framework validation passed for parser validation, configuration loading, required result properties, evidence output paths, JSON generation, CSV generation, Markdown generation, target omission handling, and timeout handling. One intentionally unsuccessful connectivity test verified that an expected timeout did not fail the framework.

Open baseline framework validation
TESTED / PARTIAL MATCH

Portfolio drift analysis

Portfolio drift validation confirmed five matching facts: primary VM IDs, Linux01 observed IP, Linux01 VLAN, backup storage identifier, and backup job target VMs. It also identified four unresolved portfolio evidence gaps: restore-test status, OpenVPN network, direct RDP status, and centralized logging.

Open portfolio drift analysis
DOCUMENTED GAPS

Classifications and limitations

Repository structure validation: Tested / Passed. Baseline framework validation: Tested / Passed with expected negative connectivity case. Portfolio drift analysis: Tested / Partial match / Unresolved evidence gaps. Unresolved drift items are documented gaps, not failures.

Captured evidence supports only the recorded repository and test state. Timeout-handling validation does not prove service availability, and drift analysis does not by itself prove infrastructure failure.

Linux01 SSSD remediation

Responder activation conflict corrected with a rollback-first change.

The initial classification was SSSD responder activation conflict. Direct responders were configured, three responder sockets were enabled and failed, and config_file_version = 2 was rejected by SSSD 2.12 validation.

Control

Backup and rollback first

A preserved backup and rollback path were created before changing Linux01. The public page does not expose the root backup path.

Change

Smallest justified change

Only the rejected directive was removed. Conflicting NSS, PAM, and PAC responder sockets were disabled, SSSD was restarted, and historical failed-unit state was cleared.

Validation

Identity and SSH passed

sssd.service was enabled and active, zero failed systemd units remained, SSSD configuration validation passed, AD identity lookup passed, and a new AD-authenticated SSH session passed.

Open direct SSSD remediation validation
SSSD remediation traceability
ArtifactValue
Pre-remediation SHA-2563CAD0FB73202D777D41DEE40D6F4D19D4019B9AD30552B37970B55A5CA5AB3BB
Original/backup config SHA-25623ACE1BECA5FF6F7D58200EFE054EA8E5A938E02F37FCE25B1CA1B5D2F05BD14
Post-remediation SHA-256FD55604BFB94487B86FBF631703FA995B9726471689385CCB2D277492AA7CBEE
Source operations commitfb6c286

Claim boundaries

The public proof is intentionally narrow.

Scope

Personal lab only

This is a personal, nonproduction home lab. No client, employer, production, business, enterprise-scale, or operational-impact claim is made.

Privacy

Raw private material excluded

Raw target-local inventories, raw event logs, complete SSSD configuration files, authentication attempt details, local user paths, ticket-cache identifiers, secrets, keys, and tokens are not public.

Testing boundary

Reachability is not full service validation

TCP reachability can support a narrow network observation, but it is not complete application, authentication, firewall-policy, or service-correctness validation.

Recovery boundary

One restore drill is not recurring DR assurance

The direct restore evidence supports one isolated Linux01 restore drill to temporary VM 401. It does not establish recurring disaster-recovery assurance, RTO, RPO, SLA, or production readiness.