Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
16.0.4, 17.0.0
-
None
-
Security Level: Default (Default Security Scheme)
Description
When managing/unmanaging services/interfaces the logic currently implemented is a bit maintenance unfriendly.
Basically we have two implementations:
./opennms-webapp/src/main/java/org/opennms/web/admin/nodeManagement/ManageNodesServlet.java
./opennms-webapp/src/main/java/org/opennms/web/admin/nodeManagement/ManageNodeServlet.java
Both do more or less the same.
In addition both implementations send different events.
The goal is to verify if both servlets can be unified.
In addition it should be verified which events should be sent.
I talked to Jeff about this and it seems that both implementations may not be optimal.
The following events should be send:
1. manage/unmanage a service
A serviceManaged or serviceUnmanaged event
2. manage/unmanage an interface
A interfaceManaged or interfaceUnmanaged event
3. resume/suspend poller
whenever a service changes from unmanaged to managed a POLLER RESUME event must be send
whenever a service changes from managed to unmanaged a POLLER SUSPEND event must be send.
Attachments
Issue Links
- blocks
-
NMS-7828 NPE on "manage and unmanage services and interfaces"
-
- Resolved
-