Vagrantfile

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

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) 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.

  Vagrant.require_version ">= 1.4.3"

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "demandcube-centos65-virtualbox-v1.1"

  # 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 = "https://github.com/DemandCube/vagrant-centos/releases/download/demandcube-v6.5.1.1/centos65-x86_64-20140126.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

  # More Info See: http://docs.vagrantup.com/v2/vagrantfile/machine_settings.html
  
  config.vm.provider :virtualbox do |vb|
    # vb.name = "sparkngin"
    vb.customize ["modifyvm", :id, "--memory", "1024"]
    vb.customize ["modifyvm", :id, "--cpus", "2"]
  end

  # More Info See: http://docs.vagrantup.com/v2/provisioning/ansible.html
  config.vm.define :demandcubecentostemplate1 do |demandcubecentostemplate1|
    # Create a private network, which allows host-only access to the machine
    # using a specific IP.
    demandcubecentostemplate1.vm.network :private_network, ip: "192.168.56.10"
    demandcubecentostemplate1.vm.hostname = "demandcubecentostemplate1.local"
    
    config.vm.provider :virtualbox do |vb|
      vb.name = "demandcubecentostemplate1"
      # vb.customize ["modifyvm", :id, "--memory", "1024"]
      # vb.customize ["modifyvm", :id, "--cpus", "2"]
    end
    
    # More Info See: http://docs.vagrantup.com/v2/vagrantfile/ssh_settings.html
    
    # sparkngin1.ssh.host = "127.0.0.1"
    # sparkngin1.ssh.port = "2222"
    # sparkngin1.ssh.guest_port = "22" 
    
    # More Info See: http://docs.vagrantup.com/v2/provisioning/ansible.html
    config.vm.provision :ansible do |ansible|
      # ansible.verbose = "v"
      # ansible.verbose = "vv"
      # ansible.verbose = "vvv"
      # ansible.verbose = "vvvv"
      #     'v', verbose mode
      #     'vv'
      #     'vvv', more
      #     'vvvv', connection debugging
      ansible.playbook = "provisioning/server.yml"
      
      # If you get the error below enable the line below
      
      #######
      ansible.host_key_checking = false
      #######
      
      # debug3: check_host_in_hostfile: host [127.0.0.1]:2222 filename /Users/username/.ssh/known_hosts
      # @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
      # @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
      # @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
      # IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
      # Someone could be eavesdropping on you right now (man-in-the-middle attack)!
      # It is also possible that the RSA host key has just been changed.
      # The fingerprint for the RSA key sent by the remote host is
      # 1b:52:69:cb:ed:31:65:ad:3c:12:41:74:8f:77:c0:68.
      # Please contact your system administrator.
      # Add correct host key in /Users/username/.ssh/known_hosts to get rid of this message.
      # Offending key in /Users/username/.ssh/known_hosts:174
      # RSA host key for [127.0.0.1]:2222 has changed and you have requested strict checking.
      # Host key verification failed.
      
    end
    
  end
  
  # config.vm.define :sparkngin2 do |sparkngin2|
  #   # Create a private network, which allows host-only access to the machine
  #   # using a specific IP.
  #   sparkngin2.vm.network :private_network, ip: "192.168.56.12"
  #   sparkngin2.vm.hostname = "sparkngin2.local"
  #   
  #   config.vm.provider :virtualbox do |vb|
  #     vb.name = "sparkngin2"
  #     # vb.customize ["modifyvm", :id, "--memory", "1024"]
  #     # vb.customize ["modifyvm", :id, "--cpus", "2"]
  #   end
  #   
  #   # More Info See: http://docs.vagrantup.com/v2/vagrantfile/ssh_settings.html
  #   
  #   # sparkngin1.ssh.host = "127.0.0.1"
  #   # sparkngin1.ssh.port = "2222"
  #   # sparkngin1.ssh.guest_port = "22" 
  #   
  #   # More Info See: http://docs.vagrantup.com/v2/provisioning/ansible.html
  #   config.vm.provision :ansible do |ansible|
  #     # ansible.verbose = "v"
  #     # ansible.verbose = "vv"
  #     # ansible.verbose = "vvv"
  #     # ansible.verbose = "vvvv"
  #     #     'v', verbose mode
  #     #     'vv'
  #     #     'vvv', more
  #     #     'vvvv', connection debugging
  #     ansible.playbook = "provisioning/server.yml"
  #     
  #     # If you get the error below enable the line below
  #     
  #     #######
  #     ansible.host_key_checking = false
  #     #######
  #     
  #     # debug3: check_host_in_hostfile: host [127.0.0.1]:2222 filename /Users/username/.ssh/known_hosts
  #     # @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
  #     # @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
  #     # @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
  #     # IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
  #     # Someone could be eavesdropping on you right now (man-in-the-middle attack)!
  #     # It is also possible that the RSA host key has just been changed.
  #     # The fingerprint for the RSA key sent by the remote host is
  #     # 1b:52:69:cb:ed:31:65:ad:3c:12:41:74:8f:77:c0:68.
  #     # Please contact your system administrator.
  #     # Add correct host key in /Users/username/.ssh/known_hosts to get rid of this message.
  #     # Offending key in /Users/username/.ssh/known_hosts:174
  #     # RSA host key for [127.0.0.1]:2222 has changed and you have requested strict checking.
  #     # Host key verification failed.
  #     
  #   end
  #   
  # end


  #
  # 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 base-centos.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  = "site.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