Vagrant and VirtualBox
This document describes how to install and set up Cumulus Linux within a Vagrant environment, using VirtualBox as the hypervisor.
Configure the Vagrant Environment
This section assumes that you have installed the VirtualBox hypervisor. For detailed instructions, refer to the VirtualBox installation section.
Cumulus VX requires Vagrant version 1.7 or later. The installation steps below use Vagrant version 1.9.4 for the example commands.
To set up the Vagrant environment:
Download and install Vagrant: Vagrant Downloads.
In a terminal, add the Cumulus VX Vagrant box image. Ensure option
Vagrant downloads and installs the latest Cumulus VX VirtualBox image.
local@host:~$ vagrant box add cumuluscommunity/cumulus-vx ==> box: Loading metadata for box 'cumuluscommunity/cumulus-vx' box: URL: https://atlas.hashicorp.com/cumuluscommunity/cumulus-vx This box can work with multiple providers! The providers that it can work with are listed below. Please review the list and choose the provider you will be working with. 1) libvirt 2) virtualbox Enter your choice: 2 ==> box: Adding box 'CumulusCommunity/cumulus-vx' (v3.3.0) for provider: virtual box ...
Cumulus Networks provides several preconfigured demos to run with Vagrant using Ansible to configure the VMs. To run these demos, download and install Ansible 1.7 or newer.
Configure a Cumulus VX VM with Vagrant
In a terminal, create a folder to contain the Vagrant environment, then change directories into that folder.
local@host:~$ mkdir vagrant local@host:~$ cd vagrant
Initialize the Vagrant environment so you can provision your VMs. This creates a file called
Vagrantfilewithin the folder you just created.
local@host:~/vagrant$ vagrant init
Configure Vagrant to spin up a Cumulus VX VM. Modify the newly created
Vagrantfileto configure the VMs, then save the file:
local@host:~/vagrant$ sudo vi Vagrantfile Vagrant.configure(2) do |config| config.vm.box = "CumulusCommunity/cumulus-vx" end
Cumulus VX 3.y.z images require at least 512MB to be fully functional. The default Vagrant memory size is 512MB. If performance issues exist, increase the amount of memory by setting the
v.memoryvariable in the
Vagrantfileto 512 or more. You can also adjust the memory size in the VirtualBox UI when the VM is powered off.
vagrant upto start the VM:
local@host:~/vagrant$ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'cumulus-vx-3.3.0'... ==> default: Matching MAC address for NAT networking... ==> default: Setting the name of the VM: temp_default_1437562573479_23184 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 22 => 2222 (adapter 1) ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key default: Warning: Connection timeout. Retrying... default: default: Vagrant insecure key detected. Vagrant will automatically replace default: this with a newly generated keypair for better security. default: default: Inserting generated public key within guest... default: Removing insecure key from the guest if it's present... default: Key inserted! Disconnecting and reconnecting using new SSH key... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... ==> default: Mounting shared folders... default: /vagrant => /Users/cumulus/vx-example
After you start a VM, you can log in using the
local@host:~/vagrant$ vagrant ssh
vagrant ssh command logs in as the preconfigured
vagrant user. A
shared file system is automatically mounted inside the VM under the
/vagrant mount point; you can transfer files between the host and
Cumulus VX instance from there.
To shut down the VM, use the
local@host:~/vagrant$ vagrant destroy
For more information on configuring VMs with Vagrant, see docs.vagrantup.com/v2/.
You can explore the various demos available as part of the cldemo-vagrant family of repositories located here.
Additional Configuration Options
Add Switch Port Interfaces to a Cumulus VX VM
By default Vagrant only configures the first network interface (eth0)
for its own use. You must configure additional network interfaces, such
as the Cumulus Linux switch port interfaces, in the
Normally, you configure these interfaces to use a private network. By
default, Vagrant provides one preconfigured private network, although
you can choose to create additional private networks. You can connect
one or more network interfaces to a private network.
The following example creates a Cumulus VX VM where the interfaces swp1 through swp4 are created and connected to the preconfigured private network:
Vagrant.configure(2) do |config| config.vm.box = "CumulusCommunity/cumulus-vx" config.vm.network "private_network", virtualbox__intnet: "swp1", auto_config: false config.vm.network "private_network", virtualbox__intnet: "swp2", auto_config: false config.vm.network "private_network", virtualbox__intnet: "swp3", auto_config: false config.vm.network "private_network", virtualbox__intnet: "swp4", auto_config: false end
For more information on creating and using private networks, see docs.vagrantup.com/v2/networking/private_network.html and docs.vagrantup.com/v2/virtualbox/networking.html.
Create Multiple Cumulus VX VMs
Vagrant can create and configure multiple VMs with a single command. For example, you can use Vagrant to create multiple Cumulus VX VMs and then connect the network interfaces of those VMs together.
The following example creates two Cumulus VX VMs, leaf1 and leaf2, where the interfaces swp1 through swp4 are connected together via separate private networks:
Vagrant.configure(2) do |config| config.vm.define "leaf1" do |leaf1| leaf1.vm.box = "CumulusCommunity/cumulus-vx" # Internal network for swp* interfaces. leaf1.vm.network "private_network", virtualbox__intnet: "swp1", auto_config: false leaf1.vm.network "private_network", virtualbox__intnet: "swp2", auto_config: false leaf1.vm.network "private_network", virtualbox__intnet: "swp3", auto_config: false leaf1.vm.network "private_network", virtualbox__intnet: "swp4", auto_config: false end config.vm.define "leaf2" do |leaf2| leaf2.vm.box = "CumulusCommunity/cumulus-vx" # Internal network for swp* interfaces. leaf2.vm.network "private_network", virtualbox__intnet: "swp1", auto_config: false leaf2.vm.network "private_network", virtualbox__intnet: "swp2", auto_config: false leaf2.vm.network "private_network", virtualbox__intnet: "swp3", auto_config: false leaf2.vm.network "private_network", virtualbox__intnet: "swp4", auto_config: false end end
When you run
vagrant up, both VMs are created. You can log in to each
VM and configure the interfaces as you want; the interfaces will pass
traffic between themselves as if they are two physical switches
connected together by four cables.
At this time, there are some limitations to using Vagrant with Cumulus VX:
- VirtualBox can only support a maximum of 36 network interfaces.
- The first network interface (eth0) is always managed by Vagrant and must be connected to a NAT network.
Cumulus VX for Vagrant has been tested in the following environments:
|Host OS||Vagrant Version(s)||VirtualBox Version(s)||Notes|
|OS X 10.10||1.7.3|
|Windows 7||1.7.3||5.0||While both VirtualBox and Vagrant are fully supported on Windows hosts, Vagrant provisioning with Ansible is not.
Cumulus VX demos that use Ansible do not work on Windows.