Define a second node in the Vagrantfile. We'll make sure that this second node can access the Puppetmaster as Puppet by adding a fixed IP for the Puppetmaster and creating an /etc/hosts/ entry that allows our new node to access the Puppetmaster at the default address of Puppet. A complete Vagrantfile with both nodes looks like this:

# -*- mode: ruby -*-
# vi: set ft=ruby :
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"
$puppetmaster_ip = "192.168.30.134"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "puppetlabs/ubuntu-14.04-64-puppet"
  config.vm.define "puppetmaster" do |puppetmaster|
    puppetmaster.vm.hostname = "puppet"
    puppetmaster.vm.network "private_network", ip: $puppetmaster_ip
    puppetmaster.vm.provision "shell" , inline: "apt-get update"
    puppetmaster.vm.provision "puppet"  do |puppet|
      puppet.manifests_path = "puppet/manifests"
      puppet.manifest_file  = "site.pp"
      puppet.module_path    = "puppet/modules"
    end
  end
  config.vm.define "web01" do |web|
    web.vm.hostname = "web01"
    web.vm.provision "shell", inline: "apt-get update"
    web.vm.provision "shell", inline: "echo '#{$puppetmaster_ip} puppet puppet.localdomain' >> /etc/hosts"
  end
end

This defines our second node as web01.

Start the node with the vagrant up web01 command.

SSH into the web01 node with the vagrant ssh web01 command.

In the web01 node, start the Puppet agent with the sudo puppet agent –t command. This will start the Puppet agent and quickly return an error as our Puppetmaster has not yet been configured to compile a catalog for web nodes.

Define a web node by editing the puppet/manifests/site.pp file (the Puppetmaster manifest file) in our working directory. We'll make this simple for now: simply install the Apache web server package. In this case, being Ubuntu only for now. The additional node looks like this:

node /^web/ {
  package{"apache2": ensure => installed,}
}

Configure the Vagrant Puppet agent provisioner in the Vagrantfile. Add a provisioning block to the web01 machine definition:

    web.vm.provision "puppet_server" do |puppet|
      puppet.puppet_server = "puppet"
    end

This will start the Puppet agent using the machine name puppet to retrieve a catalog. It would also be possible to use the IP address of the Puppetmaster itself, but having the definition of the IP address in the /etc/hosts file allows the Puppet agent to run independently of Vagrant provisioners if desired.

Run the Puppet server provisioner with the vagrant provision web01 command. This will produce provisioner output that ends in a notification that the Puppet agent is running:

==> web01: Running provisioner: puppet_server...
==> web01: Running Puppet agent...

Log in to the web server (vagrant ssh web01) and verify that the apache2 package has been installed:

vagrant@web01:~$ which apache2
/usr/sbin/apache2

The results of the Puppet run can also be verified through report creation on the node at /var/lib/puppet/state/last_run_report.yaml or any configured reporting on the Puppetmaster.