[ https://issues.apache.org/jira/browse/AMBARI-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206693#comment-14206693 ]
Hadoop QA commented on AMBARI-8276: ----------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12680808/AMBARI-8276.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 54 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/600//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/600//console This message is automatically generated. > 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)