Ansible Lab

Network Diagram

Host Machine Setup

1. Enable Hyper-V
2. Install Vagrant
3. Install Git
4. Add your user to the list of Hyper-V Administrators. This will allow you to use vagrant without opening an Administrative PowerShell prompt.
5. Clone repo using git clone git@github.com:estenrye/ansible-rancher-lab.git

Launching the Ansible Control Server and Lab Router

The vagrant driver for Hyper-V lacks two components that allow us to have a predictable lab setup. The first is that the Hyper-V vagrant driver does not provide a mechanism for specifying multiple Network Interface Adapters on a guest VM. The second is that the Hyper-V vagrant driver does not provide a mechnanism for specifying a static IP address for a guest VM on any network type. This project addresses the first problem by using a combination of vagrant commands and PowerShell commandlets to add a second Network Interface Adapter to the router guest VM. It addresses the second by dynamically generating the inventory on the host machine and copying it to the acs guest VM.

0. ./scripts/OneTimeSetup.ps1
1. vagrant up openvas router
2. vagrant halt router
3. Add-VMNetworkAdapter -VMName router.rz.lab -SwitchName Private -Name LAN
4. Start-VM router.rz.lab
5. ./scripts/Generate-Ansible-Inventory.ps1
6. vagrant ssh openvas -c "ansible-playbook -i inventory --become playbooks/network.yml"
7. vagrant up acs utility dc docker-manager docker-worker
8. vagrant ssh acs -c "ansible-playbook -i rz_lab_inventory --become playbooks/net-plan.internal.yml"
9. vagrant ssh acs -c "ansible-playbook -i rz_lab_inventory --become playbooks/site.yml"
10. Wait for ELK Stack to fully deploy and initialize before proceeding. http://utility.rz.lab:5601
11. vagrant ssh acs -c "ansible-playbook -i rz_lab_inventory --become playbooks/beats.yml"

References

Much of this project wouldn't be, if not for the great contributions of others. Please check out their sites in the references.