Fixes #221: Final tweaks to orchestration testing.

Author: geerlingguy

orchestration/README.md

@@ -4,7 +4,7 @@ Ansible playbooks are flexible and powerful. But sometimes, you just need to run
 
 Just like the device in Ender's Game, the `ansible` command allows you to run commands or call Ansible modules immediately on one or one hundred of servers.
 
-This simple Vagrantfile configures three Virtual Machines using Vagrant and VirtualBox: `app1`, `app2`, and `db`, to emulate a small-scale real-world infrastructure (two application servers and a database server), so you can practice running `ansible` commands across them, and work on a flexible Ansible inventory.
+This project configures three Virtual Machines using Vagrant and VirtualBox: `app1`, `app2`, and `db`, to emulate a small-scale real-world infrastructure (two application servers and a database server), so you can practice running `ansible` commands across them, and work on a flexible Ansible inventory.
 
 ## Quick Start Guide
 

orchestration/scripts/multi.sh

@@ -4,11 +4,10 @@
 set -e
 
 # Other commands from the book.
+ansible multi -b -m yum -a "name=chrony state=present"
 ansible multi -m stat -a "path=/etc/environment"
 ansible multi -m copy -a "src=/etc/hosts dest=/tmp/hosts"
 ansible multi -b -m fetch -a "src=/etc/hosts dest=/tmp"
 ansible multi -m file -a "dest=/tmp/test mode=644 state=directory"
 ansible multi -m file -a "dest=/tmp/test state=absent"
 ansible multi -b -B 3600 -P 0 -a "yum -y update"
-# ansible multi -b -a "tail /var/log/messages"
-# ansible multi -b -m shell -a "tail /var/log/messages | grep ansible-command | wc -l"