Ansible/Vagrant/Static Inventory - Revision history

Admin: /* Managing static inventory file: Multiple Vagrant boxes */

2018-12-10T03:32:12Z

Managing static inventory file: Multiple Vagrant boxes

← Older revision		Revision as of 03:32, 10 December 2018
Line 30:		Line 30:

	Here's an example 3-machine Vagrantfile:		Here's an example 3-machine Vagrantfile:

			'''<code>Vagrantfile</code>:'''

	<pre>		<pre>

Admin: /* Managing static inventory file: Multiple Vagrant boxes */

2018-12-10T03:26:50Z

Managing static inventory file: Multiple Vagrant boxes

← Older revision		Revision as of 03:26, 10 December 2018
Line 59:		Line 59:
	Note that without config.ssh.insert_key=false each machine would use its own SSH key, which would be a bit of a headache. With this directive, we can define a single SSH key in our ansible config file.		Note that without config.ssh.insert_key=false each machine would use its own SSH key, which would be a bit of a headache. With this directive, we can define a single SSH key in our ansible config file.

	It's probably a good idea to use [[Ansible/Vagrant/Dynamic Inventory]], but if we want to manage multiple nodes by hand, start with ssh-config:		It's probably a good idea to use [[Ansible/Vagrant/Dynamic Inventory]], but if we want to manage multiple nodes by hand, start with the output of <code>vagrant ssh-config</code>:

	<pre>		<pre>

Admin: /* Now what? */

2018-11-11T18:47:25Z

Now what?

@@ Line 112: / Line 112: @@
 <pre>
 vagrant up
 </pre>

Admin: /* Managing static inventory file: Multiple Vagrant boxes */

2018-11-11T18:45:49Z

Managing static inventory file: Multiple Vagrant boxes

← Older revision		Revision as of 18:45, 11 November 2018
Line 59:		Line 59:
	Note that without config.ssh.insert_key=false each machine would use its own SSH key, which would be a bit of a headache. With this directive, we can define a single SSH key in our ansible config file.		Note that without config.ssh.insert_key=false each machine would use its own SSH key, which would be a bit of a headache. With this directive, we can define a single SSH key in our ansible config file.

			It's probably a good idea to use [[Ansible/Vagrant/Dynamic Inventory]], but if we want to manage multiple nodes by hand, start with ssh-config:

			<pre>
			Host vagrant1
			HostName 127.0.0.1
			User vagrant
			Port 2200
			UserKnownHostsFile /dev/null
			StrictHostKeyChecking no
			PasswordAuthentication no
			IdentityFile /Users/charles/.vagrant.d/insecure_private_key
			IdentitiesOnly yes
			LogLevel FATAL

			Host vagrant2
			HostName 127.0.0.1
			User vagrant
			Port 2201
			UserKnownHostsFile /dev/null
			StrictHostKeyChecking no
			PasswordAuthentication no
			IdentityFile /Users/charles/.vagrant.d/insecure_private_key
			IdentitiesOnly yes
			LogLevel FATAL

			Host vagrant3
			HostName 127.0.0.1
			User vagrant
			Port 2202
			UserKnownHostsFile /dev/null
			StrictHostKeyChecking no
			PasswordAuthentication no
			IdentityFile /Users/charles/.vagrant.d/insecure_private_key
			IdentitiesOnly yes
			LogLevel FATAL
			</pre>

			Translated into a hosts file:

			<pre>
			$ cat playbooks/hosts

			vb1 ansible_host=127.0.0.1 ansible_port=2200 ansible_user=vagrant ansible_private_key_file=.vagrant.d/insecure_private_key
			vb2 ansible_host=127.0.0.1 ansible_port=2201 ansible_user=vagrant ansible_private_key_file=.vagrant.d/insecure_private_key
			vb3 ansible_host=127.0.0.1 ansible_port=2202 ansible_user=vagrant ansible_private_key_file=.vagrant.d/insecure_private_key
			</pre>

	==Now what?==		==Now what?==

Admin: /* Managing static inventory file: Multiple Vagrant boxes */

2018-11-11T18:30:41Z

Managing static inventory file: Multiple Vagrant boxes

