From df1afd6b127d215cbd6dbd254ff5e8c5090aca78 Mon Sep 17 00:00:00 2001 From: Paul Cuzner Date: Fri, 23 Oct 2020 18:31:50 +1300 Subject: [PATCH] doc/dev/cephadm: Updates following PR feedback Minor update adding an idea for future development as per suggestion from @anthonyeleven Signed-off-by: Paul Cuzner --- doc/dev/cephadm/host-maintenance.rst | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/doc/dev/cephadm/host-maintenance.rst b/doc/dev/cephadm/host-maintenance.rst index 464c1421c9c..af48dee01a6 100644 --- a/doc/dev/cephadm/host-maintenance.rst +++ b/doc/dev/cephadm/host-maintenance.rst @@ -3,7 +3,7 @@ Host Maintenance ================ All hosts that support Ceph daemons need to support maintenance activity, whether the host -is physical or virtual(vm or cloud). This means that management workflows should provide +is physical or virtual. This means that management workflows should provide a simple and consistent way to support this operational requirement. This document defines the maintenance strategy that could be implemented in cephadm and mgr/cephadm. @@ -96,5 +96,9 @@ Ideas for Future Work #. When a host is placed into maintenance, the time of the event could be persisted. This would allow the orchestrator layer to establish a maintenance window for the task and alert if the maintenance window has been exceeded. - - +#. The maintenance process could support plugins to allow other integration tasks to be + initiated as part of the transition to and from maintenance. This plugin capability could + support actions like; + + * alert suppression to 3rd party monitoring framework(s) + * service level reporting, to record outage windows