Where to start First steps track · 15 stages
Linux Labs

Task → recipe

Recipes: 522. A task and the commands that solve it.

Basic commands

Files and directories

Text and search

Users and permissions

Processes

Services and systemd

Network

Storage and file systems

Logs and audit

Boot

Packages

Security

Automation

  • Check a playbook before running it {#before-run} On a correct playbook --syntax-check prints only playbook: ansible-playbook: running a playbook
  • To another machine over SSH {#remote} The inventory node2.ini: ansible-playbook: running a playbook
  • Part of a playbook {#partial} With -t page the fact gathering, the tagged task and its handler ran — ok=3 changed=2. ansible-playbook: running a playbook
  • A variable from the command line {#extra-vars} -e site_title=Changed overrides the playbook's vars:: ansible-playbook: running a playbook
  • Inventory {#inventory} What Where Means machine name node2 how the machine is named in the output; Ansible also connects by it if there is no ansible_host ansible_host the machine's… Ansible: inventory, modules and one-off commands
  • One-off commands {#adhoc} ansible <machines> -m <module> -a '<arguments>' runs one module on all machines of a group. Ansible: inventory, modules and one-off commands
  • become: through sudo {#become} Modules run as the user Ansible logged in as. Ansible: inventory, modules and one-off commands
  • Playbooks and roles Variables go in group_vars/, host_vars/; secrets in ansible-vault (ansible-vault encrypt secrets.yml, run with --ask-vault-pass). Ansible: inventory, modules and one-off commands

Containers

Nothing found. Try a shorter query.

Loading…