Back to portfolioPROJECT CASE STUDY / 05
INFRASTRUCTURE & OBSERVABILITY LAB

ENGINEERING PROJECT / 05

NexusCloud.

CASE STUDY
2026

A local-first infrastructure engineering lab focused on service isolation, observability, controlled failure testing and secure site-to-site routing. The current implementation is a reproducible local lab, not a deployed hybrid-cloud environment.

PROJECTNexusCloud
TYPEINFRASTRUCTURE & OBSERVABILITY LAB
TECHNOLOGIES10 core tools
Docker ComposeNginxPrometheusGrafanaBlackbox ExporterNode ExporterWireGuardLinux namespacesPowerShellBash

01 / CONTEXT

THE WHY

The challenge

NexusCloud began as a hybrid-cloud design exercise connecting an on-premises virtual data center to Oracle Cloud Infrastructure. Practical account and local virtualization constraints made an end-to-end cloud deployment unreliable, so the scope was narrowed to a working local environment that can be started, inspected and tested repeatedly.

02 / SYSTEM DESIGN

THE STRUCTURE

How the pieces fit together

A high-level view of the documented workflow and component boundaries.

01

Isolated application sites

Two Nginx sites run as separate containers on independent Docker bridge networks.

02

Metrics and probing

Prometheus scrapes service and host metrics; Blackbox Exporter probes both sites for HTTP availability.

03

Dashboards and alert rules

Grafana is provisioned with a Prometheus data source and dashboard. Prometheus alert rules cover site availability and missing targets.

04

Host telemetry

Node Exporter exposes host metrics to the monitoring stack.

05

Independent VPN routing lab

Linux network namespaces model two site routers and two clients connected by WireGuard. This exercise is separate from the Docker application networks.

03 / ENGINEERING LOG

THE BUILD SEQUENCE

How the work took shape

A transparent sequence of engineering milestones. Status labels describe documented work—not a live completion percentage.

  1. 01
    01 · SCOPEDocumented

    Narrow the hybrid-cloud concept

    Retained the infrastructure and networking learning goals while documenting that OCI provisioning and the broader enterprise design remain future work.

  2. 02
    02 · ISOLATIONImplemented

    Build two independent service networks

    Used Docker Compose to run two Nginx sites on separate bridge networks with local-only published ports and container health checks.

  3. 03
    03 · OBSERVABILITYImplemented

    Collect metrics and probe availability

    Connected Prometheus, Blackbox Exporter, Node Exporter and Grafana with provisioned dashboards and alert rules.

  4. 04
    04 · FAILURE TESTINGImplemented

    Exercise alert and recovery behavior

    Added a controlled failure-injection workflow that stops a selected site, checks that its alert fires, restores the container and verifies recovery.

  5. 05
    05 · SECURE ROUTINGImplemented

    Simulate a site-to-site WireGuard tunnel

    Created isolated Linux router and client namespaces with a WireGuard tunnel and tests for bidirectional client traffic and prefix restrictions.

04 / DESIGN JUDGMENT

TRADE-OFFS & REASONS

Decisions behind the design

The engineering choices that shape the system—and the reason each boundary exists.

01

Keep the current build local-first

A reproducible local lab makes service boundaries and failure behavior inspectable without claiming an OCI environment that was not deployed.

02

Separate the VPN exercise from Docker application traffic

The WireGuard namespaces demonstrate routed site-to-site connectivity independently; the Docker application containers do not traverse the tunnel.

03

Use controlled failures to verify alert recovery

Stopping and restoring a test site checks both alert firing and recovery instead of relying only on a static dashboard screenshot.

04

Keep credentials and private keys outside version control

The Grafana password is supplied through a local .env file, while generated WireGuard keys and populated peer configurations are stored outside the repository.

05 / NEXT INVESTIGATION

THE NEXT USEFUL TEST

What I would test next

Add a repeatable end-to-end test that verifies the Grafana dashboard provisioning, alert delivery path and WireGuard tunnel state from a clean environment. Keep OCI deployment as a separate future milestone with its own cost, identity and network-security review.

06 / IMPLEMENTATION

THE HOW

Engineering approach

The work is broken into practical building blocks, from initial design through to validation.

  1. 01

    Runs two Nginx application sites on separate Docker bridge networks.

  2. 02

    Uses Prometheus and Blackbox Exporter to monitor HTTP availability and Node Exporter for host metrics.

  3. 03

    Provides Grafana dashboards and provisioned Prometheus alert rules.

  4. 04

    Tests controlled site outages, alert firing, service recovery and alert clearing.

  5. 05

    Models two site routers and two clients in Linux network namespaces connected by WireGuard.

  6. 06

    Uses PowerShell and Bash scripts plus GitHub Actions for repeatable validation.

07 / VERIFICATION

THE CHECKS

Validation & evidence

Specific checks documented for this project. Results are scoped to the recorded lab or test run.

Application isolationConfigured

Two Nginx sites are attached to separate Docker bridge networks and publish only to localhost.

Monitoring targets4 expected targets

The README documents four expected Prometheus scrape targets as the monitoring baseline.

Alert lifecycleFailure & recovery

The documented test stops a site, waits for its alert, restores it and checks that the probe and alert recover.

VPN routingBidirectional test

The WireGuard lab validates client-to-client traffic, tunnel handshake and allowed-prefix restrictions.

AutomationGitHub Actions

The repository documents Compose checks, shell syntax checks, service smoke tests, Prometheus checks and Linux network/port validation.

08 / RESULTS

THE VALUE

What this project demonstrates

01

A reproducible local infrastructure stack with service separation and centralized observability.

02

A controlled way to demonstrate monitoring, alert firing and recovery.

03

A separate WireGuard routing simulation with explicit network namespaces and prefix restrictions.

04

Operational scripts, documentation and CI checks that make the lab easier to repeat.

10 / ENGINEERING NOTES

TRANSPARENCY

Scope, assumptions & limitations

Clear boundaries matter. These notes describe what the current project does—and what it does not claim to do.

  • The current project is a local lab, not a deployed hybrid-cloud or production infrastructure environment.
  • Oracle Cloud Infrastructure provisioning and the broader original enterprise architecture remain design goals, not implemented components.
  • The Docker application containers do not send traffic through the WireGuard tunnel.
  • Monitoring and alert tests demonstrate the documented lab configuration; they do not establish production-grade availability or security.
  • The lab requires Windows with WSL2, Ubuntu and Docker Desktop for the documented workflow.