| TestCase ID | TestCase name | Steps | Expected Result |
|---|---|---|---|
| 1 | Monitoring services in VR | Check if monitorServerices.py is running as a cron job for every 3 minutes A-"crontab -l" | output should be: root@r-4-VM:~# crontab -l SHELL=/bin/bashPATH=/usr/local /sbin:/usr/local/bin:/sbin :/bin:/usr/sbin:/usr/bin */3 * * * * /usr/bin/python /root/monitorServices.p |
| 2 | Verify process restart and logging function | 1-Login to VR and stop one or more processes listed in /etc/monitor.conf file 2-Verify that the processes will be started by the monitor service when it starts by cron job | 1-All the processes should be started after step 2 which are stopped in step1 . 2.An INFO event should be logged in /var/log/messages file inside VR 3-After 30 minute(depend on GP) alert should be generated in MS and and MsLogs should shows these alerts |
| 3 | Map services in networkoffering with config file | 1.Create a Network Offering with just dhcp,dns and source NAT services 2.Create Isolated guest network with the above network offering 3.Deploy one guest vm with default cent os template and with the network created in previous step 5.Login to VR and processes listed in /etc/monitor.conf file | Processes with daemons in the network offering and processes mentioned in /etc/monitor.conf in VR should match |
| 4 | Monitoring services after network update | 1-Record services in /etc/monitor.conf file 2-change Vr service offering | 1-after step 2 check /etc/monitor.conf it should have processes according to new SO |