DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
| 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 |
| 5 | Verify monitor service after stop/start VR | 1.Verify monitoring services tool functionality 2.Stop and start VR 3.Repeat step3 | Monitoring VR services tool should work as expected before and after VR stop/star |
| 6 | Verify monitor service after VR restart | 1.Verify monitoring services tool functionality 2.Restart VR 3.Repeate step3 | Monitoring VR services tool should work as expected before and after VR restart |
| 7 | Verify monitor service after destroy and recreate VR | 1.Verify monitoring services tool functionality 2.Destroy and recreate VR 3.Repeat step3 | Monitoring VR services tool should work as expected before and after VR destroy and recreate |
| 8 | Monitor services with multiple Networks with different network offerings | 1.Create multiple network offerings with different services e.g: NO1:dhcp,dns,Loadbalancing,userdata,sourcenat,firewall NO2: dhcp,dns,userdata,sourcenat,firewall 3.Create networks N1,N2 using above network offerings 4.Verify monitoring services tool functionality in both the VRs in each network N1 and N2 | Monitor VR services tool should work as expected in both the networks |
| 9 | Verify monitor service in a mixed zone env | 2.Create network N1 with dhcp,dns and userdata in zone z1 3.Create network N2 with dhcp,dns,userdata,password,loadbalancing,sourcenat and firewall in zone z2 4.Verify monitoring services tool functionality in both the VRs in each zone z1 and z2 | VR services monitoring tool should work as expected in both the zones |
| 10 | Monitor VR service after network restart | 1.Create a network with dhcp,dns,userdata,password,loadbalancing,sourcenat and firewall services 2.Deploy VR in the above network 3.Restart network and verify VR services monitoring tool functionality | Tool should work as expected before and after network restart |
Overview
Content Tools