Re-implement the scheduled outages configuration page with Angular
Description
Acceptance / Success Criteria
has to be started together with
Lucidchart Diagrams
Activity
Alejandro Galue October 3, 2017 at 12:17 PM
The correct question would be: will the implementation of this new feature fix the problem reported on ? That's because the implementation mentioned here doesn't exist. Now, considering that we're talking about a brand new implementation of this feature that is completely unrelated with the current workflow, I would say: yes, it will address every single problem reported on the current workflow with a completely new workflow.
John Blackburn October 3, 2017 at 2:17 AM
Does the implementation of this issue address the problem reported in NMS-9646?
Ron Roskens February 26, 2017 at 7:35 PM
The current sched-outages page displays whether each outage affects notifications, polling, thresholds, and data collection.
The ReST interface (rest/sched-outages) does not return this data, nor is there a ReST page to query whether an outage affects which one.
Ron Roskens February 20, 2017 at 4:43 PM
Improvements that would be nice to have:
Search for nodes within a category
Add all nodes in a category
Search for nodes within provisioning requistion
Add all nodes in a provisioning requistion
The page used to configure scheduled outages is confusing as it requires several non obvious steps to properly configure a maintenance window.
There is a ReST end point to manage the scheduled outages which is the only requirement for any JS Framework like Angular.
Probably this ReST end point has to be revisited to ensure it works with JSON, and it can also provide the available packages configured for all the different services, which I think is not implemented yet.