#Opendns updater edgerouter windows
Lab Environment & Deployed Apps Microsoft Windows Server Lab:
These templates are used for later infrastructure provisioning. The following repos use Ansible to create Proxmox template images (and handle OS / package updates) for my most frequently used VM operating systems. VM deployments based on a template are much faster than running through a new install. UptimeRobot for remote network monitoring.UPS power status & consumption monitoring.Once complete, manually create cluster on one node, join other nodes to cluster, and configure cluster data storage specific to implementation details. Proxmox configuration requires installation of Proxmox VE on each node, followed by running Ansible playbook (after customization). K3s cluster is provisioned with Rancher's Ansible playbook. After a few minutes, based on defined inventory role, provisioning is complete and ready for any further config. Requires flashing SD card(s) with Ubuntu, and copying in the customizable CloudInit user-data file (included in repo) to the boot partition before inserting into and starting each Pi.
#Opendns updater edgerouter install
Raspberry Pis are each configured with an Ansible playbook, pulled at OS install from another of my GitHub repos: Authoritative DNS: AD domain controller VMs) ad. (Purpose: Windows Active Directory.(Purpose: private IP space / internal resource access by FQDN.Managed switch: currently no special config, but will likely implement VLANs in the future.DNS Resolver (default): EdgeRouterX to upstream ISP router to OpenDNS.Otherwise locally attached storage (R610 RAID controller limitation not allowing JBOD passthrough restricts ability to use Ceph and other cluster storage technologies).Old, and requires SMB v1, target for replacement. 1x Buffalo 500 GB NAS (backups, image storage, etc).1x Netgear JGS524E 24-port managed switch.Provides routing, firewall, DHCP, DNS to lab, as well as inbound VPN Roles: 4x K3s cluster members, 1x standalone running Docker and serving as an Ansible control node, all running Ubuntu Server.
Roles: 3x Proxmox VE hypervisors, 1x cold standby, 1x spare parts.Ea: 96 GB RAM, 2x 73 GB HDD (RAID-1 for OS), 4x 450 GB HDD (local data storage).Lots of Ansible for automation of provisioning and configuration.4-node Raspberry Pi K3s / Ubuntu Server cluster for ARM-compatible containerized workloads.3-node Proxmox VE cluster for KVM based virtual machines and LXC containers.Codified & documented config leading to trivial re/deployments.Totally separate lab env from home (don't want tinkering to impact "home" WiFi, DNS, storage, etc in any way).Raspberry Pis always on, power-hungry servers powered on as needed - so any "critical" roles (dynamic DNS updater, etc) should reside on a Raspberry Pi.A stable base platform of hypervisors & container hosts on physical hardware, on which further virtualized or containerized products can be easily deployed without impact to the base platform.Basic provisioning & configuration of both supporting infrastructure and additional products is documented here - mostly so I remember how I did stuff. This (WIP) page describes a home lab environment for evaluation and testing of various technologies. Home Lab Status: This has been replaced with Overview
0 kommentar(er)
