# Vagrant Published articles for Vagrant. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Sunsetting netlab Vagrant/libvirt provider DevFeed: [Sunsetting netlab Vagrant/libvirt provider]() Original publisher: [Read original article]() Published: 2026-09-17T05:51:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [Infrastructure as code](), [Orchestration](), [Containerlab topology](), [Oracle-VM-VirtualBox]() Tags: [change](), [containers](), [infrastructure](), [infrastructure-as-code](), [netlab](), [orchestration](), [vagrant](), [virtualbox]() ### AI overview The netlab project is sunsetting its Vagrant/libvirt provider after the vagrant-libvirt plugin became effectively unmaintained and HashiCorp announced the closure of Vagrant Cloud by the end of 2026. Existing support and tests will remain for now, but no new libvirt features or device integration tests are planned; containerlab will become the primary orchestration path. ### Source excerpt When I started the netlab project, Vagrant was the go-to tool if you wanted to build a virtual environment described in a text configuration file (an idea popularized as infrastructure-as-code). It wasn't ideal for what we were doing, but a tool rarely does a great job when used far away from its intended use case. netlab initially supported Vagrant with VirtualBox, quickly adding support for KVM/libvirt through the vagrant-libvirt plugin. Life was good... until it wasn't. Read more ... ## How vagrant-libvirt Plugin Deals with Duplicate Subnets DevFeed: [How vagrant-libvirt Plugin Deals with Duplicate Subnets]() Original publisher: [Read original article]() Published: 2026-09-16T06:27:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [virtual machines](), [Linux](), [Ubuntu]() Tags: [debugging](), [linux](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview The article explains that vagrant-libvirt can fail when an existing libvirt virtual network has the same IP subnet as the desired management network but a different name. It identifies the resulting network-name mismatch and reports that correcting the network definition in the Vagrantfile resolves the problem. ### Source excerpt TL&DR: Badly. The vagrant-libvirt plugin mysteriously crashes when an existing virtual network (with a different libvirt name) uses the same IP subnet as the desired management network. Background: netlab is using the vagrant-libvirt plugin to manage libvirt/KVM virtual machines with Vagrant. As I already have that infrastructure, I use it to start standalone virtual machines (usually to test various Ubuntu releases) on my Linux server. Things work great... until they don't. Here's how I managed to waste half a day chasing imaginary gremlins caused by a simple error. Read more ... ## netlab 26.06: OSPFv3 on FortiOS, MPLS/VPN on SR Linux DevFeed: [netlab 26.06: OSPFv3 on FortiOS, MPLS/VPN on SR Linux]() Original publisher: [Read original article]() Published: 2026-06-08T06:13:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [MPLS VPN](), [Ubuntu](), [Vagrant](), [Script]() Tags: [bugs](), [getting-started](), [github](), [guide](), [improvements](), [installation](), [mpls-vpn](), [netlab](), [release](), [ubuntu](), [upgrade](), [vagrant]() ### AI overview The netlab 26.06 release adds OSPFv3 support on FortiOS and MPLS/VPN support on SR Linux. It also updates installation compatibility for Ubuntu 26.04, includes Vagrant 2.4.9, and contains other improvements and bug fixes. ### Source excerpt netlab release 26.06 adds OSPFv3 support on FortiOS (by @a-v-popov) and MPLS/VPN support on SR Linux. We also ensured the installation scripts work on Ubuntu 26.04 (everything else was OK) and updated the installed Vagrant version to 2.4.9 (we're not using new Vagrant features; you don't have to upgrade it in an existing installation). Other than that, we added a few improvements and squashed a number of bugs. Upgrading or Starting from Scratch? To upgrade your netlab installation, execute pip3 install --upgrade networklab. New to netlab? Start with the Getting Started document and the installation guide. Need help? Open a discussion or an issue in netlab GitHub repository. ## netlab 26.04: EXOS, BGP Prefix Origination, More Static Routes DevFeed: [netlab 26.04: EXOS, BGP Prefix Origination, More Static Routes]() Original publisher: [Read original article]() Published: 2026-04-13T05:28:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Release notes](), [BGP](), [IP routing](), [Routing (disambiguation)](), [networking](), [Vagrant](), [evpn](), [VXLAN](), [Containerlab topology]() Tags: [bgp](), [evpn](), [ip-routing](), [linux](), [netlab](), [release](), [release-notes](), [routing](), [vagrant](), [vxlan]() ### AI overview The netlab 26.04 release adds support for Extreme Networks EXOS, new BGP advertisement and origination capabilities, additional platforms with static-route support, and EVPN/VXLAN over IPv6 support in FRRouting. It also expands routing configuration support for several platforms. ### Source excerpt netlab release 26.04 is out. Here are the highlights: Extreme Networks EXOS is supported as a Vagrant box or containerlab node with OSPF, VLAN, and VRRP configuration (by Seb d'Argoeuves). The new bgp.advertise node attribute allows you to advertise networks in the IP routing table into BGP. It's supported on most platforms. The bgp.originate attribute is now dual-stack and VRF-aware, allowing you to originate IPv4 and IPv6 prefixes into per-VRF BGP instances. New platforms with static route support: FortiOS (by Aleksey Popov), Nexus OS, Nokia SR OS, Nokia SR Linux. OpenBSD got discard static routes. Read more ... ## Open-Source Network Simulators (2026 Edition) DevFeed: [Open-Source Network Simulators (2026 Edition)]() Original publisher: [Read original article]() Published: 2026-02-10T07:09:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Open Source](), [Vagrant]() Tags: [also](), [netlab](), [network](), [open-source](), [vagrant](), [worth-reading]() ### AI overview The article highlights Brian Linkletter's updated overview of open-source network simulators and emulators. It identifies containerlab and GNS3 as leading options, notes that the original vrnetlab is abandoned, and discusses using netlab primarily with containerlab while gradually phasing out Vagrant support. ### Source excerpt Brian Linkletter published an updated overview of open-source network simulators and emulators. containerlab and GNS3 are clear leaders (no surprise there) with the original vrnetlab becoming abandonware (fortunately, we have Roman Dodin's fork), which makes me think we should focus on using netlab primarily with containerlab and slowly sunset the Vagrant support, particularly considering some people actively hate the license change. Also, if anyone feels like writing an interface (provider module) between netlab and GNS3, the pull request would be most welcome 😎 Read more ... ## Vagrant: entornos de desarrollo reproducibles DevFeed: [Vagrant: entornos de desarrollo reproducibles]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-06T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Vagrant](), [Oracle-VM-VirtualBox](), [Linux]() Tags: [ansible](), [hashicorp](), [rsync](), [ruby](), [snapshots](), [vagrant](), [virtualbox]() ### AI overview A Spanish tutorial explaining how Vagrant defines reproducible development environments as code. It covers installation, provider selection, Vagrantfile configuration, the VM lifecycle, SSH access, and synchronized folders, including performance and consistency considerations for VirtualBox, libvirt, NFS, and rsync. ### Source excerpt Vagrant con libvirt o VirtualBox: carpetas sincronizadas, snapshots, aprovisionamiento con Ansible y reload vs provision. ## Posts from the Past, October 2025 DevFeed: [Posts from the Past, October 2025]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2025-10-22T18:00:00Z Content type: article Language: en Sources: [Scott's Weblog]() Topics: [Amazon Elastic Kubernetes Service](), [Kubernetes](), [Amazon Web Services](), [Infrastructure as code](), [Azure]() Tags: [2025](), [amazon-elastic-kubernetes-service](), [ansible](), [aws](), [azure](), [cilium](), [cli](), [cloud](), [cni](), [containers](), [cri-o](), [devops](), [docker](), [go](), [iac](), [japan](), [k8s](), [kubernetes](), [kubernetes-clusters](), [linux](), [networking](), [oci](), [openstack](), [security](), [vagrant]() ### AI overview A retrospective roundup revisiting the author's Kubernetes, cloud infrastructure, and container-related posts published in October across several years. It highlights work involving Pulumi, Amazon EKS, Bottlerocket OS, Azure Kubernetes Service, Cluster API, AWS, kubeadm, Ansible, Vagrant, and OpenStack. ### Source excerpt Every now and then, I publish one of these "Posts from the Past" articles that looks back on content I've created and posted over the life of this site. This year marks 20 years of content--I can hardly believe it! Don't worry, though; you won't have to go through 20 years of past posts. Here is a selection of posts from mid- to late October over the last decade or so. I hope you find something useful, informative, or at least entertaining! October 2024 Last year I shared information on how to use Pulumi to stand up an Amazon Elastic Kubernetes Service (EKS) cluster with Bottlerocket OS on the Kubernetes nodes--without using any higher-level Pulumi components. October 2022 In 2022, after getting irritated with what I felt was a poor user experience when accessing Azure Kubernetes Service (AKS) clusters created with Pulumi, I published this post on how to change the Kubeconfig file for a more streamlined user experience. October 2021 Cluster API is the name of the game for multiple posts in October 2021. First I wrote this article on kustomize transformer configurations for Cluster API v1beta1 (so that you can use kustomize to manipulate Cluster API manifests), followed up later that month with an article on influencing Cluster API AMI selection. I also touched upon using the external (out of tree) cloud provider for AWS that month, a topic I am revisiting soon as I explore integrating Talos Linux with AWS. October 2020 More Cluster API content--this time discussing IaC considerations for Cluster API (think things like integrating workload clusters with existing AWS workloads or services). October 2019 In October 2019 I explored using jk to programmatically create Kubernetes manifests, and discussed how to use kustomize with kubeadm configuration files. October 2018 Plenty of articles discuss the use of kubeadm to bootstrap Kubernetes clusters (including a few I wrote!), but what of talking about using kubeadm to stand up an etcd cluster? I've got you covered! October 2 ## Molly-Guard: a Lifesaver on a Ubuntu Server DevFeed: [Molly-Guard: a Lifesaver on a Ubuntu Server]() Original publisher: [Read original article]() Published: 2025-07-02T06:18:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Ubuntu](), [Vagrant](), [Cisco](), [Open Source](), [Server](), [Command-line interface]() Tags: [cisco](), [networking](), [open-source](), [ssh](), [terminal](), [ubuntu](), [ubuntu-server](), [vagrant]() ### AI overview The author describes nearly powering off the wrong Ubuntu server instead of a Vagrant VM and recommends the molly-guard package. The package intercepts reboot-related commands during SSH sessions and asks for the target hostname. The article contrasts this safeguard with the lack of an equivalent mechanism on Cisco IOS devices. ### Source excerpt Have you ever managed to type reload in the wrong terminal window and brought down a core switch (I probably did)? I managed to do the Ubuntu equivalent of that stupidity: I told my main Ubuntu server to sudo poweroff instead of doing that to a Vagrant VM. Fortunately, the open-source world doesn't have to rely on the roadmaps created by networking vendors' product managers; if there's a big enough pain, someone will solve it. Read more ... ## netlab 2.0.0: Hosts, Bridges, and SRv6 DevFeed: [netlab 2.0.0: Hosts, Bridges, and SRv6]() Original publisher: [Read original article]() Published: 2025-05-12T07:05:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Release notes](), [releases](), [networking](), [SRv6](), [BGP](), [evpn](), [Firewall](), [Command-line interface](), [Routing (disambiguation)](), [Vagrant]() Tags: [2-0-0](), [bgp](), [cli](), [evpn](), [firewall](), [netlab](), [new-features](), [release](), [release-notes](), [routing](), [srv6](), [vagrant]() ### AI overview The article announces netlab 2.0.0 and summarizes new node roles, bridge support, a rudimentary firewall plugin, SRv6 BGP L3VPN support, a command-line defaults interface, routing and EVPN changes, graph styling, validation improvements, and platform or version changes. ### Source excerpt netlab release 2.0.0 is out. I spent the whole week fixing bugs and running integration tests, so I'm too brain-dead to go into the details. These are the major features we added (more about them in a few days; the details are in the release notes): Well-defined node roles (host, router, bridge) are now available on multiple platforms The firewall.zonebased plugin allows you to configure a rudimentary firewall SRv6: BGP L3VPN support is now available for FRRouting, so you can go out and kick its (free) tires. bridge nodes can be used as simple bridges or to implement multi-access links netlab defaults command provides sysctl-like CLI interface to user/system defaults. Other changes include: Read more ... ## Diagnosing MTU Mismatches Between QEMU TAP Interfaces and VM Network Devices DevFeed: [Diagnosing MTU Mismatches Between QEMU TAP Interfaces and VM Network Devices]() Original publisher: [Read original article]() Published: 2025-03-11T07:11:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Linux](), [qemu](), [networking](), [Vagrant](), [Operating system]() Tags: [article](), [connectivity](), [linux](), [networking](), [qemu](), [switching](), [vagrant](), [virtio](), [virtualization]() ### AI overview The article investigates asymmetric connectivity when oversized packets traverse two virtual machines connected through a Linux bridge. Packet captures show that QEMU does not adjust the Linux TAP interface MTU when a VM changes its virtual NIC MTU, creating an MTU mismatch that can prevent packets from reaching the outgoing interface. ### Source excerpt It all started with an innocuous article describing the MTU basics. As the real purpose of the MTU is to prevent packet drops due to fixed-size receiver buffers, and I waste spend most of my time in virtual labs, I wanted to check how various virtual network devices react to incoming oversized packets. As the first step, I created a simple netlab topology in which a single link had a slightly larger than usual MTU... and then all hell broke loose. Read more ... ## Goodbye, Cumulus Community Vagrant Boxes DevFeed: [Goodbye, Cumulus Community Vagrant Boxes]() Original publisher: [Read original article]() Published: 2025-02-19T07:01:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [Linux](), [VXLAN](), [Pull Request]() Tags: [ci](), [debugging](), [linux](), [netlab](), [nvidia](), [pull-request](), [release](), [ssh](), [vagrant](), [vxlan]() ### AI overview The article describes integration-test failures while reviewing a VXLAN on Cumulus Linux pull request. The failures were traced to Vagrant SSH authentication problems caused by password expiration in Cumulus Community virtual machines. It concludes that newer boxes remain affected, older boxes are outdated, and the Cumulus containers project is no longer maintained. ### Source excerpt Last Monday, I decided to review and merge the "VXLAN on Cumulus Linux 5.x with NVUE" pull request. I usually run integration tests on the modified code to catch any remaining gremlins, but this time, all the integration tests started failing during the VM creation phase. I was completely weirded out, considering everything worked a week ago. Fortunately, Vagrant debugging is pretty good1 and I was quickly able to pinpoint the issue (full printout): Read more ... ## Point-to-Point Links in Virtual Labs DevFeed: [Point-to-Point Links in Virtual Labs]() Original publisher: [Read original article]() Published: 2025-02-12T06:55:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [virtual machines](), [qemu](), [Vagrant](), [Containers](), [Linux](), [Command-line interface]() Tags: [blog-post](), [cli](), [container-networking](), [containers](), [linux](), [netlab](), [networking](), [qemu](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview This article explains how virtual labs connect virtual machines and Linux containers. It covers UDP tunnels used by KVM/QEMU/libvirt/Vagrant, point-to-point vEth links created by containerlab, and the packet-capture limitations of UDP tunnels. ### Source excerpt In the previous blog post, I described the usual mechanisms used to connect virtual machines or containers in a virtual lab, and the drawbacks of using Linux bridges to connect virtual network devices. In this blog post, we'll see how KVM/QEMU/libvirt/Vagrant use UDP tunnels to connect virtual machines, and how containerlab creates point-to-point vEth links between Linux containers. Read more ... ## Waiting for Network Device Interfaces During netlab Provisioning DevFeed: [Waiting for Network Device Interfaces During netlab Provisioning]() Original publisher: [Read original article]() Published: 2025-02-05T06:59:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [virtual machines](), [Containers](), [Vagrant](), [Ansible](), [qemu](), [ssh]() Tags: [ansible](), [cisco](), [containers](), [netlab](), [network](), [qemu](), [ssh](), [vagrant](), [virtual-machines]() ### AI overview The article explains why netlab must wait for network device interfaces to become operational after virtual machines and containers start. It describes readiness checks for SSH and interfaces, including differences in Cisco Nexus OS and Junos, and outlines how Ansible profiling is used to measure startup delays. ### Source excerpt Once a virtual machine running a network operating system boots, you'd expect its data-plane interfaces to be operational, right? Some vendors disagree. It takes over a minute for some network operating systems to figure out they have this thing called interfaces.1 I would love to figure out what takes them so long (a minute is an eternity on modern CPUs), but I guess we'll never know. Behind the Scenes netlab uses two device provisioning mechanisms: it can start virtual machines with Vagrant or containers with containerlab. Some of those containers might use KVM/QEMU to run a hidden virtual machine (see also: RFC 1925 rule 6a). Read more ... ## Links in Virtual Labs DevFeed: [Links in Virtual Labs]() Original publisher: [Read original article]() Published: 2025-02-03T07:27:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [virtualization](), [networking](), [Linux](), [virtual machines](), [Containers](), [Vagrant]() Tags: [containers](), [ethernet](), [links](), [linux](), [netlab](), [network](), [networks](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview This article explains how physical network links are represented in virtual labs. It examines virtual bridge switches, Linux bridges, Vagrant and libvirt networks, tap interfaces, and the veth-pair method for connecting containers to Linux bridges. ### Source excerpt There are three major ways to connect network devices in the physical world: Point-to-point links between devices (usually using some variant of Ethernet) Multi-access layer-1 networks running some IEEE 802.x encapsulation on top of that (GPON, WiFi, Ethernet hubs) Multi-access switched layer-2 network (dumb switches, hopefully running some STP variant) Implementing these connections in virtual labs is a bit harder than one might think, as all virtualization solutions assume you plan to run virtual servers connected to Ethernet segments. Read more ... ## How Does Netlab Deal with Server Reboots? DevFeed: [How Does Netlab Deal with Server Reboots?]() Original publisher: [Read original article]() Published: 2024-10-24T06:15:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Command-line interface](), [Orchestration](), [Vagrant](), [virtual machines](), [Containers](), [Linux]() Tags: [cleanup](), [cli](), [config](), [containers](), [linux](), [netlab](), [orchestration](), [server](), [vagrant](), [virtual-machines]() ### AI overview The article explains that netlab does not automatically recover labs after server reboots, power failures, or crashes because it runs as a CLI rather than a boot-time service. It describes clearing stale locks, restarting virtual-machine labs with snapshot and no-config options, and the more limited recovery options for containers. ### Source excerpt Now and then, someone asks how netlab deals with reboots (or power failures or crashes) of the server it's running on. TL&DR: It doesn't. However... netlab is a CLI command that acts as an umbrella orchestration layer for Vagrant and Containerlab. It does not run as a cron job, init script, or service and thus cannot be invoked when a server is booted. Read more ... ## Building Layer-3-Only EVPN Lab DevFeed: [Building Layer-3-Only EVPN Lab]() Original publisher: [Read original article]() Published: 2024-08-08T06:38:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [evpn](), [VXLAN](), [BGP](), [Linux]() Tags: [bgp](), [containers](), [evpn](), [linux](), [netlab](), [ospf](), [vagrant](), [vxlan]() ### AI overview A hands-on guide to building a layer-3-only EVPN lab with netlab. The lab uses Arista cEOS containers, two switches, two VRFs, four Linux hosts, OSPF, BGP, VXLAN, and EVPN, with instructions for using other supported devices. ### Source excerpt A few weeks ago, Roman Dodin mentioned layer-3-only EVPNs: a layer-3 VPN design with no stretched VLANs in which EVPN is used to transport VRF IP prefixes. The reality is a bit muddier (in the VXLAN world) as we still need transit VLANs and router MAC addresses; the best way to explore what's going on behind the scenes is to build a simple lab. Read more ... ## netlab 1.8.2: Bug Fixes, Usability Improvements DevFeed: [netlab 1.8.2: Bug Fixes, Usability Improvements]() Original publisher: [Read original article]() Published: 2024-05-14T06:01:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [bug](), [Usability](), [configuration](), [Vagrant](), [Docker](), [Ansible](), [Containers]() Tags: [ansible](), [bug](), [bug-fixes](), [configuration](), [containers](), [docker](), [netlab](), [release-notes](), [usability](), [vagrant]() ### AI overview netlab 1.8.2 includes bug fixes, usability improvements, minor changes to device configuration templates, and safeguards for Vagrant boxes, Docker containers, Ansible collections, and modified lab topologies. It also adds minimal Sonic support based on Azure VM images. ### Source excerpt netlab release 1.8.2 contains dozens of bug fixes and minor tweaks to device configuration templates. We also added a few safeguards including: Check for Vagrant boxes or Docker containers before starting the lab and display pointers to build recipes. Check installed Ansible collections before trying to configure the lab devices. Display a warning if the lab topology was modified after the lab was created Read more ... ## Networking Virtual Machines and Containers Must Work Reliably Out of the Box DevFeed: [Networking Virtual Machines and Containers Must Work Reliably Out of the Box]() Original publisher: [Read original article]() Published: 2024-05-06T06:25:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [virtual machines](), [DHCP](), [Vagrant](), [dell]() Tags: [cisco](), [dell](), [dhcp](), [netlab](), [network](), [networking](), [ssh](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview The article argues that free network operating system images distributed as containers or virtual machines must work reliably out of the box. It describes Junos vPTX rejecting DHCP-assigned addresses and Dell OS10 images having intermittent SSH server failures that make automation and CI/CD use impractical. ### Source excerpt Some networking vendors realized that one way to gain mindshare is to make their network operating systems available as free-to-download containers or virtual machines. That's the right way to go; I love their efforts and point out who went down that path whenever possible1 (as well as others like Cisco who try to make our lives miserable). However, those virtual machines better work out of the box, or you'll get frustrated engineers who will give up and never touch your warez again, or as someone said in a LinkedIn comment to my blog post describing how Junos vPTX consistently rejects its DHCP-assigned IP address: "If I had encountered an issue like this before seeing Ivan's post, I would have definitely concluded that I am doing it wrong."2 Read more ... ## Using netlab to Build Virtual VXLAN and EVPN Labs DevFeed: [Using netlab to Build Virtual VXLAN and EVPN Labs]() Original publisher: [Read original article]() Published: 2024-02-27T12:00:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [VXLAN](), [networking](), [BGP](), [evpn](), [Orchestration](), [IP routing]() Tags: [aws](), [bgp](), [building](), [cloud](), [container](), [containers](), [evpn](), [linux](), [netlab](), [networking](), [orchestration](), [ospf](), [protocol](), [routing](), [vagrant](), [virtual-machine-images](), [vxlan]() ### AI overview The article explains how netlab can automate the construction and configuration of virtual labs for learning VXLAN and EVPN. It covers supported platforms, routing protocols, device images, and cloud instance options. ### Source excerpt I stumbled upon an "I want to dive deep into VXLAN and plan to build a virtual lab" discussion on LinkedIn1. Of course, I suggested using netlab. After all, you have to build an IP core and VLAN access networks and connect a few clients to those access networks before you can start playing with VXLAN, and those things tend to be excruciatingly dull. Now imagine you decide to use netlab. Out of the box, you get topology management, lab orchestration, IPAM, routing protocol design (OSPF, BGP, and IS-IS), and device configurations, including IP routing and VLANs. Read more ... ## CloudFormation vs. Terraform DevFeed: [CloudFormation vs. Terraform]() Original publisher: [Read original article]() Author: Wojtek Gawroński (afronski) Published: 2017-04-11T08:00:00Z Content type: comparison Language: en Sources: [Wojtek Gawroński]() Topics: [Terraform](), [AWS CloudFormation](), [Amazon Web Services](), [Infrastructure as code](), [vendor lock-in](), [Disaster Recovery]() Tags: [aws](), [aws-cloudformation](), [c-sharp](), [canvas](), [clojure](), [css](), [css3](), [disaster-recovery](), [erlang](), [html](), [html5](), [infrastructure-as-code](), [javascript](), [mono](), [net](), [node-js](), [sicp](), [terraform](), [vagrant](), [vendor-lock-in](), [webgl]() ### AI overview This comparison examines Terraform and AWS CloudFormation for automating cloud infrastructure. The author explains the decision to use a pure CloudFormation setup, choose AWS, and drop Terraform, while discussing provider dependence, vendor lock-in, and disaster recovery considerations. ### Source excerpt CloudFormation vs. Terraform. a There is a time when every project that uses a cloud computing service has a difficult choice to make - should we automate the infrastructure or not? Immediately after, another question pops up - how should we do it? Should we use a dedicated tool (AWS CloudFormation, Azure Resource Templates, OpenStack Heat or Google Cloud Deployment Manager) or a provider-agnostic solution? And then - immediately after a surprise comes in - at first glance, there is no other tool like Terraform available on the market (but there is - it is called Foreman :wink:). So we have a good tool, built by amazing people (HashiCorp) which does not rely on any particular cloud - problem solved? Not entirely. As a grown up, you know that like the ORM does not let you change database on the fly, Terraform will not let you automatically switch your cloud provider for your entire system. From the other hand - you fear vendor lock-in, and for sure you are considering how to design and prepare disaster recovery scenarios. A lot of unknowns, isn't it? I would like to show my rationale for a new project and infrastructure for which I, among others, was responsible. The motivation which drove us towards a pure CloudFormation setup, the reason behind our bet on AWS, and the motivation behind the decision to drop Terraform. Keep in mind that all remarks and comments pointed in this article are constructive criticism - it does not change my opinion about companies that created those tools at all. I have huge respect for both for AWS and HashiCorp - the work they have done, especially in tooling and cloud computing landscape is outstanding. As a user of AWS Services and HashiCorp tools I am grateful for the work they did. If you do not have experience with CloudFormation or Terraform - please read either amazing documentation or any other introductory article. I will assume your basic knowledge about these two. Terraform is not a silver bullet. When I evaluated Terraform, i ## Local Development with Vagrant / Homestead DevFeed: [Local Development with Vagrant / Homestead]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-03-31T07:59:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Vagrant](), [Provisioning](), [Web Development](), [Linux](), [Tooling](), [Software Engineering]() Tags: [allows](), [debugging](), [debugging-tools](), [development](), [effectively](), [environment](), [homestead](), [insights](), [linux](), [local](), [modern-web-development](), [projects](), [provisioning](), [safely](), [vagrant](), [vagrant-homestead](), [work]() ### AI overview This tutorial explains how Vagrant/Homestead provides a separate virtual machine for local web development. It discusses safer project workflows, isolated environments, production-like Linux systems, and pre-installed development and debugging tools. ### Source excerpt A local development environment with Vagrant/Homestead allows you to work on projects more safely and effectively ## Using PhpStorm with Vagrant / Homestead DevFeed: [Using PhpStorm with Vagrant / Homestead]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-01-10T22:13:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [phpstorm](), [Vagrant](), [ide](), [PHP](), [Tutorial](), [Content Management System](), [Front end](), [debug]() Tags: [craft](), [dev](), [here-s](), [homestead](), [how-to](), [insights](), [local](), [php](), [phpstorm](), [setup](), [tutorial](), [vagrant](), [vagrant-homestead](), [xdebug]() ### AI overview A tutorial on setting up PhpStorm with Vagrant/Homestead for local PHP development, including guidance for working with Craft CMS and Xdebug. It covers opening an existing project and configuring PhpStorm to use Vagrant. ### Source excerpt Here's how to set up PhpStorm with Vagrant / Homestead for local dev with Xdebug for Craft CMS or other PHP dev ## How V8's compilation cache supports function inlining DevFeed: [How V8's compilation cache supports function inlining]() Original publisher: [Read original article]() Author: Wojtek Gawroński (afronski) Published: 2016-04-08T17:45:00Z Content type: article Language: en Sources: [Wojtek Gawroński]() Topics: [Compiler](), [V8](), [JavaScript](), [JIT](), [Optimization](), [Node.js]() Tags: [article](), [c-sharp](), [cache](), [canvas](), [clojure](), [compilation](), [compiler](), [css](), [css3](), [erlang](), [html](), [html5](), [inlining](), [javascript](), [mono](), [net](), [node-js](), [optimization](), [sicp](), [v8](), [vagrant](), [webgl]() ### AI overview This article explains why just-in-time compilation in V8 is difficult for JavaScript and discusses compilation caching as an optimization technique related to function inlining. It distinguishes compilation caches from inline caches. ### Source excerpt A mythical beast called JIT I have recently bumped into one of those articles which title sounds rather like "one weird trick" ad. Guiding just from it, you can imagine how small amount of information is contained there, and by actually going through that link there you will definitely make sure that it has some knowledge, but no real explanations are in place. Of course, a final explanation is indeed really simple - Function.prototype.toString() returns everything even the comments inside the function body, size of that string is a feature that allows the optimizing compiler inside V8 to make a decision to inline that particular function or not. There is even a command line switch which to use to modify a limit and a default value. Simple enough? Not really. That article left a lot of unanswered questions. Probably because of that JIT compilers and its optimization techniques are kind of black magic. Why is it hard? Obviously compiler engineers are not dumb people (they are actually really smart) and they are not obfuscating and complicating this by accident or on purpose. They are working hard, especially with such weakly typed and underspecified languages like JavaScript to provide you an optimized version of your code. Why is it a hard job? It is all about guarantees. How many of them you can recall from memory when it comes to JavaScript? Not a lot of them, right? That is not good, especially from the perspective of a compiler engineer. JavaScript is everywhere, success of the internet spread this language, and nowadays success of Node.js pushed this language from front-end, even to server-side - and everywhere people are talking about performance. Obviously not about native like performance for scientific computations, but the more complexity is pushed to the application layer, the more of it will have to be optimized after all. That's why compilers and their creators have to be smart people - they have to deal with complexity of your applications and "illness ## Jenkins 2.0 DevFeed: [Jenkins 2.0]() Original publisher: [Read original article]() Author: Wojtek Gawroński (afronski) Published: 2016-04-03T15:30:00Z Content type: release Language: en Sources: [Wojtek Gawroński]() Topics: [Jenkins](), [Automation](), [Open Source]() Tags: [automation](), [c-sharp](), [canvas](), [clojure](), [compatibility](), [css](), [css3](), [erlang](), [html](), [html5](), [javascript](), [jenkins](), [mono](), [net](), [node-js](), [open-source](), [release](), [sicp](), [vagrant](), [webgl]() ### AI overview This article reviews the beta release of Jenkins 2.0, covering its improved user interface, built-in delivery pipelines with Jenkinsfile support, and stated backward compatibility with Jenkins 1.x. It notes that the current LTS version remained recommended for production deployments at the time. ### Source excerpt Jenkins 2.0 Introduction Recently maintainers of Jenkins - the leading and most popular open source automation server - announced that long awaited version 2.0 is available to download and additionally it is marked as a beta release. It means that they're still recommending current LTS version for a production deployments, but new version is coming really soon. So let's look what it offers! What's new? Improved usability (aka "New UI") That is probably the most single awaited feature in Jenkins community. It means a lot for both, power users and newcomers. A lot of feedback was taken into account when preparing that feature. Old pages (e.g. Create Item or Job Configuration) look really clean and modern (we finally have tabs in Job Configuration page), new views like Pipeline Stage view (we will describe whole feature in the next section) look even more awesome: But that's not the end of goodies from that release. Delivery pipelines Finally Jenkins will be packaged with built-in delivery pipelines feature. It means that it will not require anymore plugins for doing that. It brings finally support for Jenkinsfile - concept which allows to codify your pipelines, and store it inside version control (either together with application source code or outside, in one of your supporting repositories). Besides that - finally no more XML fiddling when it comes to job configuration, because it will use a nice DSL: node { git url: 'https://github.com/joe_user/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' sh "${mvnHome}/bin/mvn -B -Dmaven.test.failure.ignore verify" step([$class: 'ArtifactArchiver', artifacts: '**/target/*.jar', fingerprint: true]) step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml']) } That is a well known concept, similar to the job DSL plugin. But finally, it will be built-in and ready to use right after installation, without any additional effort. Full backward compatibility That is the most important thing [Next page]()