Ansible/Playbooks - Revision history

Admin: /* Roles */

2018-12-10T17:00:12Z

Roles

← Older revision		Revision as of 17:00, 10 December 2018
Line 31:		Line 31:
	* Roles use a known file structure to load appropriate vars/tasks/handlers		* Roles use a known file structure to load appropriate vars/tasks/handlers
	* A given play will specify a list of roles in the playbook - this indicates that ansible should look for variables/tasks/handlers that match up with those roles, and add them to the play		* A given play will specify a list of roles in the playbook - this indicates that ansible should look for variables/tasks/handlers that match up with those roles, and add them to the play
			* Roles can be dependent on other roles (that's the purpose of the "meta" yaml file)

	~~So, for example,~~ the following playbook entry will automatically populate the play with a list of variables, tasks, and handlers from the roles subdirectory ~~(which~~ will ~~itself~~ contain subdirectories for ~~each role):~~		Example:
			* the following playbook entry will automatically populate the play with a list of variables, tasks, and handlers from the roles subdirectory
			* the roles subdirectory will contain two subdirectories, common and web, with files for those roles

	<pre>		<pre>

Admin: /* Roles */

2018-12-10T16:58:26Z

Roles

← Older revision		Revision as of 16:58, 10 December 2018
Line 36:		Line 36:
	<pre>		<pre>
	---		---
			# playbook.yml
	- name: example play		- name: example play
	hosts: webservers		hosts: webservers

Admin: /* Roles= */

2018-12-10T16:58:07Z

Roles=

← Older revision		Revision as of 16:58, 10 December 2018
Line 26:		Line 26:
	* the handlers are triggered once at the end of each block of tasks - this keeps them from being restarted over and over by a set of related tasks		* the handlers are triggered once at the end of each block of tasks - this keeps them from being restarted over and over by a set of related tasks

	===Roles====		===Roles===

	* Roles are just a way of automatically loading variables, tasks, and task handlers.		* Roles are just a way of automatically loading variables, tasks, and task handlers.
Line 42:		Line 42:
	- web		- web
	</pre>		</pre>


	===Tags===		===Tags===

Admin: /* Overview */

2018-12-10T16:57:49Z

Overview

← Older revision		Revision as of 16:57, 10 December 2018
Line 3:		Line 3:
	The Ansible documentation has a nice overview of playbooks: https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html		The Ansible documentation has a nice overview of playbooks: https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html

	Notes ~~on playbooks:~~		==Brief Notes==

			===Playbooks===

	* playbooks are a way of executing commands on remote machines in a scripted way		* playbooks are a way of executing commands on remote machines in a scripted way
	* can orchestrate multiple ordered processes		* can orchestrate multiple ordered processes
Line 12:		Line 15:
	* users - the remote user is the user that Ansible will run the particular task as		* users - the remote user is the user that Ansible will run the particular task as

	~~Notes on tasks:~~		===Tasks===

	* each play has a list of tasks associated with it		* each play has a list of tasks associated with it
Line 18:		Line 21:
	* ansible completes the task on all remote machines before it moves on to the next task		* ansible completes the task on all remote machines before it moves on to the next task

	~~Notes on handlers:~~		===Handlers===

			* handlers are "conditional tasks" - tasks that are triggered by other tasks
	* the handlers are triggered once at the end of each block of tasks - this keeps them from being restarted over and over by a set of related tasks		* the handlers are triggered once at the end of each block of tasks - this keeps them from being restarted over and over by a set of related tasks

	~~Notes on being idempotent~~:		===Roles====

			* Roles are just a way of automatically loading variables, tasks, and task handlers.
			* Roles use a known file structure to load appropriate vars/tasks/handlers
			* A given play will specify a list of roles in the playbook - this indicates that ansible should look for variables/tasks/handlers that match up with those roles, and add them to the play

			So, for example, the following playbook entry will automatically populate the play with a list of variables, tasks, and handlers from the roles subdirectory (which will itself contain subdirectories for each role):

			<pre>
			---
			- name: example play
			hosts: webservers
			roles:
			- common
			- web
			</pre>


			===Tags===

			* Tags are a way of only running part of your playbook
			* Think of tags as a filtering operation

			===Idempotence===

	* idempotent means you can run it multiple times with the same outcome as running it one time		* idempotent means you can run it multiple times with the same outcome as running it one time

Admin: /* Overview */

2018-12-10T16:52:44Z

Overview

← Older revision		Revision as of 16:52, 10 December 2018
Line 17:		Line 17:
	* tasks are executed in order on all machines that match the host pattern		* tasks are executed in order on all machines that match the host pattern
	* ansible completes the task on all remote machines before it moves on to the next task		* ansible completes the task on all remote machines before it moves on to the next task

			Notes on handlers:

			* the handlers are triggered once at the end of each block of tasks - this keeps them from being restarted over and over by a set of related tasks

	Notes on being idempotent:		Notes on being idempotent:

Admin at 16:42, 10 December 2018

2018-12-10T16:42:47Z

← Older revision		Revision as of 16:42, 10 December 2018
Line 1:		Line 1:
			=Overview=

			The Ansible documentation has a nice overview of playbooks: https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html

			Notes on playbooks:
			* playbooks are a way of executing commands on remote machines in a scripted way
			* can orchestrate multiple ordered processes
			* playbooks are written in YAML
			* each playbook can contain one or more plays
			* each play will target different servers (maybe all of them, maybe just web servers, maybe just db servers)
			* user specifies hosts - remote machines on which Ansible will run commands
			* users - the remote user is the user that Ansible will run the particular task as

			Notes on tasks:

			* each play has a list of tasks associated with it
			* tasks are executed in order on all machines that match the host pattern
			* ansible completes the task on all remote machines before it moves on to the next task

			Notes on being idempotent:

			* idempotent means you can run it multiple times with the same outcome as running it one time
			* modules should check whether the desired final state has already been achieved, and exit without doing anything if so

	=Example: Secure Nginx Server=		=Example: Secure Nginx Server=

Admin: /* Flags */

2018-11-11T16:28:15Z

Flags

← Older revision		Revision as of 16:28, 11 November 2018
Line 14:		Line 14:
	{{AnsibleFlag}}		{{AnsibleFlag}}

	[[Category:~~AnsiblePlaybooks~~]]		[[Category:Ansible Playbooks]]

Admin: /* Flags */

2018-11-11T16:28:07Z

Flags

← Older revision		Revision as of 16:28, 11 November 2018
Line 12:		Line 12:
	=Flags=		=Flags=

			{{AnsibleFlag}}

	[[Category:~~Web Server]]~~		[[Category:AnsiblePlaybooks]]
	~~[[Category:Nginx]]~~
	~~[[Category:Ansible]]~~
	~~[[Category:Infrastructure]]~~
	~~[[Category:Python]]~~
	~~[[Category:HTTPS]]~~
	~~[[Category:SSL~~]]

Admin: /* Example: Secure Nginx Server */

2018-11-11T16:22:37Z

Example: Secure Nginx Server

← Older revision		Revision as of 16:22, 11 November 2018
Line 1:		Line 1:
	=Example: Secure Nginx Server=		=Example: Secure Nginx Server=

	[[Ansible/~~Nginx_Playbook~~]] - a page that walks through two example playbooks		[[Ansible/Nginx Playbook]] - a page that walks through two example playbooks

	* [https://charlesreid1.com/wiki/Ansible/Nginx_Playbook#Ansible_Playbook_Example_1:_Nginx_Server_Playbook Example 1: nginx server playbook]		* [https://charlesreid1.com/wiki/Ansible/Nginx_Playbook#Ansible_Playbook_Example_1:_Nginx_Server_Playbook Example 1: nginx server playbook]

Admin: /* Example: Secure Nginx Server */

2018-11-07T15:54:19Z

Example: Secure Nginx Server

← Older revision		Revision as of 15:54, 7 November 2018
Line 5:		Line 5:
	* [https://charlesreid1.com/wiki/Ansible/Nginx_Playbook#Ansible_Playbook_Example_1:_Nginx_Server_Playbook Example 1: nginx server playbook]		* [https://charlesreid1.com/wiki/Ansible/Nginx_Playbook#Ansible_Playbook_Example_1:_Nginx_Server_Playbook Example 1: nginx server playbook]
	* [https://charlesreid1.com/wiki/Ansible/Nginx_Playbook#Ansible_Playbook_Example_2:_Secure_Nginx_Server_Playbook Example 2: secure nginx server playbook]		* [https://charlesreid1.com/wiki/Ansible/Nginx_Playbook#Ansible_Playbook_Example_2:_Secure_Nginx_Server_Playbook Example 2: secure nginx server playbook]

			=Full Stack Example: Django Celery RabbitMQ Postgres=

			[[Ansible/Full Stack Playbook]] - a page that walks through a playbook for a full stack example

	=Flags=		=Flags=