You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2014/11/11 17:10:37 UTC

[jira] [Updated] (AMBARI-8276) Alerts: Remove Nagios Service From The Stack

     [ https://issues.apache.org/jira/browse/AMBARI-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hurley updated AMBARI-8276:
------------------------------------
    Attachment: AMBARI-8276.patch

> Alerts: Remove Nagios Service From The Stack
> --------------------------------------------
>
>                 Key: AMBARI-8276
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8276
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8276.patch
>
>
> With the new alerting framework in place, the Nagios stack files can start to be removed. This involves many different steps between the server, the web client, and the agent.
> In this Jira, we will track the removal of the stack resources. This means:
> - Remove files in src/main/resources/stacks/*/services/NAGIOS
> - Remove files in test/main/resources/stacks/*/services/NAGIOS
> - Associated tests that depend on Nagios must be either removed if irrelevent or rewritten
> This effort should leave Ambari in a state where the web client and blueprints can still successfully install a non-Nagios cluster. Once installed, the cluster will operate normally with the exception that alerts will not be surfaced by the web client until they have switched over to the new alert framework.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)