Scott's Weblog The weblog of an IT pro focusing on cloud computing, Kubernetes, Linux, containers, and networking

Technology Short Take #67

Welcome to Technology Short Take #67. Here’s hoping something I’ve collected for you here proves useful!


  • Anthony Burke has written a script that uses VMware NSX to protect VMware Log Insight instances. More information on the script is in his blog post.
  • Russ White tackles the issue of networking engineers needing to learn to code. Is it necessary? Russ thinks so—but probably not for the reasons you might think. I tend to agree with Russ’ line of thinking.
  • This article from Marcos Hernandez shows one way to do dynamic routing in OpenStack. It’s a bit of a hack, to be honest, but it gets the job done until dynamic routing makes its way into OpenStack Neutron (which looks like it may have landed in the Mitaka release—can anyone confirm?).
  • Jason Messer has an article describing how networking works with Windows containers.
  • Tom Hollingsworth discusses how the rise of overlay networks killed large layer 2 networks and tools for building large layer 2 networks, like TRILL.
  • Dmitri Kalintsev examines some options for addressing storage-related connectivity in NSX environments.


  • Drew Conry-Murray shines a light on Intel’s network ambitions. This is something I’ve been watching for a couple of years, since attending my first Intel Developer Forum (IDF). Intel clearly has its sights set on expanding beyond just “servers” into many more platforms, including network hardware platforms.


Cloud Computing/Cloud Management

Operating Systems/Applications

  • Someone recently pointed this out. It looks like container-optimized OSes designed to run in VMs on a hypervisor are becoming all the rage these days. (Maybe VMware’s Photon OS wasn’t such a crazy idea after all?)
  • OS X users might find this Apple support article on OS X wireless roaming to be helpful.
  • You may have heard about Microsoft’s announcement regarding running Bash on Windows; here’s an article written by Deepu Thomas with more details on the Windows Subsystem for Linux (WSL), which makes running native Linux ELF64 binaries on Windows possible. (By the way, I alluded to this sort of architecture in December 2006 while discussing the future of the operating system; see this blog post.)
  • I mentioned this on Twitter, but wanted to include it here as well. Read this article by Mary Rose Cook for an excellent review of how Git works.
  • I believe I’ve mentioned the change in Docker 1.11, where Docker Engine is now built on runC (the container runtime) and containerd (a daemon controlling runC). Tiffany Jernigan has a good post outlining the changes and how it all ties together.



  • Usually, articles talking about nested virtualization use ESXi as the “base hypervisor” and are running KVM, Xen, or Hyper-V as the nested hypervisor. What about flipping that on its head, and running ESXi as a nested hypervisor inside Hyper-V? Daniel Scott Raynsford has an article showing exactly that: ESXi running nested on Hyper-V.
  • And while I am on the topic of nested virtualization: here’s an article from William Lam on running OS X as a VM on a nested ESXi instance running under VMware Fusion.
  • This nixCraft article shows how to assign static IP addresses to KVM-based VMs using dnsmasq managed by Libvirt.
  • XenServer 7, aka “Dundee,” was released recently. The features and capabilities of this new release are described in this blog post.
  • Seems like everybody and their brother is launching “container as VM” projects; the latest that I’ve seen is HyperContainer (which, AFAICT, is not the same as Hyper). Information on how HyperContainer integrates with Kubernetes to create—you guessed it—“Hypernetes” is found here. I guess the hypervisor makes a really good isolation tool after all.

Career/Soft Skills

  • I recently had the pleasure of participating in a panel discussion on the future of the data center while at Interop 2016 in Las Vegas. One of my fellow panelists, Sonia Cuff, summarized some of the thoughts and statements from the panel discussion in this blog post.

That’s all, folks…until next time, at least!

Metadata and Navigation

Be social and share this post!