Projects explained through the problem solved.

A single-node Proxmox platform operated over time with 12 VMs and several specialized roles.

Problem

Make the actual running infrastructure match configurations that are understandable, reconstructible and controllable.

Method

• Inventory dependencies and runtime state
• Compare each service with its Compose definition
• Pin images and validate without a global recreate
• Retain evidence, rollback and residual debt

Outcome

49 services aligned across 26 canonical Compose projects, with 47 pinned external images and two explicit local builds.

Demonstrated skills

Audit • Linux • Virtualization • Containers • Change management

The platform needed to correlate availability, system state, public exposure, logs and backups.

Problem

Reduce noise, remove obsolete signals and prevent a misplaced probe from producing a falsely reassuring status.

Method

• Map targets and signal ownership
• Remove duplicates and rules without a source
• Test Error, NoData and recovery states
• Measure availability, latency and capacity over 30 days

Outcome

69 useful monitored targets, instrumented local proxy health and retained SLO budgets even when exhausted.

Demonstrated skills

Troubleshooting • Metrics • Alerting • Log analysis • SLO

VM backups existed, but their presence alone did not demonstrate controlled recovery.

Problem

Prove coverage and verification, define dependencies, then clearly distinguish backup, recovery and high availability.

Method

• Check tasks, retention and verification
• Classify services by criticality
• Define RTO, RPO and recovery order
• Document limits and exercises still required

Outcome

Expected eligible-workload coverage confirmed, recent verification evidenced, logical restores performed and DR documented without claiming unavailable high availability.

Demonstrated skills

Backup • Disaster recovery • Risk analysis • Documentation • Integrity checks

Selected internal services need remote access without directly exposing their hosts.

Problem

Centralize publishing, retain consistent TLS termination and make public-path state measurable.

Method

• Separate functional zones
• Publish through a central control point
• Add filtering, headers and detection
• Validate locally and externally

Outcome

Exposure limited to the reverse proxy, monitored path health and retained rollback procedures.

Demonstrated skills

Segmentation • Reverse proxy • TLS • Hardening • End-to-end validation

At IP INFOPRO, I contribute to daily operations across user environments and network infrastructure.

Problem

Resolve incidents and requests while preserving permissions, policies, connectivity and service continuity.

Method

• Qualify the request and impact
• Diagnose from endpoint to service
• Apply the smallest necessary change
• Verify the outcome and record the intervention

Outcome

Hands-on work with Windows Server, Active Directory, GPO, user rights, L1/L2 support, VLANs, VPNs, active equipment and backups.

Demonstrated skills

L1/L2 support • Windows administration • Networking • Communication • Operations

Decisions and operations needed to remain understandable after each change window.

Problem

Prevent validation, commands and rollback paths from depending on operator memory.

Method

• Write prerequisites and success criteria
• Automate non-destructive controls
• Generate dated, hashed evidence
• Version declarative material without secrets

Outcome

A locally validated repository, integrity manifest, change log and runbooks connected to technical evidence.

Demonstrated skills

Documentation • Scripting • Git • Quality control • Traceability