Over a million developers have joined DZone.

Vagrant: Multi (Virtual) Machine with Puppet Roles

· DevOps Zone

The DevOps zone is brought to you in partnership with Sonatype Nexus. The Nexus suite helps scale your DevOps delivery with continuous component intelligence integrated into development tools, including Eclipse, IntelliJ, Jenkins, Bamboo, SonarQube and more. Schedule a demo today

I’ve been playing around with setting up a neo4j cluster using Vagrant and HAProxy and one thing I wanted to do was define two different roles for the HAProxy and neo4j machines.

When I was working at uSwitch Nathan had solved a similar problem, but with AWS VMs, by defining the role in an environment variable in the VM’s spin up script.

In retrospect I think I might have been able to do that by using the shell provisioner and calling that before the puppet provisioner but Nathan, Gareth Rushgrove and Gregor Russbuelt suggested that using facter might be better.

When I initially looked at the ‘Custom Facts’ section of the docs I thought it was only possible to set facts for the Vagrant file as a whole but you can actually do it on a per VM basis which is neat.

I added a method called ‘provision_as_role’ to the ‘Vagrant::Config::V2::Root’ class:

module Vagrant
  module Config
    module V2
      class Root
        def provision_as_role(role)
          vm.provision :puppet do |puppet|
            puppet.manifests_path = "puppet/manifests"
            puppet.module_path = "puppet/modules"
            puppet.manifest_file  = "base.pp"
            puppet.facter = { "role" => role.to_s }

and then passed in a role depending on the VM in my Vagrantfile:

require File.join(File.dirname(__FILE__), 'lib', 'root.rb')
Vagrant.configure("2") do |config|  
  config.vm.box = "precise64"
  config.vm.box_url = "http://files.vagrantup.com/precise64.box"
  config.vm.define :neo01 do |neo| 
    neo.vm.hostname = "neo01"
    neo.vm.network :private_network, ip: ""    
    neo.provision_as_role :neo
  config.vm.define :lb01 do |lb|
    lb.vm.hostname = "lb01"
    lb.vm.network :private_network, ip: ""    
    lb.provision_as_role :lb

We can now access the variable ‘$role’ in our puppet code which I used like so:


class all_the_things {
  exec { 'apt-get update': command => '/usr/bin/apt-get update'; }
  package { 'curl': ensure => '7.22.0-3ubuntu4', }
  class { 'apt': }
node default {
  class { 'all_the_things': }
  class { $role:
    require => Class['all_the_things']

The ‘neo’ and ‘lb’ classes look like this:

class neo {
  class { 'java': version => '7u25-0~webupd8~1', }
  class { 'neo4j': require     => Class['java'], }

class lb {
  class { 'haproxy':  }

The full code is on github but it’s behaving a bit weirdly in some scenarios so I’m still trying to get it properly working.

The DevOps zone is brought to you in partnership with Sonatype Nexus. Use the Nexus Suite to automate your software supply chain and ensure you're using the highest quality open source components at every step of the development lifecycle. Get Nexus today


Published at DZone with permission of Mark Needham, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}