koding / vagrantutil

A toolset to manage Vagrant boxes in Go

Vagrantutil

Vagrantutil is a toolset for managing Vagrant boxes via an idiomatic Go (Golang) API. The package is work in progress, so please vendor it. Checkout the examples below for the usage.

Install

go get github.com/koding/vagrantutil

Usage and Examples

package main

import (
	"log"

	"github.com/koding/vagrantutil"
)

func main() {
	vagrant, _ := vagrantutil.NewVagrant("myfolder")

	vagrant.Create(`# -*- mode: ruby -*-
# vi: set ft=ruby :

VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = "ubuntu/trusty64"
  config.vm.hostname = "vagrant"

  config.vm.provider "virtualbox" do |vb|
    # Use VBoxManage to customize the VM. For example to change memory:
    vb.customize ["modifyvm", :id, "--memory", "2048", "--cpus", "2"]
  end
end
`)

	status, _ := vagrant.Status() // prints "NotCreated"

	// starts the box
	output, _ := vagrant.Up()

	// print the output
	for line := range output {
		log.Println(line)
	}

	// stop/halt the box
	vagrant.Halt()

	// destroy the box
	vagrant.Destroy()
}

vagrantutil's Issues

vagrantutil: queue box builds

Having concurrent vagrant up does not work for all the boxes, especially those which use bridge networking, as VirtualBox commands executed conflict with each other.

VagrantUp implementation should queue all the builds and provide API for getting state.

This fixes the following failures:

2016-11-18T08:48:38.549Z DEBUG    [vagrantutil    ][PID:24168][logging/context.go:53] [/Users/rjeczalik/.vagrant.d/koding/team/urtv907ed4f2] An action 'up' was attempted on the machine 'default',
2016-11-18T08:48:38.549Z DEBUG    [vagrantutil    ][PID:24168][logging/context.go:53] [/Users/rjeczalik/.vagrant.d/koding/team/urtv907ed4f2] but another process is already executing an action on the machine.
2016-11-18T08:48:38.549Z DEBUG    [vagrantutil    ][PID:24168][logging/context.go:53] [/Users/rjeczalik/.vagrant.d/koding/team/urtv907ed4f2] Vagrant locks each machine for access by only one process at a time.
2016-11-18T08:48:38.55Z  DEBUG    [vagrantutil    ][PID:24168][logging/context.go:53] [/Users/rjeczalik/.vagrant.d/koding/team/urtv907ed4f2] Please wait until the other Vagrant process finishes modifying this
2016-11-18T08:48:38.55Z  DEBUG    [vagrantutil    ][PID:24168][logging/context.go:53] [/Users/rjeczalik/.vagrant.d/koding/team/urtv907ed4f2] machine, then try again.

vagrantutil: vagrant up fails if vbox kernel is misconfigured

Handle VirtualBox errors on VagrantUp.

Example log:

2016-07-27T11:35:12.514Z DEBUG    [vagrantutil    ][PID:1047][logging/context.go:53] [/home/rjeczalik/.vagrant.d/koding/team/urtvc32efb2a] VirtualBox is complaining that the kernel module is not loaded. Please
2016-07-27T11:35:12.515Z DEBUG    [vagrantutil    ][PID:1047][logging/context.go:53] [/home/rjeczalik/.vagrant.d/koding/team/urtvc32efb2a] run `VBoxManage --version` or open the VirtualBox GUI to see the error
2016-07-27T11:35:12.515Z DEBUG    [vagrantutil    ][PID:1047][logging/context.go:53] [/home/rjeczalik/.vagrant.d/koding/team/urtvc32efb2a] message which should contain instructions on how to fix this error.
2016-07-27T11:35:12.53Z  DEBUG    [vagrantutil    ][PID:1047][logging/context.go:53] [/home/rjeczalik/.vagrant.d/koding/team/urtvc32efb2a] reporting error for [vagrant up]: exit status 1 (false)
2016-07-27T11:35:12.53Z  DEBUG    [vagrantutil    ][PID:1047][logging/context.go:53] [/home/rjeczalik/.vagrant.d/koding/team/urtvc32efb2a] execution of [vagrant up] failed: exit status 1