4 # Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
5 VAGRANTFILE_API_VERSION = "2"
7 Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
8 # All Vagrant configuration is done here. The most common configuration
9 # options are documented and commented below. For a complete reference,
10 # please see the online documentation at vagrantup.com.
12 # Every Vagrant virtual environment requires a box to build off of.
13 config.vm.box = "mininet-2.1.0-of1.3"
15 # The url from where the 'config.vm.box' box will be fetched if it
16 # doesn't already exist on the user's system.
17 config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"
19 # Create a forwarded port mapping which allows access to a specific port
20 # within the machine from a port on the host machine. In the example below,
21 # accessing "localhost:8080" will access port 80 on the guest machine.
22 # config.vm.network :forwarded_port, guest: 80, host: 8080
24 # Create a private network, which allows host-only access to the machine
25 # using a specific IP.
26 # config.vm.network :private_network, ip: "192.168.33.10"
28 # Create a public network, which generally matched to bridged network.
29 # Bridged networks make the machine appear as another physical device on
31 # config.vm.network :public_network
33 # If true, then any SSH connections made will enable agent forwarding.
34 # Default value: false
35 config.ssh.forward_agent = true
37 # Share an additional folder to the guest VM. The first argument is
38 # the path on the host to the actual folder. The second argument is
39 # the path on the guest to mount the folder. And the optional third
40 # argument is a set of non-required options.
41 # config.vm.synced_folder "../data", "/vagrant_data"
43 # Provider-specific configuration so you can fine-tune various
44 # backing providers for Vagrant. These expose provider-specific options.
45 # Example for VirtualBox:
47 # config.vm.provider :virtualbox do |vb|
48 # # Don't boot with headless mode
51 # # Use VBoxManage to customize the VM. For example to change memory:
52 # vb.customize ["modifyvm", :id, "--memory", "1024"]
55 # View the documentation for the provider you're using for more
56 # information on available options.
58 config.vm.provision :shell, :path => "bootstrap.sh"
60 # Enable provisioning with Puppet stand alone. Puppet manifests
61 # are contained in a directory path relative to this Vagrantfile.
62 # You will need to create the manifests directory and a manifest in
63 # the file base.pp in the manifests_path directory.
65 # An example Puppet manifest to provision the message of the day:
68 # # ensure => "present",
71 # # File { owner => 0, group => 0, mode => 0644 }
73 # # file { '/etc/motd':
74 # # content => "Welcome to your Vagrant-built virtual machine!
75 # # Managed by Puppet.\n"
78 # config.vm.provision :puppet do |puppet|
79 # puppet.manifests_path = "manifests"
80 # puppet.manifest_file = "site.pp"
83 # Enable provisioning with chef solo, specifying a cookbooks path, roles
84 # path, and data_bags path (all relative to this Vagrantfile), and adding
85 # some recipes and/or roles.
87 # config.vm.provision :chef_solo do |chef|
88 # chef.cookbooks_path = "../my-recipes/cookbooks"
89 # chef.roles_path = "../my-recipes/roles"
90 # chef.data_bags_path = "../my-recipes/data_bags"
91 # chef.add_recipe "mysql"
94 # # You may also specify custom JSON attributes:
95 # chef.json = { :mysql_password => "foo" }
98 # Enable provisioning with chef server, specifying the chef server URL,
99 # and the path to the validation key (relative to this Vagrantfile).
101 # The Opscode Platform uses HTTPS. Substitute your organization for
102 # ORGNAME in the URL and validation key.
104 # If you have your own Chef Server, use the appropriate URL, which may be
105 # HTTP instead of HTTPS depending on your configuration. Also change the
106 # validation key to validation.pem.
108 # config.vm.provision :chef_client do |chef|
109 # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
110 # chef.validation_key_path = "ORGNAME-validator.pem"
113 # If you're using the Opscode platform, your validator client is
114 # ORGNAME-validator, replacing ORGNAME with your organization name.
116 # If you have your own Chef Server, the default validation client name is
117 # chef-validator, unless you changed the configuration.
119 # chef.validation_client_name = "ORGNAME-validator"