A Quadruple-Provider Vagrant Environment
In October 2016 I wrote about a triple-provider Vagrant environment I’d created that worked with VirtualBox, AWS, and the VMware provider (tested with VMware Fusion). Since that time, I’ve incorporated Linux (Fedora, specifically) into my computing landscape, and I started using the Libvirt provider for Vagrant (see my write-up here). With that in mind, I updated the triple-provider environment to add support for Libvirt and make it a quadruple-provider environment.
To set expectations, I’ll start out by saying there isn’t a whole lot here that is dramatically different than the triple-provider setup that I shared back in October 2016. Obviously, it supports more providers, and I’ve improved the setup so that no changes to the Vagrantfile are needed (everything is parameterized).
With that in mind, let’s take a closer look. First, let’s look at the Vagrantfile itself:
# Specify minimum Vagrant version and Vagrant API version
Vagrant.require_version '>= 1.6.0'
VAGRANTFILE_API_VERSION = '2'
# Require 'yaml' module
require 'yaml'
# Read YAML file with VM details (box, CPU, and RAM)
machines = YAML.load_file(File.join(File.dirname(__FILE__), 'machines.yml'))
# Create and configure the VMs
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# Always use Vagrant's Continue reading
Vestberg is a relative newcomer to Verizon but as the former CEO of Ericsson he has a long history in the telecom industry.


IHS Markit also reported drops in SD-WAN revenue for Huawei and InfoVista, but these could simply be reflections of quarterly variations in contracts.
If you are considering an SD-WAN or if you already have implemented the technology, let us know what challenges you are facing and what innovations are most compelling.
AT&T said it will still use its own cloud-based connectivity platform but it will work with WING so IoT customers have a single portal to manage their devices.