In the previous article, I created three CoreOS VMs and got them to talk to each other using etcd. In this article, we'll be going over cloud-config/config-drive and getting an etcd cluster that automatically starts and discovers new nodes using the freely available discovery.etcd.io service. Cloud Config
I have been noticing my Zabbix server had been alerting on high I/O and CPU wait times on several VMs when multiple servers were powered on or other concurrent high I/O tasks took place. I had a feeling it may have been due to two things: The relative
I now have three CoreOS boxes setup in my home lab - following the steps here. But just having three CoreOS boxes doing nothing is boring, so I've decided to try and accomplish the following: Figure out how to cluster the three CoreOS VMs / get containers to bounce between VMs
Quick list for home lab: Get a few CoreOS nodes deployed. Get Chef installed/configured. (Maybe littlechef would be useful?) Get Salt and/or maybe Ansible. Look into sslh. Look into Docker - perhaps to do some sort of OpenVPN/Proxy/etc?
Although I haven't administered a full enterprise Puppet deployment, I do have some experience with it - both in the masterless configuration and with Puppet master/Puppet Enterprise. I've even attended two classes - completing the Intro and Advanced Puppet courses. Unfortunately, the new job appears to have started down