Fraîche Flow

Linux · Infrastructure · Networking · Virtualisation

docs/Architecture and virtualisation
61 lines1.95 KB

Architecture and virtualisation

MILOUD NECILI

Fraîche Flow · IT Systems Integration

Project objective

Structure a layered lab environment with separate roles for management, networking, storage, applications and communication.

My implementation

  • Worked with Hyper-V and Proxmox while building the lab.
  • Connected the ff-edge-01, ff-pve-01, ff-core-01, ff-store-01, ff-app-01 and ff-mgmt-01 roles on the internal network.
  • Worked on ff-mail-01 as a separate mail host in the Proxmox/LXC context.
  • Documented dependencies between DNS, storage, the web application, the database and administration.

Proxmox infrastructure with ff-core-01, ff-app-01 and ff-mail-01

Technical context

Lab network 192.168.10.0/24
Gateway ff-edge-01 · 192.168.10.1
Hypervisor ff-pve-01 · 192.168.10.10
Core / Storage / App 192.168.10.11 / .12 / .13

Hardware configuration of the ff-app-01 virtual machine

Result

The application layer and communication between the lab roles were used in practice.

Verification and operational evidence

hostname; ip -br a; ip route
lsblk; df -h
systemctl --type=service --state=running --no-pager
docker ps

Practical troubleshooting

The package sources on ff-app-01 showed forky. The actual platform was therefore considered separately from older Debian 12 task specifications. Export the specific VM resources before redeployment.

Security and technical context

A successful training lab does not demonstrate high availability. Production approval requires separate capacity, lifecycle and security decisions.

Transferable skills

Architecture understanding, virtualisation, role modelling and dependency analysis.

Project status

Completed according to confirmation from the project lead.