← Older revision		Revision as of 18:30, 11 November 2018
Line 58:		Line 58:

	Note that without config.ssh.insert_key=false each machine would use its own SSH key, which would be a bit of a headache. With this directive, we can define a single SSH key in our ansible config file.		Note that without config.ssh.insert_key=false each machine would use its own SSH key, which would be a bit of a headache. With this directive, we can define a single SSH key in our ansible config file.


			==Now what?==

			Once you have your static inventory manged, you're ready to start up the Vagrant boxes, and then use Ansible to run commands on them.

			<pre>
			vagrant up
			</pre>

			See [[Ansible/Vagrant]] for instructions on using Ansible with Vagrant boxes.

	==Flags==		==Flags==

	{{AnsibleFlag}}		{{AnsibleFlag}}

Admin: /* Managing a static inventory file using Vagrant boxes */

2018-11-11T18:20:21Z

Managing a static inventory file using Vagrant boxes

@@ Line 9: / Line 9: @@
 [[Ansible/Vagrant/Dynamic Inventory]] - dynamic inventory uses something like an API or a database to obtain information about the machines that Ansible is managing. This makes scaling and generalization much easier.
-==Managing a static inventory file using Vagrant boxes==
+==Managing a static inventory file: 1 Vagrant box==
 Edit <code>playbooks/hosts</code> and include details about each vagrant host.
@@ Line 23: / Line 23: @@
 </pre>
-Your vagrant boxes should be up and running with the <code>vagrant up</code> command.
+Your vagrant box should be up and running with the <code>vagrant up</code> command.
 ==Flags==
 {{AnsibleFlag}}

Admin: /* Flags */

2018-11-11T16:31:02Z

Flags

← Older revision		Revision as of 16:31, 11 November 2018
Line 27:		Line 27:
	==Flags==		==Flags==

	~~[[Category:Ansible]]~~		{{AnsibleFlag}}
	~~[[Category:Vagrant]]~~

Admin at 04:20, 11 November 2018

2018-11-11T04:20:21Z

← Older revision		Revision as of 04:20, 11 November 2018
Line 1:		Line 1:
	{{Main\|Ansible/Vagrant}}		{{Main\|Ansible/Vagrant}}

	This page covers how to manage a static inventory file (a.k.a., hosts file, [[Ansible/Hosts]]) for Ansible, maintained by hand, if you are using Ansible with ~~Vagrant (~~[[~~Ansible/~~Vagrant]]).		This page covers how to manage a static inventory file (a.k.a., hosts file, [[Ansible/Hosts]]) for Ansible, maintained by hand, if you are using [[Ansible]] with [[Vagrant]].

	==Static vs dynamic inventory==		==Static vs dynamic inventory==

Admin at 01:40, 11 November 2018

2018-11-11T01:40:26Z

← Older revision		Revision as of 01:40, 11 November 2018
Line 2:		Line 2:

	This page covers how to manage a static inventory file (a.k.a., hosts file, [[Ansible/Hosts]]) for Ansible, maintained by hand, if you are using Ansible with Vagrant ([[Ansible/Vagrant]]).		This page covers how to manage a static inventory file (a.k.a., hosts file, [[Ansible/Hosts]]) for Ansible, maintained by hand, if you are using Ansible with Vagrant ([[Ansible/Vagrant]]).

			==Static vs dynamic inventory==

			[[Ansible/Vagrant/Static Inventory]] - static inventory requires the hosts file (containing the list of machines that Ansible is managing) be kept up to date by hand. This can be a burden if details are changing or if things are allocated automatically.

			[[Ansible/Vagrant/Dynamic Inventory]] - dynamic inventory uses something like an API or a database to obtain information about the machines that Ansible is managing. This makes scaling and generalization much easier.

	==Managing a static inventory file using Vagrant boxes==		==Managing a static inventory file using Vagrant boxes==

Admin at 01:37, 11 November 2018

2018-11-11T01:37:45Z

← Older revision		Revision as of 01:37, 11 November 2018
Line 1:		Line 1:
			{{Main\|Ansible/Vagrant}}

	This page covers how to manage a static inventory file (a.k.a., hosts file, [[Ansible/Hosts]]) for Ansible, maintained by hand, if you are using Ansible with Vagrant ([[Ansible/Vagrant]]).		This page covers how to manage a static inventory file (a.k.a., hosts file, [[Ansible/Hosts]]) for Ansible, maintained by hand, if you are using Ansible with Vagrant ([[Ansible/Vagrant]]).