In my previous post, I tried to lay out the foundation and reasoning behind requiring a Dynamic DNS Service, and here is how I solved it using CloudFlare.
First of all, I moved my chosen domain name to CloudFlare, and made sure everything resolved ok with static records. Once that was working, I started playing around with the CloudFlare API, using Cocoa Rest Client. I’m no developer (as is probably very apparent by the script below), nor API wizard of any kind, but it was fairly easy figuring out how to craft a request that lists my DNS zone.
While working on my new Homelab setup, I’ve been investigating ways to provide hostname based access to several web services located in my DMZ zone. Since my provider doesn’t provide static IP addresses, I also need an external Dynamic DNS service, to provide said hostname mappings through the reverse proxy on the inside.
There are loads of Dynamic DNS services available, most of them lets you use some sort of predefined domain name scheme, and point it to your external IP, but I wanted to use a domain name that I own and control. Since I use CloudFlare to provide DNS services (amongst other things) for this very site, it was a natural choice to see if they could fit the bill for my lab needs as well. Turns out, not only can they provide the services I need for free, they also allow me to play around and have fun at the same time!
Way back in 2013, I published Preserve your Veeam B&R Backups Jobs when Moving vCenter, outlining how to “cheat” (by using a CNAME alias) to preserve your Veeam Backup & Replication jobs if you replace your VMware vCenter.
Naturally, when there is a new vCenter instance, all the Virtual Machine Managed Object Reference’s (MoRef) change, which makes Veeam Backup & Replication start a new backup/replication chain, since all VMs are treated as new ones. Not ideal by any means, but at least you wouldn’t have to recreate all your jobs.
A few days ago I decided to go full-on mad scientist in documenting my new home lab / network setup, and I’ve even created a GitHub repository for it. The idea is to create a framework for developing this kind of documentation, heavily influenced by the VCDX methodology and framework. Over time, Conceptual, Logical and Physical designs will be added, as well as configuration settings and operational procedures. Hopefully it’ll also contain some useful diagrams.
While I was away on a two week holiday on the Croatia’s sunny Makarska Rivijera, Eric Siebert announced the result of his annual Top vBlog, and much to my surprise vNinja did quite the jump from last years 46th spot to this years 27th! Honestly, I thought the site would drop out of the the top 50 list this year, but once again I’m proven to be mistaken. Some times being wrong is just great!
A little while ago William Lam published a little python script called extract_vsphere_deployment_topology.py that basically lets you export your current vSphere PSC topology as a DOT (graph description language) file. Great stuff, and in itself useful as is, especially if you run it through webgraphviz.com as William suggests.
The thing is, you might want to edit the topology map, change colours and fonts, and even move the boxes around, after you get the output. If you have a large environment, you might want to combine all your PSC topologies into a single document? It turns out, that’s pretty easy to do!
Way back in late 2014 I volunteered to do technical review for a book called **IT Architect: Foundation in the Art of Infrastructure Design: A Practical Guide for IT Architects. **Due to a lot of unforeseen events, the book has been delayed quite a bit, but it’s finally available as hardcopy, paperback and eBook! The book is written by J****ohn Yani Arrasjid, VCDX-001, Mark Gabryjelski, VCDX-023, Chris McCain, VCDX-079 and as the title states it really does lay out the foundation of how to approach infrastructure design in a modern virtualised data center.
PernixData, and Frank Denneman, has released vSphere Design Pocketbook v3. As the title reads, this is the third time PernixData releases one of these books, and I’m honored to be selected amongst the contributors for the second time, this time with a chapter called “VCSA vs Windows vCenter - Which One Do I Choose, and Why?”
Go grab your electronic copy now, and be sure to bug your local PernixData representative for a hard-copy later. I know I will.