Skip to content

Instantly share code, notes, and snippets.

@chaseconey

chaseconey/ vagrant.md

Last active December 19, 2015 17:38
Show Gist options
  • Save chaseconey/5992213 to your computer and use it in GitHub Desktop.
Save chaseconey/5992213 to your computer and use it in GitHub Desktop.
Download ZIP
Vagrant installation and use
Raw
vagrant.md

Vagrant Installation

Get software

Create structure

Make a new directory wherever you want to store your virtual machine and initialize it

    mkdir ~/vm
    vagrant init precise32

This will give you a fresh Vagrantfile that you can configure to your needs. The main things that you will want to do is allow port forwarding and add puppet as the provisioning tools to use. Here is what the file will look like after that:

    # -*- mode: ruby -*-
    # vi: set ft=ruby :
    
    Vagrant.configure("2") do |config|
      # All Vagrant configuration is done here. The most common configuration
      # options are documented and commented below. For a complete reference,
      # please see the online documentation at vagrantup.com.
    
      # Every Vagrant virtual environment requires a box to build off of.
      config.vm.box = "precise32"
    
      config.vm.provision :puppet do |puppet|
        puppet.module_path = "/home/chase/.puppet/modules"
      end
      
      # Create a forwarded port mapping which allows access to a specific port
      # within the machine from a port on the host machine. In the example below,
      # accessing "localhost:8080" will access port 80 on the guest machine.
      config.vm.network :forwarded_port, guest: 80, host: 8080
    
      # Share an additional folder to the guest VM. The first argument is
      # the path on the host to the actual folder. The second argument is
      # the path on the guest to mount the folder. And the optional third
      # argument is a set of non-required options.
      config.vm.synced_folder "../data", "/vagrant_data"
    end

Puppet config

  • Now we can store all of our provisioning information in the manifests directory.
  • By default, vagrant will look at the manifests/default.pp file and run everything there on creation/startup.
  • Here we can define pacakges, services, files, etc...
  • See attached for self-created puppet config and one that uses puppetlabs/apache as well

Using pre-built puppet modules

  • If we want to use pre-built puppet modules seen here, we must create a local directory that will hold pacakges locally that will be installed to the VM.
    mkdir ~/.puppet/modules
    puppet module install puppetlabs/apache
  • This will install the package to our ~/.puppet/modules directory
  • You can see that we specified this directory in the Vagrantfile so that it knows where these packages live

Configuring apache classes

  • Now we can just configure the apache, vhost, exec, php, and other relevent config items in our default.pp.
Raw
default.pp
class { 'apache':
mpm_module => 'prefork',
default_vhost => false,
}
Exec {
path => ["/usr/bin", "/usr/local/bin"],
}
exec { "update":
command => "apt-get update"
}
class { "apache::mod::php" :
require => Exec["update"]
}
apache::vhost { 'personal-site':
port => '80',
docroot => '/vagrant',
}
file { "/vagrant/index.php":
content => "The date is <?php echo date('Y-m-d')?>"
}
Raw
Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
# All Vagrant configuration is done here. The most common configuration
# options are documented and commented below. For a complete reference,
# please see the online documentation at vagrantup.com.
# Every Vagrant virtual environment requires a box to build off of.
config.vm.box = "precise32"
config.vm.provision :puppet do |puppet|
puppet.module_path = "/home/chase/.puppet/modules"
end
# The url from where the 'config.vm.box' box will be fetched if it
# doesn't already exist on the user's system.
# config.vm.box_url = "http://domain.com/path/to/above.box"
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
config.vm.network :forwarded_port, guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network :private_network, ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network :public_network
# If true, then any SSH connections made will enable agent forwarding.
# Default value: false
# config.ssh.forward_agent = true
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider :virtualbox do |vb|
# # Don't boot with headless mode
# vb.gui = true
#
# # Use VBoxManage to customize the VM. For example to change memory:
# vb.customize ["modifyvm", :id, "--memory", "1024"]
# end
#
# View the documentation for the provider you're using for more
# information on available options.
# Enable provisioning with Puppet stand alone. Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file precise32.pp in the manifests_path directory.
#
# An example Puppet manifest to provision the message of the day:
#
# # group { "puppet":
# # ensure => "present",
# # }
# #
# # File { owner => 0, group => 0, mode => 0644 }
# #
# # file { '/etc/motd':
# # content => "Welcome to your Vagrant-built virtual machine!
# # Managed by Puppet.\n"
# # }
#
# config.vm.provision :puppet do |puppet|
# puppet.manifests_path = "manifests"
# puppet.manifest_file = "init.pp"
# end
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
# config.vm.provision :chef_solo do |chef|
# chef.cookbooks_path = "../my-recipes/cookbooks"
# chef.roles_path = "../my-recipes/roles"
# chef.data_bags_path = "../my-recipes/data_bags"
# chef.add_recipe "mysql"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
# end
# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision :chef_client do |chef|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
# chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# If you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
# chef.validation_client_name = "ORGNAME-validator"
end
Raw
webserver.pp
class webserver {
package { 'apache2':
ensure => 'installed',
}
file { 'site-config':
path => "/etc/apache2/sites-enabled/000-default",
source => "/vagrant/site-config",
require => Package["apache2"],
}
service { 'apache2':
ensure => 'running',
hasrestart => true,
subscribe => File["site-config"],
}
file { '/vagrant/index.html':
content => "<h1> Vagrant + Puppet </h1>"
}
package { 'vim':
ensure => 'installed',
}
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment