With the current version scheme and development paradigm for OpenNMS Horizon, it is difficult to maintain extensions to configuration and components outside of the main source tree.
In order to make it easier to write "plugins" and extensions to OpenNMS, we would like to introduce a standalone API against which such components can be written.
This API will be versioned separately from OpenNMS, making it possible to target an API version, rather than a particular OpenNMS Horizon and/or OpenNMS Meridian version.
In scope for v1.0.0 will be all facilities necessary for building the OCE (OpenNMS Correlation Engine) and other interfaces we deem useful as time permits.
With the current version scheme and development paradigm for OpenNMS Horizon, it is difficult to maintain extensions to configuration and components outside of the main source tree.
In order to make it easier to write "plugins" and extensions to OpenNMS, we would like to introduce a standalone API against which such components can be written.
This API will be versioned separately from OpenNMS, making it possible to target an API version, rather than a particular OpenNMS Horizon and/or OpenNMS Meridian version.
In scope for v1.0.0 will be all facilities necessary for building the OCE (OpenNMS Correlation Engine) and other interfaces we deem useful as time permits.