working with ad-hoc commands
This commit is contained in:
46
README.md
46
README.md
@@ -6,6 +6,8 @@ Red Hat Certified Specialist in Ansible Automation (EX407) Preparation Course
|
|||||||
- [Understanding Core Components of Ansible Part 2](#understanding-core-components-of-ansible-part-2)
|
- [Understanding Core Components of Ansible Part 2](#understanding-core-components-of-ansible-part-2)
|
||||||
- [A Brief Tour of the Ansible Configuration File](#a-brief-tour-of-the-ansible-configuration-file)
|
- [A Brief Tour of the Ansible Configuration File](#a-brief-tour-of-the-ansible-configuration-file)
|
||||||
- [LAB Getting Started with Ansible](#lab-getting-started-with-ansible)
|
- [LAB Getting Started with Ansible](#lab-getting-started-with-ansible)
|
||||||
|
- [Run Ad-Hoc Ansible Commands](#run-ad-hoc-ansible-commands)
|
||||||
|
- [Run Ad-Hoc Ansible Commands](#run-ad-hoc-ansible-commands)
|
||||||
|
|
||||||
## Understanding Core Components of Ansible
|
## Understanding Core Components of Ansible
|
||||||
### Understanding Core Components of Ansible Part 1
|
### Understanding Core Components of Ansible Part 1
|
||||||
@@ -189,4 +191,46 @@ ansible ALL=(ALL) NOPASSWD: ALL
|
|||||||
- `ansible -i /home/ansible/inventory node1 -m ping`
|
- `ansible -i /home/ansible/inventory node1 -m ping`
|
||||||
- `ansible -i /home/ansible/inventory node2 -m ping`
|
- `ansible -i /home/ansible/inventory node2 -m ping`
|
||||||
- To redirect output of a successful command to `/home/ansible/output`:
|
- To redirect output of a successful command to `/home/ansible/output`:
|
||||||
- `ansible -i /home/ansible/inventory node1 -m ping > /home/ansible/output`
|
- `ansible -i /home/ansible/inventory node1 -m ping > /home/ansible/output`
|
||||||
|
|
||||||
|
|
||||||
|
## Run Ad-Hoc Ansible Commands
|
||||||
|
### Run Ad-Hoc Ansible Commands
|
||||||
|
Learn how to use ad-hoc ansible commands for simple system managment. This lecture covers one of the key objectives for Red Hat exam 407.
|
||||||
|
|
||||||
|
- Overview:
|
||||||
|
- What is an ad-hoc command in Ansible?
|
||||||
|
- Use cases for ad-hoc commands
|
||||||
|
- Ad-hoc vs Playbook
|
||||||
|
- Ansible command syntax
|
||||||
|
- Common modules
|
||||||
|
|
||||||
|
- What is an ad-hoc command in Ansible
|
||||||
|
- You can run ansible either ad-hoc or as a playbook
|
||||||
|
- Both methods have the same capabilities
|
||||||
|
- Ad-hoc commands are effectively one-liners
|
||||||
|
|
||||||
|
- Use cases for Ad-hoc
|
||||||
|
- Operational commands
|
||||||
|
- Checking log contents
|
||||||
|
- Daemon control
|
||||||
|
- Process management
|
||||||
|
- Informational commands
|
||||||
|
- Check installed software
|
||||||
|
- Check system properties
|
||||||
|
- Gather system performance information
|
||||||
|
- Research
|
||||||
|
- Work with unfamiliar modules on test systems
|
||||||
|
- Practice for playbook engineering
|
||||||
|
|
||||||
|
##### Ad-hoc vs Playbook
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
##### Common Modules
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
BIN
images/img2.png
Normal file
BIN
images/img2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 287 KiB |
BIN
images/img3.png
Normal file
BIN
images/img3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 70 KiB |
BIN
images/img4.png
Normal file
BIN
images/img4.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
BIN
images/img5.png
Normal file
BIN
images/img5.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
Reference in New Issue
Block a user