vlab VS LabBuilder

- 47-49: Resource cluster These hosts run the hands on lab pods/vms. 47/49: Supermicro X10SDV, Xeon-D 1541, 8c/16t, 128GB ram, local NVME for ONTAP system disks, 6x2TB SSD pass through for software RAID. This is an HA pair of storage nodes in a shared nothing configuration, raid4 at the node level, with mirrored plexes between nodes. It provides the bulk of the lab storage. 48: Supermicro X10SLR, Xeon E5-2697v4, 18c/36t, 256GB ram 30: QNAP NAS for ISOs, scratch space, and a few containers. 29: SimplyNUC Sequoia, Ryzen 1605b, 32gb RAM, 2TB NVME This one is primarily a KVM host running RockyLinux, but doubles as a VMware workstation. And the switch in the middle of all this is a CISCO SG300-28. Automation: vlab: https://github.com/madlabber/vlab This project includes a node.js web portal, and powershell driven flexclone based provisioning engine that can clone large complex lab environments almost instantly. It combines VMware's PowerCLI and NetApp's PSTK to orchestrate the workflows. Some of this code dates back to the days when powershell was windows only so it still runs on windows, for that reason I am using Myrtille as the HTML5 RDP client in the portal. LabBuilder: https://github.com/madlabber/labbuilder This Ansible project automates the creation of the master lab pods. Lab pods are defined in yaml formatted ansible inventory files, and constructed by a playbook that calls roles for each supported lab component. Currently that includes: - Windows Server - Centos Linux derivatives (Rocky,Alma,RHEL) - PfSense routers - Ubuntu Server - Nested ESXi - vCenter Server - StorageGrid nodes - ONTAP Clusters - OVA packages It also handles some of the complexities I couldn't handle with a traditional "deploy from template" approach such as shared virtual disks and interconnected serial ports.

- 47-49: Resource cluster These hosts run the hands on lab pods/vms. 47/49: Supermicro X10SDV, Xeon-D 1541, 8c/16t, 128GB ram, local NVME for ONTAP system disks, 6x2TB SSD pass through for software RAID. This is an HA pair of storage nodes in a shared nothing configuration, raid4 at the node level, with mirrored plexes between nodes. It provides the bulk of the lab storage. 48: Supermicro X10SLR, Xeon E5-2697v4, 18c/36t, 256GB ram 30: QNAP NAS for ISOs, scratch space, and a few containers. 29: SimplyNUC Sequoia, Ryzen 1605b, 32gb RAM, 2TB NVME This one is primarily a KVM host running RockyLinux, but doubles as a VMware workstation. And the switch in the middle of all this is a CISCO SG300-28. Automation: vlab: https://github.com/madlabber/vlab This project includes a node.js web portal, and powershell driven flexclone based provisioning engine that can clone large complex lab environments almost instantly. It combines VMware's PowerCLI and NetApp's PSTK to orchestrate the workflows. Some of this code dates back to the days when powershell was windows only so it still runs on windows, for that reason I am using Myrtille as the HTML5 RDP client in the portal. LabBuilder: https://github.com/madlabber/labbuilder This Ansible project automates the creation of the master lab pods. Lab pods are defined in yaml formatted ansible inventory files, and constructed by a playbook that calls roles for each supported lab component. Currently that includes: - Windows Server - Centos Linux derivatives (Rocky,Alma,RHEL) - PfSense routers - Ubuntu Server - Nested ESXi - vCenter Server - StorageGrid nodes - ONTAP Clusters - OVA packages It also handles some of the complexities I couldn't handle with a traditional "deploy from template" approach such as shared virtual disks and interconnected serial ports.

madlabber's LabBuilder