[
https://issues.apache.org/jira/browse/AMBARI-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263296#comment-14263296
]
Hadoop QA commented on AMBARI-8970:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12689882/AMBARI-8970.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 2 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.HostStackVersionResourceProviderTest
org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProviderTest
org.apache.ambari.server.controller.AmbariManagementControllerTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1148//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1148//console
This message is automatically generated.
> Custom Actions for Namenode to execute tasks by calling a python script
> -----------------------------------------------------------------------
>
> Key: AMBARI-8970
> URL: https://issues.apache.org/jira/browse/AMBARI-8970
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.0.0
>
> Attachments: AMBARI-8970.patch
>
>
> Currently, the upgrade-2.2.xml file, which contains the Upgrade Pack, defines
> the exact commands to run for the Namenode prepare and finalize steps.
> The downside of having this logic in the xml file is that it makes it
> difficult to maintain, and is not as powerful as being able to run the
> commands by using Python and its functions. Therefore, it is preferable for
> the ExecuteTask to be able to invoke a function inside a script.
> The plan is for Namenode to have functions for prepare and finalize, and for
> the upgrade pack to contain something like,
> Masters Group,
> {code}
> <service name="HDFS">
> <component name="NAMENODE">
> <pre-upgrade>
> <task xsi:type="execute" hosts="master">
> <script>scripts/namenode.py</script>
> <function>prepare_rolling_upgrade</function>
> </task>
> </pre-upgrade>
> </component>
> </service>
> {code}
> While the Cluster Group has,
> {code}
> <execute-stage service="HDFS" component="NAMENODE" title="Execute HDFS
> Finalize">
> <task xsi:type="execute" hosts="master">
> <script>scripts/namenode.py</script>
> <function>finalize_rolling_upgrade</function>
> </task>
> </execute-stage>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
