Redefine the start ordering of the OpenNMS daemons during bootstrap.

Description

There are several OpenNMS daemons that should start as soon as Eventd is up and running, and prior the working daemons start to send events.

I'm talking about Alarmd, Bsmd, Ticketer, Correlator and Scriptd. Those daemons will react based upon events generated by Trapd, Pollerd, Collectd, Provisiond, etc.

For this reason, I propose to move the daemons (i.e. Alarmd, Bsmd, Ticketer, Correlator and Scriptd) to be after Eventd and before Trapd inside service-configuration.xml.

The main reason is to be ready after starting OpenNMS to start processing events prior the working daemons start pushing those events to the Event Bus, and also because some of the working daemons might delay the startup time on medium to big installations.

We already have several customers using this approach.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Alejandro Galue April 14, 2017 at 1:17 PM

Fixed

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created April 11, 2017 at 3:08 PM
Updated May 2, 2017 at 3:56 PM
Resolved April 19, 2017 at 11:07 AM