From b4c088c6a4215a8aea2da306c4bc7fe616f6bce6 Mon Sep 17 00:00:00 2001 From: Tee Ngo Date: Fri, 26 Jul 2019 17:53:13 -0400 Subject: [PATCH] Define alarm group, type and ids for application The newly introduced fault constants will be used to raise and clear application related alarms. Closes-Bug: 1833323 Change-Id: I992ab7a788cfab8d52d2e6a498519c591148f588 Signed-off-by: Tee Ngo --- fm-api/fm_api/constants.py | 9 +++++++ fm-doc/fm_doc/events.yaml | 53 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 62 insertions(+) diff --git a/fm-api/fm_api/constants.py b/fm-api/fm_api/constants.py index 3c6948e1..b0ee2f35 100755 --- a/fm-api/fm_api/constants.py +++ b/fm-api/fm_api/constants.py @@ -37,6 +37,7 @@ FM_ENTITY_TYPE_PV = 'pv' FM_ENTITY_TYPE_BGP_PEER = "bgp-peer" FM_ENTITY_TYPE_STORAGE_BACKEND = 'storage_backend' FM_ENTITY_TYPE_SUBCLOUD = 'subcloud' +FM_ENTITY_TYPE_APPLICATION = 'k8s_application' # alarm service sub entity values FM_SERVICE_NETWORKING = 'networking' @@ -56,6 +57,7 @@ ALARM_GROUP_HA = "400" ALARM_GROUP_SECURITY = "500" ALARM_GROUP_LICENSING = "600" ALARM_GROUP_VM = "700" +ALARM_GROUP_APPLICATION = "750" ALARM_GROUP_STORAGE = "800" ALARM_GROUP_SW_MGMT = "900" @@ -144,6 +146,13 @@ FM_ALARM_ID_VM_GUEST_HEARTBEAT = ALARM_GROUP_VM + ".015" FM_ALARM_ID_VM_MULTI_NODE_RECOVERY_MODE = ALARM_GROUP_VM + ".016" FM_ALARM_ID_VM_GROUP_POLICY_CONFLICT = ALARM_GROUP_VM + ".017" +# Application alarm id +FM_ALARM_ID_APPLICATION_UPLOAD_FAILED = ALARM_GROUP_APPLICATION + ".001" +FM_ALARM_ID_APPLICATION_APPLY_FAILED = ALARM_GROUP_APPLICATION + ".002" +FM_ALARM_ID_APPLICATION_REMOVE_FAILED = ALARM_GROUP_APPLICATION + ".003" +FM_ALARM_ID_APPLICATION_APPLYING = ALARM_GROUP_APPLICATION + ".004" +FM_ALARM_ID_APPLICATION_UPDATING = ALARM_GROUP_APPLICATION + ".005" + # VM log id FM_LOG_ID_VM_ENABLED = ALARM_GROUP_VM + ".101" FM_LOG_ID_VM_FAILED = ALARM_GROUP_VM + ".102" diff --git a/fm-doc/fm_doc/events.yaml b/fm-doc/fm_doc/events.yaml index 2c0bd6ae..2a8c8f09 100755 --- a/fm-doc/fm_doc/events.yaml +++ b/fm-doc/fm_doc/events.yaml @@ -2626,6 +2626,59 @@ Probable_Cause: unspecified-reason Service_Affecting: False +#--------------------------------------------------------------------------- +# APPLICATION +#--------------------------------------------------------------------------- + +750.001: + Type: Alarm + Description: "Application Upload Failure" + Entity_Instance_ID: k8s_application= + Severity: warning + Proposed_Repair_Action: "Check system inventory log for cause." + Alarm_Type: processing-error + Probable_Cause: unknown + Service_Affecting: False + +750.002: + Type: Alarm + Description: "Application Apply Failure" + Entity_Instance_ID: k8s_application= + Severity: major + Proposed_Repair_Action: "Retry applying the application. If the issue persists, please check system inventory log for cause." + Alarm_Type: processing-error + Probable_Cause: unknown + Service_Affecting: True + +750.003: + Type: Alarm + Description: "Application Remove Failure" + Entity_Instance_ID: k8s_application= + Severity: major + Proposed_Repair_Action: "Retry removing the application. If the issue persists, please check system inventory log for cause." + Alarm_Type: processing-error + Probable_Cause: unknown + Service_Affecting: True + +750.004: + Type: Alarm + Description: "Application Apply In Progress" + Entity_Instance_ID: k8s_application= + Severity: warning + Proposed_Repair_Action: "No action required." + Alarm_Type: other + Probable_Cause: unknown + Service_Affecting: True + +750.005: + Type: Alarm + Description: "Application Update In Progress" + Entity_Instance_ID: k8s_application= + Severity: warning + Proposed_Repair_Action: "No action required." + Alarm_Type: other + Probable_Cause: unknown + Service_Affecting: True #--------------------------------------------------------------------------- # STORAGE