VR Service Failure Alerting

Check if monitorServerices.py is running  as a cron job for

every 3 minutes A-"crontab -l"

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  and /var/log/routerServiceMonitor.log file inside VR

3-After 30 minute(depend on GP) alert should be generated in  MS ,

MsLogs should shows these alerts with router times tamp

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

Monitoring services after

network update

1-Record services in /etc/monitor.conf file

2-change VR Network  offering

1-after step 2 check /etc/monitor.conf it should have

processes according to new SO

2-stop few services and check for alert in Ms and MS logs.

1.Check monitoring tool and alerting

2.Stop and start VR

3.Repeat step1

1-Monitoring VR services tool should work as expected before and after VR stop/star

2-Alert generation should work as expected before and after stop/start

1.Check monitoring tool and alerting

2.Restart VR

3.Repeate step1

1-Monitoring VR services tool should work as expected before and after VR restart

2-Alert generation should work as expected before and after restart

1.Verify monitoring services tool functionality

2.Destroy and recreate VR

3.Repeat step3

1-Monitoring VR services tool should work as expected before and after VR destroy and recreate

2-Alert generation should work as expected before and after .

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

1-Monitor VR services tool should work as expected in both the networks

2-Alert generation should work as expected in both networks

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

1-VR services monitoring tool should work as expected in both the zones

2-Alert generation should work as expected in both zones

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

1-Tool should work as expected before and after network restart

2-Alert generation should work as expected before and 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 with cleanup enabled and verify VR services monitoring tool functionality

1-Tool should work as expected before and after network restart with cleanup enabled

2-Alert generation should work as expected before and after network restart.

Pass

1.Create a shared network with 3 or IP addresses with dhcp,dns and userdata services

2.Deploy guest vms in the above network and make sure that all the IP addresses are used up in the shared network

3.Add few more IP addresses to the shared network in a different CIDR but in the same vlan

4.Deploy one vm in the same shared network.

5.After step5 ip alias would be created on VR and dnsmasq,apache2 services would also bind to alias ip address

6.Kill one of the dnsmasq and apache2 processes and verify the tool functionality

1-After step7 tool should bring up the processes killed.

2-Alert should be generated

2.Create a netowrk with dhcp,dns,userdata,loadbalancing,sourcenat and firewall services

3.Deploy guest vms in the above network

4.Register a new routing template

5.Change the global setting parameter to use this new template for the VRs and restart MS

6.Repeat step2 and 3

7.Verify tool functionality in both the VRs

1-Tool should work as expected in both the VRs

2-Alert should be generated properly.

1.Create a netowrk with dhcp,dns,userdata,loadbalancing,sourcenat and firewall services

2.Deploy guest vms in the above network

3.In VR's /etc/monitor.conf change dnsmasq process name to dnsmas and in monitorServices.py script change unmoint interval to a small value say 3min.

4.Kill dnsmasq process

5.Verify that after 3 mins. dnsmasq process will be unmonitored

1-process should be unmoinited by the tool if it fails to bring up the process after several attempts and log/alert  should be generated.

1.Create a netowrk with dhcp,dns,userdata,loadbalancing,sourcenat and firewall services

2.Deploy guest vms in the above network

3.Upgrade to 4.4

4.Verify tool functionality

1-check for table "op_router_moniter_service" in db

2-check for  time stamp and router id

3-after log generation check if time stamp is getting updated

1-Table should be present

2-both field should be there

3-time stamp should get updated

1-check log file size.

2-check number of backed up log files

1-size should be 10MB

2-not more than five files should be backed up