Current VM List - vintagedon/ai-ops-home-lab GitHub Wiki
Current VM List 🖥️
Overview
This page provides an up-to-date list of all Virtual Machines (VMs) currently running in the Project Synapse lab environment. Each VM is configured to support various aspects of the lab’s infrastructure, from AI workloads to DevOps practices. This list will be regularly updated as the lab evolves and new VMs are added or existing ones are reconfigured.
VM Table w/Node Capacity
Note that this section changes a lot. Am moving most VM workloads to containerized workloads, which some will then be moved into the k8s cluster.
Oversubscribing vCPU: since this is a lab environment and not under a production 24/7 workload, I do allow some core oversubscribing, but generally not more than 125%-150%.
For core/RAM balance, nodes 1-3 are 1 vCPU = 4GB of RAM, while node4 is 1 vCPU = 8GB of vRAM. This can vary, but is a good rule of thumb when assigning core/RAM usage.
Node01
VM Name | Cores | RAM | Disk 1 | Disk 2 | Node |
---|---|---|---|---|---|
dc01 | 2 | 6144 | 125G | N/A | node01 |
work01 | 2 | 6144 | 125G | N/A | node01 |
monitor01 | 2 | 4096 | 32G | 250G | node01 |
k8sworker01 | 8 | 32768 | 32G | 250G | node01 |
pihole02 | 1 | 2048 | 32G | N/A | node01 |
Node02
VM Name | Cores | RAM | Disk 1 | Disk 2 | Node |
---|---|---|---|---|---|
gitea01 | 1 | 2048 | 32G | N/A | node02 |
ansible01 | 1 | 2048 | 32G | N/A | node02 |
docker01 | 4 | 16384 | 32G | 250G | node02 |
k8sworker02 | 8 | 32758 | 32G | 250G | node02 |
Node03
VM Name | Cores | RAM | Disk 1 | Disk 2 | Node |
---|---|---|---|---|---|
k8sworker03 | 8 | 32768 | 32G | 250G | node03 |
loki01 | 1 | 2048 | 32G | N/A | node03 |
visualize01 | 1 | 2048 | 32G | N/A | node03 |
docker02 | 4 | 16384 | 32G | 250G | node03 |
Node04
VM Name | Cores | RAM | Disk 1 | Disk 2 | Node |
---|---|---|---|---|---|
dc02 | 2 | 6144 | 125G | N/A | node04 |
work02 | 1 | 2048 | 32G | N/A | node04 |
port01 | 1 | 2048 | 32G | N/A | node04 |
k8smaster01 | 4 | 8192 | 32G | N/A | node04 |
docker03 | 2 | 8192 | 32G | 250G | node04 |
Node Capacity Summary
Node | Cores Used | Total Cores | % Core Usage | RAM Used | Total RAM | % RAM Usage | Disk 1 Used | Disk 2 Used | Total Disk | % Disk Usage |
---|---|---|---|---|---|---|---|---|---|---|
node01 | 15 | 16 | 93.75% | 50,048 MB | 64,000 MB | 78.20% | 346 GB | 500 GB | 2,500 GB | 33.84% |
node02 | 14 | 16 | 87.50% | 53,238 MB | 64,000 MB | 83.19% | 128 GB | 500 GB | 2,500 GB | 25.12% |
node03 | 14 | 16 | 87.50% | 53,238 MB | 64,000 MB | 83.19% | 128 GB | 500 GB | 2,500 GB | 25.12% |
node04 | 10 | 16 | 62.50% | 26,624 MB | 128,000 MB | 20.80% | 253 GB | 250 GB | 4,250 GB | 11.82% |
Detailed VM Descriptions
🖥️ Lab Virtual Machine Overview
VM Name | Primary Function | Description |
---|---|---|
ansible01 | Ansible Controller | Primary Ansible controller with Semaphore for orchestrating automation tasks across the lab environment. |
dc01, dc02 | Domain Controllers | Primary and secondary domain controllers. Hybrid-joined to Microsoft Entra (formerly Azure AD) via AD Connect Sync, with password writeback and passthrough authentication enabled for seamless identity management. |
docker01 | Database Containers | Hosts containerized database services including MariaDB, PostgreSQL, SQL Server 2022 on Linux, MongoDB, Neo4j, InfluxDB, and Redis. Provides a variety of database options for development and testing. |
docker02 | Application Containers | Runs containerized applications such as Nginx Proxy Manager for reverse proxy and load balancing, and DbGate for database management and administration. |
docker03 | Home Server Applications | 'House' docker server hosting various personal and productivity applications: Jellyfin (media server), Navidrome (music streaming), Paperless-ngx (document management), Firefly III (personal finance management), Nextcloud (file hosting), and Audiobookshelf (audiobook server). |
gitea01 | On-Premises Git Server | Hosts Gitea, an on-premises repository for Infrastructure as Code (IaC). Selectively mirrors repositories to GitHub and Azure DevOps for backup and collaboration. |
k8s master01, workers01-03 | Kubernetes Cluster | RKE2 Kubernetes cluster with one master and three worker nodes. Total resources: 32 vCPUs, 96GB RAM. Used for container orchestration and microservices deployment. |
loki01 | Log Management | Runs Loki for centralized log aggregation and management across the lab environment. |
monitor01 | Metrics Collection | Prometheus server collecting and storing metrics from all VMs and the Kubernetes cluster for monitoring and alerting purposes. |
pihole02 | DNS Filtering | Provides DNS filtering for lab traffic with conditional forwarding to the domain controllers, enhancing network security and control. |
port01 | Container Management | Hosts Portainer for easy management and orchestration of Docker containers on docker01, docker02, and docker03. |
puppet01 | Configuration Management | Puppet server for automated configuration management across the lab, ensuring consistency and ease of maintenance. |
visualize01 | Data Visualization | Runs Grafana for metrics visualization and OpenWebUI for AI-assisted data analysis and reporting. |
work01 | Windows Work Environment | Windows 11 Pro 'work' VDI, Entra-Joined, Auto-Pilot, Intune Managed |
work02 | Linux Work Server | Linux-based server for development, testing, and running various work-related applications and services. |
This table provides an overview of the virtual machines in our lab environment, detailing their primary functions and roles within the infrastructure. Each VM is designed to fulfill specific purposes, from identity management and containerization to monitoring and productivity applications, creating a comprehensive and diverse lab setup for various testing and development scenarios.
Update Log
- [Sep 1 2024]: Refresh of original wiki page
Example entries:
- [Date]: Added VM [Name] for [Purpose].
- [Date]: Reconfigured VM [Name] to [New Configuration].
- [Date]: Decommissioned VM [Name].
Notes
This VM list is essential for tracking resource allocation and understanding the current setup of the Project Synapse lab. If any changes are made to the VMs, this page will be updated to reflect those changes.
For any questions or further information, please refer to the Contact Page or open an issue in the repository.