Ansible/Vagrant - Revision history

Admin: /* Starting services */

2018-12-10T05:35:11Z

Starting services

← Older revision		Revision as of 05:35, 10 December 2018
Line 232:		Line 232:

	equivalent of running <code>sudo service nginx restart</code>		equivalent of running <code>sudo service nginx restart</code>



			=Flags=

			{{AnsibleFlag}}

Admin: /* Example config file */

2018-12-10T05:34:13Z

Example config file

← Older revision		Revision as of 05:34, 10 December 2018
Line 150:		Line 150:
	</pre>		</pre>

	~~Because~~ the ~~hosts~~ file ~~is already specified as~~ the inventory file, we don't ~~have~~ to ~~use~~ the -i flag:		Now that the Ansible config file specifies that the inventory file is called <code>hosts</code>, we don't need to specify that with the -i flag anymore:

	<pre>		<pre>

Admin: /* Before you begin: set up vagrant box */

2018-12-10T03:38:05Z

Before you begin: set up vagrant box

← Older revision		Revision as of 03:38, 10 December 2018
Line 24:		Line 24:
	vagrant init ubuntu/xenial64		vagrant init ubuntu/xenial64
	</pre>		</pre>

			this will result in a Vagrantfile.

	To bring it up:		To bring it up:

Admin: /* Managing hosts dynamically */

2018-11-11T22:30:17Z

Managing hosts dynamically

← Older revision		Revision as of 22:30, 11 November 2018
Line 68:		Line 68:
	ansible -i dynamic_vagrant.py ...		ansible -i dynamic_vagrant.py ...
	</pre>		</pre>

			===Shortcuts: configuring ansible===

			To make the ansible commands being executed slightly simpler, you can define default values for flags and options.

			See [[Ansible/Configuration]]

	==Ping Vagrant box==		==Ping Vagrant box==

Admin: /* Before you begin: set up vagrant box */

2018-11-11T18:58:03Z

Before you begin: set up vagrant box

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

	Briefly:		Briefly:

			To clear everything out and destroy all old vagrant boxes:

			<pre>
			vagrant destroy --force
			</pre>

	To initialize a vagrant box:		To initialize a vagrant box:

Admin at 04:18, 11 November 2018

2018-11-11T04:18:04Z

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

	[[Vagrant]] is a command line interface to VirtualBox that allows you to create virtual machines from the command line and manage them.		[[Vagrant]] is a command line interface to VirtualBox that allows you to create virtual machines from the command line and manage them. This is a convenient way of testing Ansible scripts locally without using the AWS or Google Cloud platforms.

	Ansible can wrap around Vagrant and use it to automate the management of remote machines. This is useful for testing Ansible locally if you need to test it with multiple machines or particular architectures.		Ansible can wrap around Vagrant and use it to automate the management of remote machines. This is useful for testing Ansible locally if you need to test it with multiple machines or particular architectures.

	~~[[Vagrant]] allows you to set up virtual machine(s) using VirtualBox, which can give you a way of testing Ansible scripts locally (without using the AWS or Google Cloud platforms).~~

	Details of how to connect to vagrant boxes can be added to the Ansible hosts file (see [[Ansible/Vagrant/Static Inventory]] for an example static inventory (hosts) file), or machines can be managed using a dynamic inventory script (see [[Ansible/Vagrant/Dynamic Inventory]] for an example Vagrant dynamic inventory script). This will allow Ansible to connect to the remote machines and execute commands.		Details of how to connect to vagrant boxes can be added to the Ansible hosts file (see [[Ansible/Vagrant/Static Inventory]] for an example static inventory (hosts) file), or machines can be managed using a dynamic inventory script (see [[Ansible/Vagrant/Dynamic Inventory]] for an example Vagrant dynamic inventory script). This will allow Ansible to connect to the remote machines and execute commands.

Admin at 04:17, 11 November 2018

2018-11-11T04:17:22Z

← Older revision		Revision as of 04:17, 11 November 2018
Line 7:		Line 7:
	[[Vagrant]] allows you to set up virtual machine(s) using VirtualBox, which can give you a way of testing Ansible scripts locally (without using the AWS or Google Cloud platforms).		[[Vagrant]] allows you to set up virtual machine(s) using VirtualBox, which can give you a way of testing Ansible scripts locally (without using the AWS or Google Cloud platforms).

	Details of how to connect to vagrant boxes can be added to the Ansible hosts file, or machines can be managed using a dynamic inventory script (see [[Ansible/~~Hosts~~/Dynamic Inventory]] for an example Vagrant dynamic inventory script). This will allow Ansible to connect to the remote machines and execute commands.		Details of how to connect to vagrant boxes can be added to the Ansible hosts file (see [[Ansible/Vagrant/Static Inventory]] for an example static inventory (hosts) file), or machines can be managed using a dynamic inventory script (see [[Ansible/Vagrant/Dynamic Inventory]] for an example Vagrant dynamic inventory script). This will allow Ansible to connect to the remote machines and execute commands.

	==Before you begin: set up vagrant box==		==Before you begin: set up vagrant box==

Admin at 04:15, 11 November 2018

2018-11-11T04:15:32Z

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

	Vagrant is a command line interface to VirtualBox that allows you to create virtual machines from the command line and manage them.		[[Vagrant]] is a command line interface to VirtualBox that allows you to create virtual machines from the command line and manage them.

	Ansible can wrap around Vagrant and use it to automate the management of remote machines. This is useful for testing Ansible locally if you need to test it with multiple machines or particular architectures.		Ansible can wrap around Vagrant and use it to automate the management of remote machines. This is useful for testing Ansible locally if you need to test it with multiple machines or particular architectures.

Admin at 01:46, 11 November 2018

2018-11-11T01:46:19Z

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

	Vagrant is a command line interface to VirtualBox that allows you to create virtual machines from the command line and manage them.		Vagrant is a command line interface to VirtualBox that allows you to create virtual machines from the command line and manage them.

Admin: /* Managing hosts dynamically */

2018-11-11T01:41:53Z

Managing hosts dynamically

← Older revision		Revision as of 01:41, 11 November 2018
Line 55:		Line 55:
	===Managing hosts dynamically===		===Managing hosts dynamically===

	{{Main\|Ansible/~~Hosts~~/Dynamic Inventory}}		{{Main\|Ansible/Vagrant/Dynamic Inventory}}

	~~There is a~~ dynamic inventory ~~management script that interacts with vagrant to provide Ansible with machine details: https://charlesreid1.com/wiki/Ansible/Hosts/Dynamic_Inventory#Putting_it_all_together~~		A dynamic inventory executable file can be used by specifying the path to the executable dynamic inventory script using the -i flag when running ansible:

	~~This~~ can be used by specifying the path to the executable dynamic inventory script using the -i flag when running ansible:

	<pre>		<pre>