When working with complex or long playbooks, administrators can use separate files to divide tasks and lists of variables into smaller pieces for easier management. There are multiple ways to include task files and variables in a playbook.<\/p>\n
<\/p>\n
\u2022 Tasks can be included in a playbook from an external file by using the \u2022 The Using multiple, external files for tasks and variables is a convenient way to build the main playbook in a modular way, and facilitates reuse of Ansible elements across multiple playbooks.<\/p>\n Including tasks<\/span><\/p>\n The include directive allows administrators to have a task file inserted at a particular point in a playbook. A task file is simply a file that contains a flat list of tasks ( An Important<\/strong><\/em> For complex projects, roles<\/strong> provide a powerful way to organize included task files and playbooks.<\/p>\n <\/p>\n Including variables<\/span> The following YAML file, To import these two variables in a playbook, the Important<\/strong><\/em> <\/p>\n Example 1.<\/span><\/p>\n Define the Create the fileservers.yml playbook and include the paths.yml variables file. The fileserver will be created using the variable defined previously in the paths.yml variables file.<\/p>\n Run the fileservers.yml playbook and examine the output.<\/p>\n The output shows the directory structure that has been created by Ansible, which matches the path that has been set by the paths.fileserver variable.<\/p>\n Create the Run the Create another variable file, Create a task file, called Create the Run the playbook and watch the output.<\/p>\n Note the httpd package has been installed from a task, whereas the name of the package to install is defined in the variables file.<\/p>\n Update the Run the playbook and watch the output as Ansible installs the tomcat package.<\/p>\n <\/p>\n Example 2.<\/span><\/p>\n In the vars directory, create the In the tasks directory, create the Create and edit the main playbook, named playbook.yml. The playbook imports the tasks as well as the variables; and it installs the firewalld service and configures it.\u00a0 Start by adding the webserver host group. Define a rule variable with a value of http.<\/p>\n Define the first task, which uses the Define the second task which uses the include module to include the base Create three more tasks: one that installs the firewalld package, one that starts the firewalld service, and one that adds a rule for the HTTP service. Use the variables that were defined previously.<\/p>\n Create a task that installs the firewalld<\/em> package using the Finally, add a task that creates the The main Run the playbook using the ansible-playbook command. Watch the output as Ansible starts by including the environment.yml playbook and running its tasks, then keeps executing the tasks defined in the main playbook.<\/p>\n Use curl to ensure the web server is reachable from workstation. Because the <\/p>\n Example 2.<\/span><\/p>\n Create a facts file in INI format called custom.fact. Create a section called Create the fact file From the project directory, create the Run the playbook to install the custom facts and verify the facts are available as Ansible facts.<\/p>\n Ensure the newly created facts can be retrieved.<\/p>\n Create a directory for variables, called vars. Define a YAML variable file, called main.yml, in that directory that defines a new variable, called web_root, with a value of \/var\/www\/html.<\/p>\n Create the variables directory, vars, inside the project directory.<\/p>\n Create the variables file From the project directory, lab-managing-vars, create a directory for tasks, called tasks. Define a task file in the subdirectory, called Create the tasks directory inside the project directory.<\/p>\n Create the tasks file, Create the main playbook Both the host name and the IP address should use Ansible facts.<\/p>\n When complete, the tree should appear as follows:<\/p>\n The main playbook should appear as follows:<\/p>\n Explanation:<\/p>\n First task includes the variables file located under vars\/main.yml. Second task imports the tasks file located under tasks\/main.yml. Next tasks that install the firewall, start the service, open port 80, and reload the service. Finally, create the task that uses the copy module to create a custom main page, index.html. Use the variable Run the playbook From workstation, use curl to ensure the web server is reachable.<\/p>\n Also use an ad hoc command to connect to serverb as the devops user and ensure the mariadb service is running.<\/p>\n <\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" When working with complex or long playbooks, administrators can use separate files to divide tasks and lists of variables into smaller pieces for easier management. There are multiple ways to include task files and variables in a playbook.<\/p>\n","protected":false},"author":1,"featured_media":3446,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[86],"tags":[],"_links":{"self":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts\/3441"}],"collection":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/comments?post=3441"}],"version-history":[{"count":13,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts\/3441\/revisions"}],"predecessor-version":[{"id":3456,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts\/3441\/revisions\/3456"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/media\/3446"}],"wp:attachment":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/media?parent=3441"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/categories?post=3441"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/tags?post=3441"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}include<\/code> directive.<\/p>\ntasks:\r\n- name: Include tasks to install the database server\r\n include: tasks\/db_server.yml<\/pre>\n
include_vars<\/code> module can include variables defined in either JSON or YAML files, overriding host variables and playbook variables already defined.<\/p>\ntasks:\r\n- name: Include the variables from a YAML or JSON file\r\n include_vars: vars\/variables.yml<\/pre>\n
environment.yml<\/code>):<\/p>\n- name: Installs the {{ package }} package\r\n yum:\r\n name: \"{{ package }}\"\r\n state: latest\r\n- name: Starts the {{ service }} service\r\n service:\r\n name: \"{{ service }}\"\r\n state: \"{{ state }}\"<\/pre>\ninclude<\/code> directive with variables could be used in a playbook, like this:<\/p>\n---\r\n- name: Install, start, and enable services\r\n hosts: all\r\n tasks:\r\n - name: Includes the tasks file and defines the variables\r\n include: environment.yml\r\n vars:\r\n package: mariadb-server\r\n service: mariadb\r\n state: started\r\n register: output\r\n - name: Debugs the included tasks\r\n debug:\r\n var: output<\/pre>\n
\nTasks included in a playbook are evaluated based on their order in the playbook. For example, a playbook may have a task to start a service provided by a software package, and a second task included from an external file that installs that software package. The external task must be included in the playbook before the task to start the package’s service is declared in the playbook.<\/p>\n
\nJust as tasks can be included in playbooks, variables can be externally defined and included in playbooks. There are many ways in which this can be done. Some of the ways to set variables include:
\n\u2022 Inventory variables defined in the inventory file or in external files in host_vars<\/code> and group_vars<\/code> directories
\n\u2022 Facts and registered<\/code> variables
\n\u2022 Playbook variables defined in the playbook file with vars or in an external file through vars_files<\/code><\/p>\nvariables.yml<\/code>, contains two variables
\nthat define the packages to install:<\/p>\n---\r\npackages:\r\n web_package: httpd\r\n db_package: mariadb-server<\/pre>\n
include_vars<\/code> module can be used:<\/p>\n---\r\n- name: Install web application packages\r\n hosts: all\r\n tasks:\r\n - name: Includes the tasks file and defines the variables\r\n include_vars: variables.yml\r\n - name: Debugs the variables imported\r\n debug:\r\n msg: >\r\n \"{{ packages['web_package'] }} and {{ packages.db_package }} have been imported\"<\/pre>\n
\nWhen deciding where to define variables, try to keep things simple.
\nIn most cases, it is not necessary to use include_vars, host_vars and
\ngroup_vars files, playbook vars_files directives, inlined variables in playbook and inventory files, and command-line overrides all at the same time. In fact, that much complexity could make it hard to easily maintain your Ansible project.<\/p>\npaths.yml<\/code> variables file and create a dictionary that sets some system paths. Specify the fileserver base path\u00a0 with the\u00a0 ansible_fqdn<\/code> variable and dbpath base path\u00a0 with the ansible_fqdn<\/code> variable.<\/p>\n---\r\npaths:\r\n fileserver: \/home\/student\/srv\/filer\/{{ ansible_fqdn }}\r\n dbpath: \/home\/student\/srv\/database\/{{ ansible_fqdn }}\r\n<\/pre>\n---\r\n- name: Configure fileservers\r\n hosts: fileservers\r\n tasks:\r\n - name: Imports the variables file\r\n include_vars: paths.yml\r\n - name: Creates the remote directory\r\n file:\r\n path: \"{{ paths.fileserver }}\"\r\n state: directory\r\n mode: 0755\r\n register: result\r\n - name: Debugs the results\r\n debug:\r\n var: result<\/pre>\n[student@workstation demo-vars-inclusions]$ ansible-playbook fileservers.yml\r\nPLAY [Configure fileservers] ***********************************************\r\nTASK [setup] ***************************************************************\r\nChapter\u00a04.\u00a0Managing Variables and Inclusions\r\n144 DO407-A2.0-en-1-20160804\r\nok: [servera.lab.example.com]\r\nTASK [Imports the variables file] ******************************************\r\nok: [servera.lab.example.com]\r\nTASK [Creates the remote directory] ****************************************\r\nchanged: [servera.lab.example.com]\r\nTASK [Debugs the results] **************************************************\r\nok: [servera.lab.example.com] => {\r\n\"result\": {\r\n\"changed\": true,\r\n\"gid\": 0,\r\n\"group\": \"root\",\r\n\"mode\": \"0755\",\r\n\"owner\": \"root\",\r\n\"path\": \"\/home\/student\/srv\/filer\/servera.lab.example.com\",\r\n\"secontext\": \"unconfined_u:object_r:user_home_t:s0\",\r\n\"size\": 6,\r\n\"state\": \"directory\",\r\n\"uid\": 0\r\n}\r\n}\r\nPLAY RECAP *****************************************************************\r\nservera.lab.example.com : ok=4 changed=1 unreachable=0 failed=0<\/pre>\ndbservers.yml<\/code> playbook. Include the variable file and use the paths.dbpath<\/code> variable to create the directory structure.<\/p>\n---\r\n- name: Configure DB Servers\r\n hosts: dbservers\r\n tasks:\r\n - name: Imports the variables file\r\n include_vars: paths.yml\r\n - name: Creates the remote directory\r\n file:\r\n path: \"{{ paths.dbpath }}\"\r\n state: directory\r\n mode: 0755\r\n register: result\r\n - name: Debugs the results\r\n debug:\r\n var: result<\/pre>\ndbservers.yml<\/code> playbook and examine the output.<\/p>\n[student@workstation demo-vars-inclusions]$ ansible-playbook dbservers.yml\r\nPLAY [Configure DB Servers] ************************************************\r\nTASK [setup] ***************************************************************\r\nok: [servera.lab.example.com]\r\nTASK [Imports the variables file] ******************************************\r\nIncluding variables\r\nDO407-A2.0-en-1-20160804 145\r\nok: [servera.lab.example.com]\r\nTASK [Creates the remote directory] ****************************************\r\nchanged: [servera.lab.example.com]\r\nTASK [Debugs the results] **************************************************\r\nok: [servera.lab.example.com] => {\r\n\"result\": {\r\n\"changed\": true,\r\n\"gid\": 0,\r\n\"group\": \"root\",\r\n\"mode\": \"0755\",\r\n\"owner\": \"root\",\r\n\"path\": \"\/home\/student\/srv\/database\/servera.lab.example.com\",\r\n\"secontext\": \"unconfined_u:object_r:user_home_t:s0\",\r\n\"size\": 6,\r\n\"state\": \"directory\",\r\n\"uid\": 0\r\n}\r\n}\r\nPLAY RECAP *****************************************************************\r\nservera.lab.example.com : ok=4 changed=1 unreachable=0 failed=0<\/pre>\npackage.yml<\/code>, and define the name of the package to install.<\/p>\n---\r\npackages:\r\n web_pkg: httpd<\/pre>\n
install_package.yml<\/code>, and create a basic task that installs a package.<\/p>\n---\r\n- name: Installs {{ packages.web_pkg }}\r\n yum:\r\n name: \"{{ packages.web_pkg }}\"\r\n state: latest<\/pre>\nplaybook.yml<\/code> playbook. Define it for the hosts in the fileservers group. Include both variable files as well as the task file.<\/p>\n---\r\n- name: Install fileserver packages\r\n hosts: fileservers\r\n tasks:\r\n - name: Includes the variable\r\n include_vars: package.yml\r\n - name: Installs the package\r\n include: install_package.yml<\/pre>\n
[student@workstation demo-vars-inclusions]$ ansible-playbook playbook.yml\r\nPLAY [Install fileserver packages] *****************************************\r\nChapter\u00a04.\u00a0Managing Variables and Inclusions\r\n146 DO407-A2.0-en-1-20160804\r\nTASK [setup] ***************************************************************\r\nok: [servera.lab.example.com]\r\nTASK [Includes the variable] ***********************************************\r\nok: [servera.lab.example.com]\r\nTASK [Installs the package] ************************************************\r\nincluded: \/home\/student\/demo-vars-inclusions\/install_package.yml\r\nfor servera.lab.example.com\r\nTASK [Installs httpd] ******************************************************\r\nchanged: [servera.lab.example.com]\r\nPLAY RECAP *****************************************************************\r\nservera.lab.example.com : ok=4 changed=1 unreachable=0 failed=0<\/pre>\n
playbook.yml<\/code> playbook to override the name of the package to install. Append a vars block to the include statement and define a dictionary to override the name of the package to install.<\/p>\n---\r\n- name: Install fileserver packages\r\n hosts: fileservers\r\n tasks:\r\n - name: Includes the variable\r\n include_vars: package.yml\r\n - name: Installs the package\r\n include: install_package.yml\r\n vars:\r\n packages:\r\n web_pkg: tomcat<\/pre>\n
[student@workstation demo-vars-inclusions]$ ansible-playbook playbook.yml\r\nPLAY [Install fileserver packages] *****************************************\r\nTASK [setup] ***************************************************************\r\nok: [servera.lab.example.com]\r\nTASK [Includes the variable] ***********************************************\r\nok: [servera.lab.example.com]\r\nTASK [Installs the package] ************************************************\r\nincluded: \/home\/student\/demo-vars-inclusions\/install_package.yml\r\nfor servera.lab.example.com\r\nTASK [Installs tomcat] *****************************************************\r\nchanged: [servera.lab.example.com]\r\nPLAY RECAP *****************************************************************\r\nservera.lab.example.com : ok=4 changed=1 unreachable=0 failed=0<\/pre>\n
variables.yml<\/code> variables file. The file defines the firewall_pkg<\/code> variable in YAML format. The file should read as follows:<\/p>\n---\r\nfirewall_pkg: firewalld<\/pre>\n
environment.yml<\/code> task file. Define the two tasks that install and start the web server; use the package variable for the package name, service for the service name, and svc_state for the service state.<\/p>\n---\r\n- name: Install the {{ package }} package\r\n yum:\r\n name: \"{{ package }}\"\r\n state: latest\r\n- name: Start the {{ service }} service\r\n service:\r\n name: \"{{ service }}\"\r\n state: \"{{ svc_state }}\"<\/pre>\n include_vars<\/code> module to import extra variables in the playbook. The variables are used by other tasks in the playbook. Include the variables.yml<\/code> variable file created previously.<\/p>\n
\nenvironment.yml<\/code> playbook. Because the three defined variables are used in the base playbook, but are not defined, include a vars block. Set three variables in the vars section: package<\/code> set as httpd, service<\/code> set as httpd, and svc_state<\/code> set as started.<\/p>\n firewall_pkg<\/code> variable. Create a task that starts the firewalld service. Create a task that adds a firewall rule for the HTTP service using the rule variable.<\/p>\n index.html<\/code> file for the web server using the copy module. Create the file with the Ansible ansible_fqdn fact<\/code>, which returns the fully qualified domain name. Also include a time stamp in the file using an Ansible fact.<\/p>\nplaybook.yml<\/code> playbook appear as follows:<\/p>\n---\r\n- hosts: webserver\r\n vars:\r\n rule: http\r\n tasks:\r\n - name: Include the variables from the YAML file\r\n include_vars: vars\/variables.yml\r\n - name: Include the environment file and set the variables\r\n include: tasks\/environment.yml\r\n vars:\r\n package: httpd\r\n service: httpd\r\n svc_state: started\r\n - name: Install the firewall\r\n yum:\r\n name: \"{{ firewall_pkg }}\"\r\n state: latest\r\n - name: Start the firewall\r\n service:\r\n name: firewalld\r\n state: started\r\n enabled: true\r\n - name: Open the port for {{ rule }}\r\n firewalld:\r\n service: \"{{ rule }}\"\r\n immediate: true\r\n permanent: true\r\n state: enabled\r\n - name: Create index.html\r\n copy:\r\n content: \"{{ ansible_fqdn }} has been customized using Ansible on the{{ ansible_date_time.date }}\\n\"\r\n dest: \/var\/www\/html\/index.html<\/pre>\n[student@workstation dev-vars-inclusions]$ ansible-playbook playbook.yml\r\nPLAY ***********************************************************************\r\nTASK [setup] ***************************************************************\r\nok: [servera.lab.example.com]\r\nTASK [Include the variables from the YAML file] ****************************\r\nok: [servera.lab.example.com]\r\nTASK [Include the environment file and set the variables] ******************\r\nincluded: \/home\/student\/dev-vars-inclusions\/tasks\/environment.yml for\r\nservera.lab.example.com\r\nTASK [Install and start the web server] ************************************\r\nchanged: [servera.lab.example.com]\r\nTASK [Start the service] ***************************************************\r\nchanged: [servera.lab.example.com]\r\nTASK [Install the firewall] ************************************************\r\nchanged: [servera.lab.example.com]\r\nTASK [Start the firewall] **************************************************\r\nchanged: [servera.lab.example.com]\r\nTASK [Open the port for http] **********************************************\r\nchanged: [servera.lab.example.com]\r\nTASK [Create index.html] ***************************************************\r\nchanged: [servera.lab.example.com]\r\nPLAY RECAP *****************************************************************\r\nservera.lab.example.com : ok=9 changed=4 unreachable=0 failed=0<\/pre>\n
\nindex.html<\/code> has been created, the output should appear as follows:<\/p>\n[student@workstation dev-vars-inclusions]$ curl http:\/\/servera.lab.example.com\r\nservera.lab.example.com has been customized using Ansible on the 2016-03-31<\/pre>\n
packages<\/code> and define two facts: one called db_package<\/code>, with a value of mariadb-server<\/code>, and one called web_package<\/code>, with a value of httpd<\/code>. Create a section called services with two facts: one called db_service<\/code>, with a value of mariadb<\/code>, and one called web_service<\/code>, with a value of httpd<\/code>.
\nDefine a playbook, called setup_facts.yml, that will install the facts on serverb.<\/p>\ncustom.fact<\/code>. The file should appear as follows:<\/p>\n[packages]\r\ndb_package = mariadb-server\r\nweb_package = httpd\r\n\r\n[services]\r\ndb_service = mariadb\r\nweb_service = httpd<\/pre>\n
setup_facts.yml<\/code> playbook to install the facts on the managed host, serverb.lab.example.com. Use the file and copy modules to install the custom facts. The playbook should appear as follows:<\/p>\n---\r\n- name: Install remote facts\r\n hosts: lamp\r\n vars:\r\n remote_dir: \/etc\/ansible\/facts.d\r\n facts_file: custom.fact\r\n tasks:\r\n - name: Create the remote directory\r\n file:\r\n state: directory\r\n recurse: yes\r\n path: \"{{ remote_dir }}\"\r\n - name: Install the new facts\r\n copy:\r\n src: \"{{ facts_file }}\"\r\n dest: \"{{ remote_dir }}\"<\/pre>\n[student@workstation lab-managing-vars]$ ansible-playbook setup_facts.yml\r\nPLAY [Install remote facts] ************************************************\r\nTASK [setup] ***************************************************************\r\nchanged: [serverb.lab.example.com]\r\nTASK [Create the remote directory] *****************************************\r\nok: [serverb.lab.example.com]\r\nTASK [Install the new facts] ***********************************************\r\nchanged: [serverb.lab.example.com]\r\nPLAY RECAP *****************************************************************\r\nserverb.lab.example.com : ok=3 changed=2 unreachable=0 failed=0<\/pre>\n
[student@workstation lab-managing-vars]$ ansible lamp -m setup -a\r\n'filter=ansible_local*'\r\nserverb.lab.example.com | SUCCESS => {\r\n\"ansible_facts\": {\r\n\"ansible_local\": {\r\n\"custom\": {\r\n\"packages\": {\r\n\"db_package\": \"mariadb-server\",\r\n\"web_package\": \"httpd\"\r\n},\r\n\"services\": {\r\n\"db_service\": \"mariadb\",\r\n\"web_service\": \"httpd\"\r\n}\r\n}\r\n}\r\n},\r\n\"changed\": false\r\n}<\/pre>\n[student@workstation lab-managing-vars]$ mkdir vars<\/pre>\n
vars\/main.yml<\/code>. The file should contain the following content:<\/p>\n---\r\nweb_root: \/var\/www\/html<\/pre>\n
main.yml<\/code>, that instructs Ansible to install both the web server package and the database package using facts Ansible gathered from serverb.lab.example.com. When they are installed, start the two services.<\/p>\n[student@workstation lab-managing-vars]$ mkdir tasks<\/pre>\n
tasks\/main.yml<\/code>. The tasks should install both the database and the web server, and start the services httpd<\/em> and mariadb<\/em>. Use the custom Ansible facts for the name of the services to manage. The file should appear as follows:<\/p>\n---\r\n- name: Install and start the database and web servers\r\n yum:\r\n name:\r\n - \"{{ ansible_local.custom.packages.db_package }}\"\r\n - \"{{ ansible_local.custom.packages.web_package }}\"\r\n state: latest\r\n- name: Start the database service\r\n service:\r\n name: \"{{ ansible_local.custom.services.db_service }}\"\r\n state: started\r\n enabled: true\r\n- name: Start the web service\r\n service:\r\n name: \"{{ ansible_local.custom.services.web_service }}\"\r\n state: started\r\n enabled: true<\/pre>\nplaybook.yml<\/code> in the top-level directory for this lab. The playbook should be in the following order: target the lamp hosts groups and define a new variable, firewall with a value of firewalld.
\nCreate the following tasks:
\n\u2022 A task that includes the variable file main.yml<\/code>.
\n\u2022 A task that includes the tasks defined in the tasks file.
\n\u2022 A task for installing the latest version of the firewall package.
\n\u2022 A task for for starting the firewall service.
\n\u2022 A task for opening TCP port 80 permanently.
\n\u2022 A task that uses the copy module to create the index.html<\/code> page in the directory the variable defines.
\nThe index.html should appear as follows:<\/p>\nserverb.lab.example.com (172.25.250.11) has been customized by Ansible<\/pre>\n
[student@workstation lab-managing-vars]$ tree\r\n.\r\n\u251c\u2500\u2500 ansible.cfg\r\n\u251c\u2500\u2500 custom.fact\r\n\u251c\u2500\u2500 inventory\r\n\u251c\u2500\u2500 playbook.yml\r\n\u251c\u2500\u2500 setup_facts.yml\r\n\u251c\u2500\u2500 tasks\r\n\u2502 \u2514\u2500\u2500 main.yml\r\n\u2514\u2500\u2500 vars\r\n\u2514\u2500\u2500 main.yml\r\n2 directories, 7 files<\/pre>\n
---\r\n- hosts: lamp\r\n vars:\r\n firewall: firewalld\r\n tasks:\r\n - name: Include the variable file\r\n include_vars: vars\/main.yml\r\n - name: Include the tasks\r\n include: tasks\/main.yml\r\n - name: Install the firewall\r\n yum:\r\n name: \"{{ firewall }}\"\r\n state: latest\r\n - name: Start the firewall\r\n service:\r\n name: \"{{ firewall }}\"\r\n state: started\r\n enabled: true\r\n - name: Open the port for the web server\r\n firewalld:\r\n service: http\r\n state: enabled\r\n immediate: true\r\n permanent: true\r\n - name: Create index.html\r\n copy:\r\n content: \"{{ ansible_fqdn }}({{ ansible_default_ipv4.address }}) has been customized by Ansible\\n\"\r\n dest: \"{{ web_root }}\/index.html\"<\/pre>\nweb_root<\/code>, defined in the variables file, for the home directory of the web server.<\/p>\n playbook.yml<\/code> created in the previous step.<\/p>\n[student@workstation lab-managing-vars]$ ansible-playbook playbook.yml\r\nPLAY ***********************************************************************\r\n... Output omitted ...\r\nPLAY RECAP *****************************************************************\r\nserverb.lab.example.com : ok=10 changed=5 unreachable=0 failed=0\r\n<\/pre>\n
[student@workstation lab-managing-vars]$ curl http:\/\/serverb\r\nserverb.lab.example.com(172.25.250.11) has been customized by Ansible<\/pre>\n
[student@workstation lab-managing-vars]$ ansible lamp -a 'systemctl status\r\nmariadb'\r\nserverb.lab.example.com | SUCCESS | rc=0 >>\r\n\u25cf mariadb.service - MariaDB database server\r\nLoaded: loaded (\/usr\/lib\/systemd\/system\/mariadb.service; disabled; vendor\r\npreset: disabled)\r\nActive: active (running) since Fri 2016-04-01 10:50:40 PDT; 7min ago\r\n... Output omitted ...<\/pre>\n