Service monitoring tool in Virtual Router

FS Reference: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Monitoring+VR+services

Test Scope

The goal for this feature is to monitor all the VR services and ensure they are running through the lifetime of VR

On service failure monitor script does the following:

1. write syslog log about service fail and Restart the service.

2. If the restart fails, writes an event log in in syslog.

Networks supported:

1.Isolated

2.Shared (Both Basic and Advanced zone)

3.VPC (as from CloudStack 4.14)

Out of Scope

RVR

Failure Notification

Monitoring of VR services without daemons (e.g. SourceNAT,StaticNAT,PortForwarding,Firewall,VPN....)

Test Scenarios

Following scenarios will be executed on both Shared and Isolated Networks and across different hypervisors.

1. Create Network and verify Monitoring Service inside the VR

2.Simulate process crash and verify restart and logging functions

3.Update network offering and verify the list of services

4.Verify Monitoring Service status after stop/start, Restart, Destroy/Recreate VR

5.Create Multiple Networks with different Network offerings and verify the list of services to monitor in each VR

6.Mixed zone setup(Isolated and Shared)

7.Network restart with/without cleanup and verify monitoring Service in VR

8.After Upgrade from pre-4.3 to 4.3 verify the monitoring service functionality in exiting and new VRs

9.Running multiple instances of the same process(e.g apache2) in VR

10.In a running setup register Routing template and create one or more VRs with this new template and verify the monitoring functionality

11.Observing VRs performance (any degradation) due to the monitoring functionality

12.Unmonit a process if it failed to start after several attempts to start

Test Cases

Test cases for the above scenarios have been developed and updated in the following excel sheet:

Monitoring VR Services.xlsx