Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Where to store Ansible host file on Mac OS X

I am trying to get started with Ansible to provision my Vagrantbox, but I can’t figure out how to deal with host files.

According to the documentation the should be storred in /etc/ansible/hosts, but I can’t find this on my system (Mac OS X). I also seen examples where the host.ini file situated in the document root adjacent to the vagrant file.

So my question is where would you store your hostfile for setting up a single vagrant box?

like image 798
StenW Avatar asked Feb 22 '14 18:02

StenW


People also ask

Where are Ansible host files stored?

The default location for the inventory file is /etc/ansible/hosts. You can also create project-specific inventory files in alternate locations. The inventory file can list individual hosts or user-defined groups of hosts.

How can I get a list of hosts from an Ansible inventory file?

You can use the option --list-hosts. It will show all the host IPs from your inventory file.


1 Answers

While Ansible will try /etc/ansible/hosts by default, there are several ways to tell ansible where to look for an alternate inventory file :

  • use the -i command line switch and pass your inventory file path
  • add inventory = path_to_hostfile in the [defaults] section of your ~/.ansible.cfg configuration file
  • use export ANSIBLE_HOSTS=path_to_hostfile as suggested by DomaNitro in his answer

Now you don't mention if you want to use the ansible provisionner available in vagrant, or if you want to provision your vagrant host manually.

Let's go for the Vagrant ansible provisionner first :

Create a directory (e.g. test), and create a Vagrant file inside :

Vagrantfile:

Vagrant.configure("2") do |config|    config.vm.box = "precise64-v1.2"   config.vm.box_url = "http://files.vagrantup.com/precise64.box"    config.vm.define :webapp do |webapp|     webapp.vm.hostname = "webapp.local"     webapp.vm.network :private_network, ip: "192.168.123.2"     webapp.vm.provider "virtualbox" do |v|       v.customize ["modifyvm", :id, "--memory", 200, "--name", "vagrant-docs", "--natdnshostresolver1", "on"]     end   end    #    # Provisionning   #   config.vm.provision :ansible do |ansible|     ansible.playbook = "provision.yml"     ansible.inventory_path = "hosts"     ansible.sudo = true     #     # Use anible.tags if you want to restrict what `vagrant provision`     # Here is a list of possible tags     # ansible.tags = "foo bar"     #     # Use ansible.verbose to see detailled output for ansible runs     # ansible.verbose = 'vvv'     #     # Customize your stuff here     ansible.extra_vars = {        some_var: 42,       foo: "bar",     }   end end 

Now when you run vagrant up (or vagrant provision), Vangrant's ansible provionner will look for a file name hosts in the same directory as Vagrantfile, and will try to apply the provision.yml playbook.

You can also run it manually, without resorting to Vagrant's ansible provisionner :

ansible-playbook -i hosts provision.yml --ask-pass --sudo 

Note that Vagrant+Virtualbox+Ansible trio does not always get along well. There are some versions combinations that are problematic. Try to upgrade to the latests versions if you experience issues (especially regarding network).

{shameless_plug} You can find an more extensive example mixing vagrant and ansible here {/shameless_plug}

Good luck !

like image 113
leucos Avatar answered Oct 12 '22 18:10

leucos