|
| 1 | +# -*- mode: ruby -*- |
| 2 | +# vi: set ft=ruby : |
| 3 | + |
| 4 | +# Vagrantfile API/syntax version. Don't touch unless you know what you're doing! |
| 5 | +VAGRANTFILE_API_VERSION = "2" |
| 6 | + |
| 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. |
| 11 | + |
| 12 | + # Every Vagrant virtual environment requires a box to build off of. |
| 13 | + #config.vm.box = "hashicorp/precise32" |
| 14 | + #config.vm.box = "chef/centos-6.5" |
| 15 | + |
| 16 | + #config.vm.synced_folder ".", "/vagrant", type: "nfs" |
| 17 | + config.vm.synced_folder ".", "/vagrant" |
| 18 | + |
| 19 | + config.vm.define "execd2" do |execd2| |
| 20 | + execd2.vm.box = "chef/centos-6.5" |
| 21 | + execd2.vm.hostname = "execd2" |
| 22 | + execd2.vm.network "private_network", ip: "192.168.10.101" |
| 23 | + execd2.vm.provision "shell", path: "hostnames.sh" |
| 24 | + end |
| 25 | + |
| 26 | + config.vm.define "execd1" do |execd1| |
| 27 | + execd1.vm.box = "chef/centos-6.5" |
| 28 | + execd1.vm.hostname = "execd1" |
| 29 | + execd1.vm.network "private_network", ip: "192.168.10.100" |
| 30 | + execd1.vm.provision "shell", path: "hostnames.sh" |
| 31 | + end |
| 32 | + |
| 33 | + config.vm.define "master" do |master| |
| 34 | + master.vm.box = "chef/centos-6.5" |
| 35 | + master.vm.hostname = "master" |
| 36 | + master.vm.network "private_network", ip: "192.168.10.99" |
| 37 | + master.vm.provision "shell", path: "hostnames.sh" |
| 38 | + master.vm.provision "shell", path: "installation.sh" |
| 39 | + end |
| 40 | + |
| 41 | + # Disable automatic box update checking. If you disable this, then |
| 42 | + # boxes will only be checked for updates when the user runs |
| 43 | + # `vagrant box outdated`. This is not recommended. |
| 44 | + # config.vm.box_check_update = false |
| 45 | + |
| 46 | + # Create a forwarded port mapping which allows access to a specific port |
| 47 | + # within the machine from a port on the host machine. In the example below, |
| 48 | + # accessing "localhost:8080" will access port 80 on the guest machine. |
| 49 | + # config.vm.network "forwarded_port", guest: 80, host: 8080 |
| 50 | + |
| 51 | + # Create a private network, which allows host-only access to the machine |
| 52 | + # using a specific IP. |
| 53 | + config.vm.network "private_network", ip: "192.168.33.10" |
| 54 | + |
| 55 | + # Create a public network, which generally matched to bridged network. |
| 56 | + # Bridged networks make the machine appear as another physical device on |
| 57 | + # your network. |
| 58 | + # config.vm.network "public_network" |
| 59 | + |
| 60 | + # If true, then any SSH connections made will enable agent forwarding. |
| 61 | + # Default value: false |
| 62 | + # config.ssh.forward_agent = true |
| 63 | + |
| 64 | + # Share an additional folder to the guest VM. The first argument is |
| 65 | + # the path on the host to the actual folder. The second argument is |
| 66 | + # the path on the guest to mount the folder. And the optional third |
| 67 | + # argument is a set of non-required options. |
| 68 | + # config.vm.synced_folder "../data", "/vagrant_data" |
| 69 | + |
| 70 | + # Provider-specific configuration so you can fine-tune various |
| 71 | + # backing providers for Vagrant. These expose provider-specific options. |
| 72 | + # Example for VirtualBox: |
| 73 | + # |
| 74 | + config.vm.provider "virtualbox" do |vb| |
| 75 | + # # Don't boot with headless mode |
| 76 | + vb.gui = false |
| 77 | + # |
| 78 | + # # Use VBoxManage to customize the VM. For example to change memory: |
| 79 | + vb.customize ["modifyvm", :id, "--memory", "1024"] |
| 80 | + end |
| 81 | + # |
| 82 | + # View the documentation for the provider you're using for more |
| 83 | + # information on available options. |
| 84 | + |
| 85 | + # Enable provisioning with CFEngine. CFEngine Community packages are |
| 86 | + # automatically installed. For example, configure the host as a |
| 87 | + # policy server and optionally a policy file to run: |
| 88 | + # |
| 89 | + # config.vm.provision "cfengine" do |cf| |
| 90 | + # cf.am_policy_hub = true |
| 91 | + # # cf.run_file = "motd.cf" |
| 92 | + # end |
| 93 | + # |
| 94 | + # You can also configure and bootstrap a client to an existing |
| 95 | + # policy server: |
| 96 | + # |
| 97 | + # config.vm.provision "cfengine" do |cf| |
| 98 | + # cf.policy_server_address = "10.0.2.15" |
| 99 | + # end |
| 100 | + |
| 101 | + # Enable provisioning with Puppet stand alone. Puppet manifests |
| 102 | + # are contained in a directory path relative to this Vagrantfile. |
| 103 | + # You will need to create the manifests directory and a manifest in |
| 104 | + # the file default.pp in the manifests_path directory. |
| 105 | + # |
| 106 | + # config.vm.provision "puppet" do |puppet| |
| 107 | + # puppet.manifests_path = "manifests" |
| 108 | + # puppet.manifest_file = "site.pp" |
| 109 | + # end |
| 110 | + |
| 111 | + # Enable provisioning with chef solo, specifying a cookbooks path, roles |
| 112 | + # path, and data_bags path (all relative to this Vagrantfile), and adding |
| 113 | + # some recipes and/or roles. |
| 114 | + # |
| 115 | + # config.vm.provision "chef_solo" do |chef| |
| 116 | + # chef.cookbooks_path = "../my-recipes/cookbooks" |
| 117 | + # chef.roles_path = "../my-recipes/roles" |
| 118 | + # chef.data_bags_path = "../my-recipes/data_bags" |
| 119 | + # chef.add_recipe "mysql" |
| 120 | + # chef.add_role "web" |
| 121 | + # |
| 122 | + # # You may also specify custom JSON attributes: |
| 123 | + # chef.json = { mysql_password: "foo" } |
| 124 | + # end |
| 125 | + |
| 126 | + # Enable provisioning with chef server, specifying the chef server URL, |
| 127 | + # and the path to the validation key (relative to this Vagrantfile). |
| 128 | + # |
| 129 | + # The Opscode Platform uses HTTPS. Substitute your organization for |
| 130 | + # ORGNAME in the URL and validation key. |
| 131 | + # |
| 132 | + # If you have your own Chef Server, use the appropriate URL, which may be |
| 133 | + # HTTP instead of HTTPS depending on your configuration. Also change the |
| 134 | + # validation key to validation.pem. |
| 135 | + # |
| 136 | + # config.vm.provision "chef_client" do |chef| |
| 137 | + # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME" |
| 138 | + # chef.validation_key_path = "ORGNAME-validator.pem" |
| 139 | + # end |
| 140 | + # |
| 141 | + # If you're using the Opscode platform, your validator client is |
| 142 | + # ORGNAME-validator, replacing ORGNAME with your organization name. |
| 143 | + # |
| 144 | + # If you have your own Chef Server, the default validation client name is |
| 145 | + # chef-validator, unless you changed the configuration. |
| 146 | + # |
| 147 | + # chef.validation_client_name = "ORGNAME-validator" |
| 148 | +end |
0 commit comments