Be able to use the ReST end-point for scheduled outages to manipulate them.
The current implementation relies on Node ID (primary-key of the node's table in the database) or IP addresses. It would be nice to be able to use node-labels, foreign-source/foreign-id combination when adding or visualizing scheduled outages to improve user experience.
To do this, the idea is to translate NodeID/IP to NodeLabel back and forward. During this computation, the tool can detect if the provided NodeID/IP is valid or not.
Speaking of invalid entries, it would be nice to have an option to clean past entries and verify if there are currently nodes that are being impacted by scheduled outages.
Finally, when "adding" nodes to a new outage, we could specify a filter and include all of the nodes that match it to simplify the configuration.
Be able to use the ReST end-point for scheduled outages to manipulate them.
The current implementation relies on Node ID (primary-key of the node's table in the database) or IP addresses. It would be nice to be able to use node-labels, foreign-source/foreign-id combination when adding or visualizing scheduled outages to improve user experience.
To do this, the idea is to translate NodeID/IP to NodeLabel back and forward. During this computation, the tool can detect if the provided NodeID/IP is valid or not.
Speaking of invalid entries, it would be nice to have an option to clean past entries and verify if there are currently nodes that are being impacted by scheduled outages.
Finally, when "adding" nodes to a new outage, we could specify a filter and include all of the nodes that match it to simplify the configuration.