###########################
###########################
- Place vagrantfile and all .sh scripts into a folder.
- Navigate to this folder through git bash.
- Execute command 'vagrant up' and wait.
- Congraulations your master and agents are communicating and pulling configuration changes every 5 minutes!*
*nexus does not work on CentOS, jenkins must be manually started on CentOS, LAN must be changed to area 200 in order to view jenkins and jira browsers
#################################
#################################
- Place vagrantfile and all .sh scripts into a folder.
- Navigate to this folder through git bash.
- Execute command 'vagrant up' and wait.
- Once the entire installation is complete the Enterprise console can be accessed at (to sign certificates and use MCollective): https:// 192.168.1.250
- Or to sign certificates log onto the master VM and execute 'sudo puppet cert sign --all'
- To access zabbix go to '192.168.1.250/zabbix' User = admin, Password = zabbix
- On the master turn the zabbix agent on: 'sudo service zabbix-agent start'. NB: wait for master-agent to do a puppet run in order to install zabbix agent
- On the Zabbix browser page naviagte to 'Configuration' along the top bar.
- Click 'Hosts' on the navbar underneath.
- On the far right click on 'not monitored' and switch to enable for 'Name = zabbix server'
- Click on the actual name ' Zabbix server' - Edit the top Name box to 'masterevilcorp.evilcorp.com' - inside the agent field add all IPs: 192.168.1.250 192.168.1.251 192.168.1.253