Vagrantfile.example

# -*- mode: ruby -*-
# vi: set ft=ruby :


Vagrant.configure("2") do |config|
  config.vm.box = "dummy"

  config.vm.provider "brightbox" do |brightbox|
    brightbox.client_id = "cli-xxxxx"
    brightbox.secret = "abc123"
    brightbox.ssh_username = "ubuntu"
    brightbox.ssh_private_key_path = "/home/here/.ssh/id_rsa"
    brightbox.image_id = "img-77j4h"
    #brightbox.auth_url = "https://api.gb1.brightbox.com"
    #brightbox.api_url = brightbox.auth_url
    #brightbox.region = "gb1"
  end

  # By default the Brightbox provider maps a cloud ip to each server
  # created and accesses the server over the public IPv4 network. This
  # may cause your allocation to be exhausted. Therefore there are a couple
  # of options.
  #
  # Switch off cloud ip allocation and access over the private IPv4
  # network. Useful if Vagrant is running on another cloud server in the
  # same region.
  #
  # config.vm.network :private_network
  #
  # Switch off cloud ip allocation and access over the public IPv6 network
  #
  # config.vm.network :public_network, ipv6: true

  config.vm.provision :shell do |s|
    s.inline=<<-END
    apt-get install -y -V puppet
    END
  end
  

  # 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 base.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  = "base.pp"
  # end

  # Won't work without puppet installed on the image.
  config.vm.provision :puppet

  # 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