Scott's Weblog The weblog of an IT pro specializing in virtualization, networking, open source, and cloud computing

Technology Short Take #49

Welcome to Technology Short Take #49 (also known as Distraction-as-a-Service)! I have here for your reading pleasure an eclectic collection of links and articles from around the web, focusing on data center-related technologies. Here’s hoping you find something useful. Bring on the content!

Networking

  • I love this post from Matt Oswalt on five next-gen skills for networking pros. I highly recommend you read the entire post, but in short the five skills Matt recommends are software skills (which includes configuration management and software development tools like Git), Linux, deep protocol knowledge, hypervisor and container networking, and IPv6. What’s really interesting to me is the (completely uncoordinated) alignment between Matt’s list of skills for networking pros and the list I provided to virtualization pros in a series of recent VMUG presentations (refer to slide 15, but the list is software development basics, Linux, automation/orchestration, and public cloud services). What does this mean? It tells me that some skills—specifically, Linux, automation/configuration management, software development concepts—are going to be essential for all new IT pros in the near future. If you want to stay relevant, regardless of your current “silo,” it’s time to evolve.
  • Carl Niger has a write-up on the introduction of the Nexus 1000v BGP control plane, which uses BGP to help VXLAN figure out which MAC addresses live at which VTEPs. His article also provides a quick look at some of the configuration commands involved.
  • I don’t think I’ve mentioned this before; if I have, please forgive me. Anthony Burke (disclaimer: Anthony works for VMware in the NSBU) has a post on how to use Python to automate the bulk creation of firewall rules for use with the VMware NSX distributed firewall.
  • You may have heard about the “6-pack”, Facebook’s new open modular hardware switch introduced recently (here’s a post on it). With the introduction of 6-pack (as with Wedge, Facebook’s top-of-rack switch before it), many people have proclaimed that Facebook is now competing directly with Cisco. Not everyone agrees, though—here’s Steven Noble’s take on the introduction of 6-pack and why this is pushing the networking industry forward.
  • James (Just James), author at The Technical Blog of James, shared his thoughts—both good and bad—on Cumulus Networks and treating the switch as a standard GNU/Linux server.
  • There’s been a lot of talk about using configuration management tools like Puppet, Chef, Salt, and Ansible to manage networking devices, but (at least as far as I can tell) there haven’t been a lot of practical examples. That seems to be changing now—here’s an example of using Ansible to set up OSPF in a test environment.
  • Dmitri Kalintsev (disclaimer: he works for the NSBU at VMware, as I do) has a write-up on the different control plane modes for VXLAN in VMware NSX. It’s a pretty detailed article with lots of useful information.

Servers/Hardware

  • This news came out of Mobile World Congress (MWC) 2015: Ericsson has announced a new “hyperscale” hardware platform based on Intel’s Rack Scale Architecture (RSA). With all the focus on NFV, it’s interesting to see vendors like Ericsson—whose business has been traditionally hardware-based—shift into “new” platforms in a bid to retain control of their customer base. I guess this underscores the difficulty for hardware-based companies to shift to a more software-based business.

Security

Cloud Computing/Cloud Management

  • If you want to get a rough feel for how some of the OpenStack projects are changing from Juno to Kilo, this post on 12 highlights from the OpenStack roadmap might be a good start.
  • Heard of Kubernetes, but not really sure what it is or what it does? Afraid to ask that question because…well, doesn’t everyone know about Kubernetes? No fear, Google has a post on everything you wanted to know about Kubernetes but were afraid to ask. You’re welcome.
  • Still trying to wrap your head around OpenStack’s use (when using the Open vSwitch plugin) of OVS+Linux bridges+IPtables? You might find this article by Venu Murthy helpful.
  • Most people aren’t really interested in the details of a given cloud management platform’s APIs, but if you are interested, Matt Curry takes a walk through some of the OpenStack APIs by spinning up a server on Rackspace. Readers seeking a bit more detail on the APIs should find this write-up useful.
  • Based on this article, it looks like filesystem quiescing and the ability to take consistent snapshots might be coming in OpenStack Kilo.

Operating Systems/Applications

  • Per my list of 2015 projects, I’ve been investigating other configuration management systems (I’ve primarily focused my efforts on Puppet until now). I found this post comparing Ansible and Salt to be quite helpful, particularly given some of the comparisons with Puppet.
  • NixOS seems to be an interesting re-think of a Linux distribution. Sure, it has atomic upgrades and rollbacks, like CoreOS, Ubuntu Snappy Core, and Project Atomic. But it also uses a completely declarative approach to the entire OS build, allowing users to define the exact NixOS build they desire in a NixOS-specific build language (somewhat of a domain-specific language, a DSL). While this offers some power for those who understand it, I wonder if this won’t make it a bit too complicated to see broad adoption.
  • Puppet Labs recently blogged about the new VMware vRealize Orchestrator plugin for Puppet. The plugin allows users to bootstrap the Puppet agent as VMs are created and provisioned. It sounds pretty handy if you’re a combined VMware-Puppet shop.
  • You’re probably tired of hearing about containers, but for those that aren’t…Michael Crosby has a pretty detailed write-up on container internals, complete with code examples. Nifty.
  • Much is said about how Docker enables applications to be moved about from Linxu distribution to Linux distribution, but I don’t think that complete kernel independence has been achieved yet. This blog post highlights just one example.
  • In the event you like to keep your eyes on not only where the industry is headed now but also to where the industry might be headed next, this article by Darren Rush talks about unikernels and immutable infrastructure as possible “next steps” in the evolution of the cloud.
  • Having recently started exploring Ansible, I liked this article by Jason Edelman on how to generate Markdown documents for Ansible modules. That’s pretty handy.
  • Brent Salisbury has a very handy write-up of some Docker command-line one-liners. I suspect this is an article I’ll be referencing frequently. I’m also looking forward to spending a bit of time working with SocketPlane in the near future.

Storage

Nothing this time around, but I’ll keep my eyes peeled for content to include in future posts!

Virtualization

Career/Soft Skills

  • I saw this post by Martin Glassborow (aka “Storagebod”), wherein he talks about three types of folks: the daredevils to come up with crazy new ideas, the implementers/finishers to take those crazy ideas and make them the “new normal,” and the folks to run the “new normal” now that it has become boring. This is strikingly similar to Simon Wardley’s pioneers/settlers/town planners model and Cringely’s commandos/infantry/policy model (described here). (I’m personally a fan of the commandos/infantry/police model, myself.) I mentioned this here because I think it’s important for us to understand where we fit in these models—are we commandos, or are we infantry? Are we police? There’s no right or wrong answer; some people are better suited to certain roles. The reason it’s important for us to know the answer, though, is that it helps us understand if we are in the right role for us. Are you unhappy in your current role? Perhaps you’re being asked to be a police officer when what you’re really best suited for is infantry (or even a commando). Anyway, it’s something to think about.

Well, this post turned out to be quite hefty (over 1600 words!) Sorry for the length; there’s just so much good content out there that I want to share with my readers. In any case, thanks for sticking around to read the whole post.

Be social and share this post!