[jira] [Commented] (AMBARI-7448) Create Kerberos Service

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-7448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217561#comment-14217561
 ] 

Hudson commented on AMBARI-7448:


FAILURE: Integrated in Ambari-trunk-Commit-docker #268 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/268/])
AMBARI-7448. Create Kerberos Service. (Robert Levas via jaimin) (jaimin: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6fbfdb4a0774b64ca92760747e90f9de01db5542)
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/kerberos_common.py
* ambari-server/src/test/python/stacks/2.2/KERBEROS/test_kerberos_client.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/utils.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/kadm5-acl.xml
* ambari-server/src/test/python/stacks/2.2/KERBEROS/use_cases.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/templates/kadm5_acl.j2
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/KerberosServiceMetaInfoTest.java
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/kerberos_server.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/templates/krb5_conf.j2
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/kerberos_client.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/kdc-conf.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/krb5-conf.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/metainfo.xml
* ambari-server/src/test/python/stacks/2.2/KERBEROS/test_kerberos_server.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/templates/kdc_conf.j2
* ambari-server/src/main/java/org/apache/ambari/server/Role.java


> Create Kerberos Service
> ---
>
> Key: AMBARI-7448
> URL: https://issues.apache.org/jira/browse/AMBARI-7448
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: component, kdc, kerberos, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-7448.patch, AMBARI-7448.patch.2, 
> AMBARI-7448.patch.3, AMBARI-7448.patch.4, AMBARI-7448.patch.5, 
> AMBARI-7448.patch.6, AMBARI-7448.patch.7, AMBARI-7448.patch.8, 
> AMBARI-7448.patch.9, AMBARI-7448_10.patch, AMBARI-7448_11.patch, 
> AMBARI-7985_09.patch
>
>
> Create a service to manage the (optional) Kerberos server (managed KDC) and 
> client components.
> See [Ambari Cluster Kerberization Technical 
> Document|https://issues.apache.org/jira/secure/attachment/12671235/AmbariClusterKerberization.pdf]
>  for more information.



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

[jira] [Commented] (AMBARI-7448) Create Kerberos Service

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-7448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217551#comment-14217551
 ] 

Hudson commented on AMBARI-7448:


FAILURE: Integrated in Ambari-trunk-Commit #979 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/979/])
AMBARI-7448. Create Kerberos Service. (Robert Levas via jaimin) (jaimin: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6fbfdb4a0774b64ca92760747e90f9de01db5542)
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/krb5-conf.xml
* ambari-server/src/main/java/org/apache/ambari/server/Role.java
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/kerberos_server.py
* ambari-server/src/test/python/stacks/2.2/KERBEROS/use_cases.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/kerberos_client.py
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/KerberosServiceMetaInfoTest.java
* ambari-server/src/test/python/stacks/2.2/KERBEROS/test_kerberos_client.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/utils.py
* ambari-server/src/test/python/stacks/2.2/KERBEROS/test_kerberos_server.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/templates/kdc_conf.j2
* ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/metainfo.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/kadm5-acl.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/templates/krb5_conf.j2
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/kerberos_common.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/kdc-conf.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/templates/kadm5_acl.j2


> Create Kerberos Service
> ---
>
> Key: AMBARI-7448
> URL: https://issues.apache.org/jira/browse/AMBARI-7448
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: component, kdc, kerberos, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-7448.patch, AMBARI-7448.patch.2, 
> AMBARI-7448.patch.3, AMBARI-7448.patch.4, AMBARI-7448.patch.5, 
> AMBARI-7448.patch.6, AMBARI-7448.patch.7, AMBARI-7448.patch.8, 
> AMBARI-7448.patch.9, AMBARI-7448_10.patch, AMBARI-7448_11.patch, 
> AMBARI-7985_09.patch
>
>
> Create a service to manage the (optional) Kerberos server (managed KDC) and 
> client components.
> See [Ambari Cluster Kerberization Technical 
> Document|https://issues.apache.org/jira/secure/attachment/12671235/AmbariClusterKerberization.pdf]
>  for more information.



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

Re: Review Request 27206: Create Kerberos Service

[Jaimin Jetly]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27206/#review62136
---

Ship it!


Ship It!

- Jaimin Jetly


On Nov. 14, 2014, 10:14 a.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27206/
> ---
> 
> (Updated Nov. 14, 2014, 10:14 a.m.)
> 
> 
> Review request for Ambari, dilli dorai, Jaimin Jetly, John Speidel, Nate 
> Cole, Robert Nettleton, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-7448
> https://issues.apache.org/jira/browse/AMBARI-7448
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Create a service to manage the (optional) Kerberos server (managed KDC) and 
> client components in the HDP 2.2 stack.
> 
> See [Ambari Cluster Kerberization Technical 
> Document](https://issues.apache.org/jira/secure/attachment/12671235/AmbariClusterKerberization.pdf)
>  for more information.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/java/org/apache/ambari/server/Role.java 61a2fb9 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/kadm5-acl.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/kdc-conf.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/configuration/krb5-conf.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/metainfo.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/kerberos_client.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/kerberos_common.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/kerberos_server.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/params.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/service_check.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/scripts/utils.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/templates/kadm5_acl.j2
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/templates/kdc_conf.j2
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/KERBEROS/package/templates/krb5_conf.j2
>  PRE-CREATION 
>   
> ambari-server/src/test/java/org/apache/ambari/server/api/services/KerberosServiceMetaInfoTest.java
>  PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.2/KERBEROS/test_kerberos_client.py 
> PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.2/KERBEROS/test_kerberos_server.py 
> PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.2/KERBEROS/use_cases.py PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/27206/diff/
> 
> 
> Testing
> ---
> 
> Tests run: 2248, Failures: 0, Errors: 0, Skipped: 14
> 
> Running tests for stack:2.2 service:KERBEROS
> test_configure_cross_realm_trust (test_kerberos_client.TestKerberosClient) 
> ... ok
> test_configure_managed_kdc (test_kerberos_client.TestKerberosClient) ... ok
> test_configure_unmanaged_ad (test_kerberos_client.TestKerberosClient) ... ok
> test_configure_unmanaged_kdc (test_kerberos_client.TestKerberosClient) ... ok
> test_configure_cross_realm_trust (test_kerberos_server.TestKerberosServer) 
> ... ok
> test_configure_managed_kdc (test_kerberos_server.TestKerberosServer) ... ok
> test_configure_unmanaged_ad (test_kerberos_server.TestKerberosServer) ... ok
> test_configure_unmanaged_kdc (test_kerberos_server.TestKerberosServer) ... ok
> 
> --
> Ran 8 tests in 0.151s
> 
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 36:44 min
> [INFO] Finished at: 2014-11-13T12:28:08+00:00
> [INFO] Final Memory: 41M/412M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

[jira] [Commented] (AMBARI-8377) Alerts UI: Alert Definition API should provide a 'description' field

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217332#comment-14217332
 ] 

Hadoop QA commented on AMBARI-8377:
---

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12682248/AMBARI-8377.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 7 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/687//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/687//console

This message is automatically generated.

> Alerts UI: Alert Definition API should provide a 'description' field
> 
>
> Key: AMBARI-8377
> URL: https://issues.apache.org/jira/browse/AMBARI-8377
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8377.patch, AMBARI-8377.patch
>
>
> Alerts UI needs a title and a description for alert definitions. We have the 
> {{label}} property for the title. We need a {{description}} property to 
> describe what this alert-definition does. 
> Default alert-definitions provided in stack could have better description 
> about themselves.
> {{AlertDefinition/description}} will be added for this. We'll include 
> descriptions on {{alerts.json}} in HDFS for this Jira, and then a new Jira 
> will cover getting descriptions into the other JSON files.



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

[jira] [Commented] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217306#comment-14217306
 ] 

Hudson commented on AMBARI-8379:


FAILURE: Integrated in Ambari-trunk-Commit-docker #267 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/267/])
AMBARI-8379. Falcon lineage needs changes to startup.properties (alejandro) 
(afernandez: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=defa49b7815a39977f8c9c02a0887670bc1185e7)
* ambari-web/app/data/HDP2/site_properties.js
* 
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
* ambari-web/app/models/service_config.js


> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch, AMBARI-8379_branch-1.7.0.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

[jira] [Commented] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217301#comment-14217301
 ] 

Hudson commented on AMBARI-8379:


SUCCESS: Integrated in Ambari-branch-1.7.0-docker #175 (See 
[https://builds.apache.org/job/Ambari-branch-1.7.0-docker/175/])
AMBARI-8379. Falcon lineage needs changes to startup.properties (alejandro) 
(afernandez: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=115a7a387f300038ae2a3db0bd6f0967b06c3891)
* ambari-web/app/models/service_config.js
* 
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
* ambari-web/app/data/HDP2/site_properties.js
* 
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py


> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch, AMBARI-8379_branch-1.7.0.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

[jira] [Commented] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217299#comment-14217299
 ] 

Hudson commented on AMBARI-8379:


FAILURE: Integrated in Ambari-trunk-Commit #978 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/978/])
AMBARI-8379. Falcon lineage needs changes to startup.properties (alejandro) 
(afernandez: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=defa49b7815a39977f8c9c02a0887670bc1185e7)
* ambari-web/app/data/HDP2/site_properties.js
* 
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
* ambari-web/app/models/service_config.js
* 
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml


> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch, AMBARI-8379_branch-1.7.0.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

[jira] [Commented] (AMBARI-7872) Create stack definitions for PHD-3.0.0.0

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-7872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217294#comment-14217294
 ] 

Hadoop QA commented on AMBARI-7872:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12682268/AMBARI-7872.trunk.v2.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{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/686//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/686//console

This message is automatically generated.

> Create stack definitions for PHD-3.0.0.0
> 
>
> Key: AMBARI-7872
> URL: https://issues.apache.org/jira/browse/AMBARI-7872
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 1.7.0
>Reporter: Mahesh Kumar Vasanthu Somashekar
>Assignee: Mahesh Kumar Vasanthu Somashekar
> Fix For: 2.0.0
>
> Attachments: AMBARI-7872-branch-1.7.patch, AMBARI-7872-trunk.patch, 
> AMBARI-7872.trunk.v2.patch
>
>
> Create service definitions for PHD-3.0.0.0 stack.



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

[jira] [Commented] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217291#comment-14217291
 ] 

Hudson commented on AMBARI-8379:


SUCCESS: Integrated in Ambari-branch-1.7.0 #411 (See 
[https://builds.apache.org/job/Ambari-branch-1.7.0/411/])
AMBARI-8379. Falcon lineage needs changes to startup.properties (alejandro) 
(afernandez: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=115a7a387f300038ae2a3db0bd6f0967b06c3891)
* ambari-web/app/models/service_config.js
* ambari-web/app/data/HDP2/site_properties.js
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py


> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch, AMBARI-8379_branch-1.7.0.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

Re: Review Request 28194: Alerts UI: Alert Definition API should provide a 'description' field

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28194/#review62108
---

Ship it!


Ship It!

- Alejandro Fernandez


On Nov. 18, 2014, 11:39 p.m., Jonathan Hurley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28194/
> ---
> 
> (Updated Nov. 18, 2014, 11:39 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Srimanth Gunturi.
> 
> 
> Bugs: AMBARI-8377
> https://issues.apache.org/jira/browse/AMBARI-8377
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Alerts UI needs a title and a description for alert definitions. We have the 
> {{label}} property for the title. We need a {{description}} property to 
> describe what this alert-definition does. 
> Default alert-definitions provided in stack could have better description 
> about themselves.
> 
> {{AlertDefinition/description}} will be added for this. We'll include 
> descriptions on {{alerts.json}} in HDFS for this Jira, and then a new Jira 
> will cover getting descriptions into the other JSON files.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/AlertDefinitionResponse.java
>  c6de8fe 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProvider.java
>  ccc71f1 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertDefinitionEntity.java
>  a66a916 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinition.java
>  9f2ec07 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionFactory.java
>  c694f90 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog200.java
>  a85a5d0 
>   ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 4fa4be1 
>   ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql 5092332 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql fb666df 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
> bb3fa5f 
>   ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql 2993cbf 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/alerts.json 
> ed0f4a6 
>   
> ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
>  faaafa6 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProviderTest.java
>  c1567dc 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertGroupResourceProviderTest.java
>  0643301 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertDefinitionEqualityTest.java
>  1ee1224 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/cluster/AlertDataManagerTest.java
>  f2c4053 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java
>  64bdbca 
>   ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HDFS/alerts.json 
> 202488c 
> 
> Diff: https://reviews.apache.org/r/28194/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 12:54 min
> [INFO] Finished at: 2014-11-18T09:04:37-05:00
> [INFO] Final Memory: 30M/606M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Jonathan Hurley
> 
>

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/
---

(Updated Nov. 19, 2014, 1:46 a.m.)


Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
Sid Wagle.


Bugs: AMBARI-8379
https://issues.apache.org/jira/browse/AMBARI-8379


Repository: ambari


Description
---

Summary of changes needed and implications

changes in falcon/conf/startup.properties:

1) For Falcon lineage to work below changes are needed on Ambari deployed 
configs for Falcon
Implications : Lineage feature of Falcon is blocked without these changes

MetadataMappingService is required for lineage:
```
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\

org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
org.apache.falcon.service.ProcessSubscriberService,\
org.apache.falcon.entity.store.ConfigurationStore,\
org.apache.falcon.rerun.service.RetryService,\
org.apache.falcon.rerun.service.LateRunService,\
org.apache.falcon.service.LogCleanupService,\
org.apache.falcon.metadata.MetadataMappingService
```

```
# Graph Database Properties #
# Graph implementation
*.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory

# Graph Storage
*.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
*.falcon.graph.storage.backend=berkeleyje
*.falcon.graph.serialize.path=/grid/0/data/lineage
*.falcon.graph.preserve.history=false
```

The properties that need a directory in the local file system should detect a 
mount point that is available on the Falcon server, and the python scripts need 
to crease these directories when the Falcon service is configured.

The folder permission are,
owner:falcon user
group:hadoop
permissions:775


Diffs (updated)
-

  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
 37dd213 
  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
 2316326 
  
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
 ec8b9c7 
  ambari-web/app/data/HDP2/site_properties.js e9b8234 
  ambari-web/app/models/service_config.js 255a679 

Diff: https://reviews.apache.org/r/28197/diff/


Testing
---

Ran ambari-server unit tests, all of which passed.
OK
--
Total run:664
Total errors:0
Total failures:0
OK

Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one of 
which was the Falcon server, and the other the client.
The falcon-startup.properties contains the correct values, and the Falcon 
Service Check passed.

http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1


* *.application.services: 
"org.apache.falcon.security.AuthenticationInitializationService,\ 
org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
org.apache.falcon.service.ProcessSubscriberService,\ 
org.apache.falcon.entity.store.ConfigurationStore,\ 
org.apache.falcon.rerun.service.RetryService,\ 
org.apache.falcon.rerun.service.LateRunService,\ 
org.apache.falcon.service.LogCleanupService,\ 
org.apache.falcon.metadata.MetadataMappingService",
* *.falcon.graph.blueprints.graph: "com.thinkaurelius.titan.core.TitanFactory",
* *.falcon.graph.preserve.history: "false",
* *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
* *.falcon.graph.storage.backend: "berkeleyje",
* *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",


Further, the permissions are correct,
ls -la /hadoop/falcon/data/
drwxrwxr-x 3 falcon hadoop 4096 Nov 18 23:54 lineage
ls -la /hadoop/falcon/data/lineage/
drwxrwxr-x 2 falcon hadoop 4096 Nov 19 00:03 graphdb


Thanks,

Alejandro Fernandez

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Sid Wagle]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/#review62105
---

Ship it!


Ship It!

- Sid Wagle


On Nov. 19, 2014, 1:46 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28197/
> ---
> 
> (Updated Nov. 19, 2014, 1:46 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-8379
> https://issues.apache.org/jira/browse/AMBARI-8379
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Summary of changes needed and implications
> 
> changes in falcon/conf/startup.properties:
> 
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> 
> MetadataMappingService is required for lineage:
> ```
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> ```
> 
> ```
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> 
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> ```
> 
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> 
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
>  37dd213 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
>  2316326 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
>  ec8b9c7 
>   ambari-web/app/data/HDP2/site_properties.js e9b8234 
>   ambari-web/app/models/service_config.js 255a679 
> 
> Diff: https://reviews.apache.org/r/28197/diff/
> 
> 
> Testing
> ---
> 
> Ran ambari-server unit tests, all of which passed.
> OK
> --
> Total run:664
> Total errors:0
> Total failures:0
> OK
> 
> Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one 
> of which was the Falcon server, and the other the client.
> The falcon-startup.properties contains the correct values, and the Falcon 
> Service Check passed.
> 
> http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1
> 
> 
> * *.application.services: 
> "org.apache.falcon.security.AuthenticationInitializationService,\ 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
> org.apache.falcon.service.ProcessSubscriberService,\ 
> org.apache.falcon.entity.store.ConfigurationStore,\ 
> org.apache.falcon.rerun.service.RetryService,\ 
> org.apache.falcon.rerun.service.LateRunService,\ 
> org.apache.falcon.service.LogCleanupService,\ 
> org.apache.falcon.metadata.MetadataMappingService",
> * *.falcon.graph.blueprints.graph: 
> "com.thinkaurelius.titan.core.TitanFactory",
> * *.falcon.graph.preserve.history: "false",
> * *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
> * *.falcon.graph.storage.backend: "berkeleyje",
> * *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",
> 
> 
> Further, the permissions are correct,
> ls -la /hadoop/falcon/data/
> drwxrwxr-x 3 falcon hadoop 4096 Nov 18 23:54 lineage
> ls -la /hadoop/falcon/data/lineage/
> drwxrwxr-x 2 falcon hadoop 4096 Nov 19 00:03 graphdb
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Sid Wagle]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/#review62104
---



ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py


This should be renamed to path instead or graph.path


- Sid Wagle


On Nov. 19, 2014, 1:36 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28197/
> ---
> 
> (Updated Nov. 19, 2014, 1:36 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-8379
> https://issues.apache.org/jira/browse/AMBARI-8379
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Summary of changes needed and implications
> 
> changes in falcon/conf/startup.properties:
> 
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> 
> MetadataMappingService is required for lineage:
> ```
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> ```
> 
> ```
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> 
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> ```
> 
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> 
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
>  37dd213 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
>  2316326 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
>  ec8b9c7 
>   ambari-web/app/data/HDP2/site_properties.js e9b8234 
>   ambari-web/app/models/service_config.js 255a679 
> 
> Diff: https://reviews.apache.org/r/28197/diff/
> 
> 
> Testing
> ---
> 
> Ran ambari-server unit tests, all of which passed.
> OK
> --
> Total run:664
> Total errors:0
> Total failures:0
> OK
> 
> Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one 
> of which was the Falcon server, and the other the client.
> The falcon-startup.properties contains the correct values, and the Falcon 
> Service Check passed.
> 
> http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1
> 
> 
> * *.application.services: 
> "org.apache.falcon.security.AuthenticationInitializationService,\ 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
> org.apache.falcon.service.ProcessSubscriberService,\ 
> org.apache.falcon.entity.store.ConfigurationStore,\ 
> org.apache.falcon.rerun.service.RetryService,\ 
> org.apache.falcon.rerun.service.LateRunService,\ 
> org.apache.falcon.service.LogCleanupService,\ 
> org.apache.falcon.metadata.MetadataMappingService",
> * *.falcon.graph.blueprints.graph: 
> "com.thinkaurelius.titan.core.TitanFactory",
> * *.falcon.graph.preserve.history: "false",
> * *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
> * *.falcon.graph.storage.backend: "berkeleyje",
> * *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",
> 
> 
> Further, the permissions are correct,
> ls -la /hadoop/falcon/data/
> drwxrwxr-x 3 falcon hadoop 4096 Nov 18 23:54 lineage
> ls -la /hadoop/falcon/data/lineage/
> drwxrwxr-x 2 falcon hadoop 4096 Nov 19 00:03 graphdb
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Jaimin Jetly]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/#review62102
---

Ship it!


Ship It!

- Jaimin Jetly


On Nov. 19, 2014, 1:36 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28197/
> ---
> 
> (Updated Nov. 19, 2014, 1:36 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-8379
> https://issues.apache.org/jira/browse/AMBARI-8379
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Summary of changes needed and implications
> 
> changes in falcon/conf/startup.properties:
> 
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> 
> MetadataMappingService is required for lineage:
> ```
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> ```
> 
> ```
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> 
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> ```
> 
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> 
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
>  37dd213 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
>  2316326 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
>  ec8b9c7 
>   ambari-web/app/data/HDP2/site_properties.js e9b8234 
>   ambari-web/app/models/service_config.js 255a679 
> 
> Diff: https://reviews.apache.org/r/28197/diff/
> 
> 
> Testing
> ---
> 
> Ran ambari-server unit tests, all of which passed.
> OK
> --
> Total run:664
> Total errors:0
> Total failures:0
> OK
> 
> Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one 
> of which was the Falcon server, and the other the client.
> The falcon-startup.properties contains the correct values, and the Falcon 
> Service Check passed.
> 
> http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1
> 
> 
> * *.application.services: 
> "org.apache.falcon.security.AuthenticationInitializationService,\ 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
> org.apache.falcon.service.ProcessSubscriberService,\ 
> org.apache.falcon.entity.store.ConfigurationStore,\ 
> org.apache.falcon.rerun.service.RetryService,\ 
> org.apache.falcon.rerun.service.LateRunService,\ 
> org.apache.falcon.service.LogCleanupService,\ 
> org.apache.falcon.metadata.MetadataMappingService",
> * *.falcon.graph.blueprints.graph: 
> "com.thinkaurelius.titan.core.TitanFactory",
> * *.falcon.graph.preserve.history: "false",
> * *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
> * *.falcon.graph.storage.backend: "berkeleyje",
> * *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",
> 
> 
> Further, the permissions are correct,
> ls -la /hadoop/falcon/data/
> drwxrwxr-x 3 falcon hadoop 4096 Nov 18 23:54 lineage
> ls -la /hadoop/falcon/data/lineage/
> drwxrwxr-x 2 falcon hadoop 4096 Nov 19 00:03 graphdb
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Commented] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217238#comment-14217238
 ] 

Hadoop QA commented on AMBARI-8379:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12682299/AMBARI-8379.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{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/685//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/685//console

This message is automatically generated.

> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch, AMBARI-8379_branch-1.7.0.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/
---

(Updated Nov. 19, 2014, 1:36 a.m.)


Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
Sid Wagle.


Bugs: AMBARI-8379
https://issues.apache.org/jira/browse/AMBARI-8379


Repository: ambari


Description
---

Summary of changes needed and implications

changes in falcon/conf/startup.properties:

1) For Falcon lineage to work below changes are needed on Ambari deployed 
configs for Falcon
Implications : Lineage feature of Falcon is blocked without these changes

MetadataMappingService is required for lineage:
```
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\

org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
org.apache.falcon.service.ProcessSubscriberService,\
org.apache.falcon.entity.store.ConfigurationStore,\
org.apache.falcon.rerun.service.RetryService,\
org.apache.falcon.rerun.service.LateRunService,\
org.apache.falcon.service.LogCleanupService,\
org.apache.falcon.metadata.MetadataMappingService
```

```
# Graph Database Properties #
# Graph implementation
*.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory

# Graph Storage
*.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
*.falcon.graph.storage.backend=berkeleyje
*.falcon.graph.serialize.path=/grid/0/data/lineage
*.falcon.graph.preserve.history=false
```

The properties that need a directory in the local file system should detect a 
mount point that is available on the Falcon server, and the python scripts need 
to crease these directories when the Falcon service is configured.

The folder permission are,
owner:falcon user
group:hadoop
permissions:775


Diffs (updated)
-

  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
 37dd213 
  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
 2316326 
  
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
 ec8b9c7 
  ambari-web/app/data/HDP2/site_properties.js e9b8234 
  ambari-web/app/models/service_config.js 255a679 

Diff: https://reviews.apache.org/r/28197/diff/


Testing
---

Ran ambari-server unit tests, all of which passed.
OK
--
Total run:664
Total errors:0
Total failures:0
OK

Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one of 
which was the Falcon server, and the other the client.
The falcon-startup.properties contains the correct values, and the Falcon 
Service Check passed.

http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1


* *.application.services: 
"org.apache.falcon.security.AuthenticationInitializationService,\ 
org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
org.apache.falcon.service.ProcessSubscriberService,\ 
org.apache.falcon.entity.store.ConfigurationStore,\ 
org.apache.falcon.rerun.service.RetryService,\ 
org.apache.falcon.rerun.service.LateRunService,\ 
org.apache.falcon.service.LogCleanupService,\ 
org.apache.falcon.metadata.MetadataMappingService",
* *.falcon.graph.blueprints.graph: "com.thinkaurelius.titan.core.TitanFactory",
* *.falcon.graph.preserve.history: "false",
* *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
* *.falcon.graph.storage.backend: "berkeleyje",
* *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",


Further, the permissions are correct,
ls -la /hadoop/falcon/data/
drwxrwxr-x 3 falcon hadoop 4096 Nov 18 23:54 lineage
ls -la /hadoop/falcon/data/lineage/
drwxrwxr-x 2 falcon hadoop 4096 Nov 19 00:03 graphdb


Thanks,

Alejandro Fernandez

[jira] [Updated] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-8379:

Attachment: AMBARI-8379.patch

> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch, AMBARI-8379_branch-1.7.0.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

[jira] [Updated] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-8379:

Attachment: AMBARI-8379_branch-1.7.0.patch

> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch, AMBARI-8379_branch-1.7.0.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

[jira] [Updated] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-8379:

Attachment: (was: AMBARI-8379.patch)

> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch, AMBARI-8379_branch-1.7.0.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Jaimin Jetly]

> On Nov. 19, 2014, 1:06 a.m., Alejandro Fernandez wrote:
> > ambari-web/app/data/HDP2/site_properties.js, lines 1908-1914
> > 
> >
> > Because these properties are only needed for HDP 2.2, what would happen 
> > for HDP 2.1 if isRequired is removed?

Since these properties are not defined in the HDP-2.1 stack, these properties 
will not show up in the UI when HDP-2.1 stack is selected irrespective of 
whatever attributes with any values are specified in the site_properties.js


- Jaimin


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/#review62087
---


On Nov. 19, 2014, 12:53 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28197/
> ---
> 
> (Updated Nov. 19, 2014, 12:53 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-8379
> https://issues.apache.org/jira/browse/AMBARI-8379
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Summary of changes needed and implications
> 
> changes in falcon/conf/startup.properties:
> 
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> 
> MetadataMappingService is required for lineage:
> ```
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> ```
> 
> ```
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> 
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> ```
> 
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> 
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
>  37dd213 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
>  2316326 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
>  ec8b9c7 
>   ambari-web/app/data/HDP2/site_properties.js e9b8234 
>   ambari-web/app/models/service_config.js 255a679 
> 
> Diff: https://reviews.apache.org/r/28197/diff/
> 
> 
> Testing
> ---
> 
> Ran ambari-server unit tests, all of which passed.
> OK
> --
> Total run:664
> Total errors:0
> Total failures:0
> OK
> 
> Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one 
> of which was the Falcon server, and the other the client.
> The falcon-startup.properties contains the correct values, and the Falcon 
> Service Check passed.
> 
> http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1
> 
> 
> * *.application.services: 
> "org.apache.falcon.security.AuthenticationInitializationService,\ 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
> org.apache.falcon.service.ProcessSubscriberService,\ 
> org.apache.falcon.entity.store.ConfigurationStore,\ 
> org.apache.falcon.rerun.service.RetryService,\ 
> org.apache.falcon.rerun.service.LateRunService,\ 
> org.apache.falcon.service.LogCleanupService,\ 
> org.apache.falcon.metadata.MetadataMappingService",
> * *.falcon.graph.blueprints.graph: 
> "com.thinkaurelius.titan.core.TitanFactory",
> * *.falcon.graph.preserve.history: "false",
> * *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
> * *.falcon.graph.storage.backend: "berkeleyje",
> * *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",
> 
> 
> Further, the permissio

Re: Review Request 28199: Quick Links should be disabled when the service is down.

[Yusaku Sako]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28199/#review62092
---


This would disable QuickLinks altogether for the entire service if any of its 
master component is down.
Instead of disabling the whole QuickLinks at the service-level, we should 
disable at the individual link level and say " (Inaccessible)" or 
something to that effect.

- Yusaku Sako


On Nov. 19, 2014, 12:41 a.m., Richard Zang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28199/
> ---
> 
> (Updated Nov. 19, 2014, 12:41 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly and Yusaku Sako.
> 
> 
> Bugs: AMBARI-8380
> https://issues.apache.org/jira/browse/AMBARI-8380
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> When the service is down, quick links should be disabled.  Otherwise the link 
> is taking to 404 page.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/controllers/main/service/item.js 2666032 
>   ambari-web/app/templates/main/service/item.hbs a264f5f 
>   ambari-web/app/views/common/quick_view_link_view.js 4123c8f 
> 
> Diff: https://reviews.apache.org/r/28199/diff/
> 
> 
> Testing
> ---
> 
> Manually tested on a live cluster.
> 
> 
> Thanks,
> 
> Richard Zang
> 
>

[jira] [Updated] (AMBARI-8380) Quick Links should be disabled when the service is down.

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-8380:

Fix Version/s: (was: 2.0.0)
   2.1.0

> Quick Links should be disabled when the service is down.
> 
>
> Key: AMBARI-8380
> URL: https://issues.apache.org/jira/browse/AMBARI-8380
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.1.0
>
> Attachments: AMBARI-8380.patch
>
>
> When the service is down, quick links should be disabled. Otherwise the link 
> is taking to 404 page.



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

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/#review62087
---



ambari-web/app/data/HDP2/site_properties.js


Because these properties are only needed for HDP 2.2, what would happen for 
HDP 2.1 if isRequired is removed?


- Alejandro Fernandez


On Nov. 19, 2014, 12:53 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28197/
> ---
> 
> (Updated Nov. 19, 2014, 12:53 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-8379
> https://issues.apache.org/jira/browse/AMBARI-8379
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Summary of changes needed and implications
> 
> changes in falcon/conf/startup.properties:
> 
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> 
> MetadataMappingService is required for lineage:
> ```
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> ```
> 
> ```
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> 
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> ```
> 
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> 
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
>  37dd213 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
>  2316326 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
>  ec8b9c7 
>   ambari-web/app/data/HDP2/site_properties.js e9b8234 
>   ambari-web/app/models/service_config.js 255a679 
> 
> Diff: https://reviews.apache.org/r/28197/diff/
> 
> 
> Testing
> ---
> 
> Ran ambari-server unit tests, all of which passed.
> OK
> --
> Total run:664
> Total errors:0
> Total failures:0
> OK
> 
> Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one 
> of which was the Falcon server, and the other the client.
> The falcon-startup.properties contains the correct values, and the Falcon 
> Service Check passed.
> 
> http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1
> 
> 
> * *.application.services: 
> "org.apache.falcon.security.AuthenticationInitializationService,\ 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
> org.apache.falcon.service.ProcessSubscriberService,\ 
> org.apache.falcon.entity.store.ConfigurationStore,\ 
> org.apache.falcon.rerun.service.RetryService,\ 
> org.apache.falcon.rerun.service.LateRunService,\ 
> org.apache.falcon.service.LogCleanupService,\ 
> org.apache.falcon.metadata.MetadataMappingService",
> * *.falcon.graph.blueprints.graph: 
> "com.thinkaurelius.titan.core.TitanFactory",
> * *.falcon.graph.preserve.history: "false",
> * *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
> * *.falcon.graph.storage.backend: "berkeleyje",
> * *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",
> 
> 
> Further, the permissions are correct,
> ls -la /hadoop/falcon/data/
> drwxrwxr-x 3 falcon hadoop 4096 Nov 18 23:54 lineage
> ls -la /hadoop/falcon/data/lineage/
> drwxrwxr-x 2 falcon hadoop 4096 Nov 19 00:03 graphdb
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Jaimin Jetly]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/#review62084
---



ambari-web/app/data/HDP2/site_properties.js


This property and below property are having *isRequired* attribute set to 
false.
ambari-web code sets this flag to false for the properties for which it is 
ok to have *no value* (otherwise web code gives validation error for *no value* 
properties)

Is this intentional ?

NOTE: If *isRequired* attribute is not mentioned then it defaults to true


- Jaimin Jetly


On Nov. 19, 2014, 12:53 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28197/
> ---
> 
> (Updated Nov. 19, 2014, 12:53 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-8379
> https://issues.apache.org/jira/browse/AMBARI-8379
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Summary of changes needed and implications
> 
> changes in falcon/conf/startup.properties:
> 
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> 
> MetadataMappingService is required for lineage:
> ```
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> ```
> 
> ```
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> 
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> ```
> 
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> 
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
>  37dd213 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
>  2316326 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
>  ec8b9c7 
>   ambari-web/app/data/HDP2/site_properties.js e9b8234 
>   ambari-web/app/models/service_config.js 255a679 
> 
> Diff: https://reviews.apache.org/r/28197/diff/
> 
> 
> Testing
> ---
> 
> Ran ambari-server unit tests, all of which passed.
> OK
> --
> Total run:664
> Total errors:0
> Total failures:0
> OK
> 
> Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one 
> of which was the Falcon server, and the other the client.
> The falcon-startup.properties contains the correct values, and the Falcon 
> Service Check passed.
> 
> http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1
> 
> 
> * *.application.services: 
> "org.apache.falcon.security.AuthenticationInitializationService,\ 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
> org.apache.falcon.service.ProcessSubscriberService,\ 
> org.apache.falcon.entity.store.ConfigurationStore,\ 
> org.apache.falcon.rerun.service.RetryService,\ 
> org.apache.falcon.rerun.service.LateRunService,\ 
> org.apache.falcon.service.LogCleanupService,\ 
> org.apache.falcon.metadata.MetadataMappingService",
> * *.falcon.graph.blueprints.graph: 
> "com.thinkaurelius.titan.core.TitanFactory",
> * *.falcon.graph.preserve.history: "false",
> * *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
> * *.falcon.graph.storage.backend: "berkeleyje",
> * *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",
> 
> 
> Further, the permissions are correct,
> ls -la /hadoop/falcon/data/
> drwxrwxr-x 3 falcon hadoop 4096 Nov 1

[jira] [Commented] (AMBARI-8380) Quick Links should be disabled when the service is down.

[Richard Zang (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217169#comment-14217169
 ] 

Richard Zang commented on AMBARI-8380:
--

UI change is not unit testable. Verified fix manually on live cluster.

> Quick Links should be disabled when the service is down.
> 
>
> Key: AMBARI-8380
> URL: https://issues.apache.org/jira/browse/AMBARI-8380
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.0.0
>
> Attachments: AMBARI-8380.patch
>
>
> When the service is down, quick links should be disabled. Otherwise the link 
> is taking to 404 page.



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

[jira] [Updated] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-8379:

Attachment: AMBARI-8379.patch

> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/
---

(Updated Nov. 19, 2014, 12:53 a.m.)


Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
Sid Wagle.


Bugs: AMBARI-8379
https://issues.apache.org/jira/browse/AMBARI-8379


Repository: ambari


Description
---

Summary of changes needed and implications

changes in falcon/conf/startup.properties:

1) For Falcon lineage to work below changes are needed on Ambari deployed 
configs for Falcon
Implications : Lineage feature of Falcon is blocked without these changes

MetadataMappingService is required for lineage:
```
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\

org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
org.apache.falcon.service.ProcessSubscriberService,\
org.apache.falcon.entity.store.ConfigurationStore,\
org.apache.falcon.rerun.service.RetryService,\
org.apache.falcon.rerun.service.LateRunService,\
org.apache.falcon.service.LogCleanupService,\
org.apache.falcon.metadata.MetadataMappingService
```

```
# Graph Database Properties #
# Graph implementation
*.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory

# Graph Storage
*.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
*.falcon.graph.storage.backend=berkeleyje
*.falcon.graph.serialize.path=/grid/0/data/lineage
*.falcon.graph.preserve.history=false
```

The properties that need a directory in the local file system should detect a 
mount point that is available on the Falcon server, and the python scripts need 
to crease these directories when the Falcon service is configured.

The folder permission are,
owner:falcon user
group:hadoop
permissions:775


Diffs (updated)
-

  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
 37dd213 
  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
 2316326 
  
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
 ec8b9c7 
  ambari-web/app/data/HDP2/site_properties.js e9b8234 
  ambari-web/app/models/service_config.js 255a679 

Diff: https://reviews.apache.org/r/28197/diff/


Testing
---

Ran ambari-server unit tests, all of which passed.
OK
--
Total run:664
Total errors:0
Total failures:0
OK

Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one of 
which was the Falcon server, and the other the client.
The falcon-startup.properties contains the correct values, and the Falcon 
Service Check passed.

http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1


* *.application.services: 
"org.apache.falcon.security.AuthenticationInitializationService,\ 
org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
org.apache.falcon.service.ProcessSubscriberService,\ 
org.apache.falcon.entity.store.ConfigurationStore,\ 
org.apache.falcon.rerun.service.RetryService,\ 
org.apache.falcon.rerun.service.LateRunService,\ 
org.apache.falcon.service.LogCleanupService,\ 
org.apache.falcon.metadata.MetadataMappingService",
* *.falcon.graph.blueprints.graph: "com.thinkaurelius.titan.core.TitanFactory",
* *.falcon.graph.preserve.history: "false",
* *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
* *.falcon.graph.storage.backend: "berkeleyje",
* *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",


Further, the permissions are correct,
ls -la /hadoop/falcon/data/
drwxrwxr-x 3 falcon hadoop 4096 Nov 18 23:54 lineage
ls -la /hadoop/falcon/data/lineage/
drwxrwxr-x 2 falcon hadoop 4096 Nov 19 00:03 graphdb


Thanks,

Alejandro Fernandez

[jira] [Updated] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-8379:

Attachment: (was: AMBARI-8379.patch)

> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

[jira] [Commented] (AMBARI-8380) Quick Links should be disabled when the service is down.

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217167#comment-14217167
 ] 

Hadoop QA commented on AMBARI-8380:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12682304/AMBARI-8380.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{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 .

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/684//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/684//console

This message is automatically generated.

> Quick Links should be disabled when the service is down.
> 
>
> Key: AMBARI-8380
> URL: https://issues.apache.org/jira/browse/AMBARI-8380
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.0.0
>
> Attachments: AMBARI-8380.patch
>
>
> When the service is down, quick links should be disabled. Otherwise the link 
> is taking to 404 page.



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

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/#review62077
---



ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py


There's no harm in being precise. The Falcon folks verified that those 2 
directories have those permissions when installed via GSInstaller



ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py


I'll use the default() construct, thanks for the tip.


- Alejandro Fernandez


On Nov. 19, 2014, 12:31 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28197/
> ---
> 
> (Updated Nov. 19, 2014, 12:31 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-8379
> https://issues.apache.org/jira/browse/AMBARI-8379
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Summary of changes needed and implications
> 
> changes in falcon/conf/startup.properties:
> 
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> 
> MetadataMappingService is required for lineage:
> ```
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> ```
> 
> ```
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> 
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> ```
> 
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> 
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
>  37dd213 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
>  2316326 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
>  ec8b9c7 
>   ambari-web/app/data/HDP2/site_properties.js e9b8234 
>   ambari-web/app/models/service_config.js 255a679 
> 
> Diff: https://reviews.apache.org/r/28197/diff/
> 
> 
> Testing
> ---
> 
> Ran ambari-server unit tests, all of which passed.
> OK
> --
> Total run:664
> Total errors:0
> Total failures:0
> OK
> 
> Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one 
> of which was the Falcon server, and the other the client.
> The falcon-startup.properties contains the correct values, and the Falcon 
> Service Check passed.
> 
> http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1
> 
> 
> * *.application.services: 
> "org.apache.falcon.security.AuthenticationInitializationService,\ 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
> org.apache.falcon.service.ProcessSubscriberService,\ 
> org.apache.falcon.entity.store.ConfigurationStore,\ 
> org.apache.falcon.rerun.service.RetryService,\ 
> org.apache.falcon.rerun.service.LateRunService,\ 
> org.apache.falcon.service.LogCleanupService,\ 
> org.apache.falcon.metadata.MetadataMappingService",
> * *.falcon.graph.blueprints.graph: 
> "com.thinkaurelius.titan.core.TitanFactory",
> * *.falcon.graph.preserve.history: "false",
> * *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
> * *.falcon.graph.storage.backend: "berkeleyje",
> * *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",
> 
> 
> Further, the permissions are correct,
> ls -la /hadoop/falcon/data/
> drwxrwxr-

Review Request 28199: Quick Links should be disabled when the service is down.

[Richard Zang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28199/
---

Review request for Ambari, Jaimin Jetly and Yusaku Sako.


Bugs: AMBARI-8380
https://issues.apache.org/jira/browse/AMBARI-8380


Repository: ambari


Description
---

When the service is down, quick links should be disabled.  Otherwise the link 
is taking to 404 page.


Diffs
-

  ambari-web/app/controllers/main/service/item.js 2666032 
  ambari-web/app/templates/main/service/item.hbs a264f5f 
  ambari-web/app/views/common/quick_view_link_view.js 4123c8f 

Diff: https://reviews.apache.org/r/28199/diff/


Testing
---

Manually tested on a live cluster.


Thanks,

Richard Zang

[jira] [Commented] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217154#comment-14217154
 ] 

Hudson commented on AMBARI-8378:


FAILURE: Integrated in Ambari-trunk-Commit #977 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/977/])
AMBARI-8378. Flume version is incorrect in HDP 2.2 stack. (mahadev) (mahadev: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3d99629705a8ea59f8fce91fa3e64728f9ed5de1)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/FLUME/metainfo.xml


> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

[jira] [Commented] (AMBARI-8015) Dashboard: add a widget for YARN links (similar to the HDFS Links)

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217153#comment-14217153
 ] 

Hudson commented on AMBARI-8015:


FAILURE: Integrated in Ambari-trunk-Commit #977 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/977/])
AMBARI-8015 Dashboard: add a widget for YARN links (similar to the HDFS Links) 
(rpidva via jaoki) (jaoki: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c0dc64ca3f9b634ed3e98fc614c0e7feb7fd5651)
* ambari-web/app/views/main/dashboard/widgets/yarn_links.js
* ambari-web/app/templates/main/dashboard/widgets/yarn_links.hbs
* ambari-web/app/views/main/dashboard/widgets.js
* ambari-web/app/views.js
* ambari-web/app/messages.js


> Dashboard: add a widget for YARN links (similar to the HDFS Links)
> --
>
> Key: AMBARI-8015
> URL: https://issues.apache.org/jira/browse/AMBARI-8015
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Mingjiang Shi
>Assignee: Rishi Pidva
> Fix For: 2.0.0
>
> Attachments: AMBARI-8015-1.patch, tested on my environment.png, 
> yarn_links.png
>
>
> There is an HDFS Links widget. It would be good to have a similar widget for 
> YARN.



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

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Sumit Mohanty]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/#review62073
---



ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py


In the conf directory above we do not set "group" or the "mode". Should we 
be setting those for these folders?



ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py


When you upgrade these config may not exist. Should there be a default 
value of None/Null?


- Sumit Mohanty


On Nov. 19, 2014, 12:31 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28197/
> ---
> 
> (Updated Nov. 19, 2014, 12:31 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-8379
> https://issues.apache.org/jira/browse/AMBARI-8379
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Summary of changes needed and implications
> 
> changes in falcon/conf/startup.properties:
> 
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> 
> MetadataMappingService is required for lineage:
> ```
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> ```
> 
> ```
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> 
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> ```
> 
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> 
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
>  37dd213 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
>  2316326 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
>  ec8b9c7 
>   ambari-web/app/data/HDP2/site_properties.js e9b8234 
>   ambari-web/app/models/service_config.js 255a679 
> 
> Diff: https://reviews.apache.org/r/28197/diff/
> 
> 
> Testing
> ---
> 
> Ran ambari-server unit tests, all of which passed.
> OK
> --
> Total run:664
> Total errors:0
> Total failures:0
> OK
> 
> Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one 
> of which was the Falcon server, and the other the client.
> The falcon-startup.properties contains the correct values, and the Falcon 
> Service Check passed.
> 
> http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1
> 
> 
> * *.application.services: 
> "org.apache.falcon.security.AuthenticationInitializationService,\ 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
> org.apache.falcon.service.ProcessSubscriberService,\ 
> org.apache.falcon.entity.store.ConfigurationStore,\ 
> org.apache.falcon.rerun.service.RetryService,\ 
> org.apache.falcon.rerun.service.LateRunService,\ 
> org.apache.falcon.service.LogCleanupService,\ 
> org.apache.falcon.metadata.MetadataMappingService",
> * *.falcon.graph.blueprints.graph: 
> "com.thinkaurelius.titan.core.TitanFactory",
> * *.falcon.graph.preserve.history: "false",
> * *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
> * *.falcon.graph.storage.backend: "berkeleyje",
> * *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",
> 
> 
> Further, the permissions are correct,
> ls -la /hadoop/falcon/data/
> drwxr

[jira] [Updated] (AMBARI-8380) Quick Links should be disabled when the service is down.

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-8380:
-
Attachment: AMBARI-8380.patch

> Quick Links should be disabled when the service is down.
> 
>
> Key: AMBARI-8380
> URL: https://issues.apache.org/jira/browse/AMBARI-8380
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.0.0
>
> Attachments: AMBARI-8380.patch
>
>
> When the service is down, quick links should be disabled. Otherwise the link 
> is taking to 404 page.



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

[jira] [Created] (AMBARI-8380) Quick Links should be disabled when the service is down.

[Richard Zang (JIRA)]

Richard Zang created AMBARI-8380:


 Summary: Quick Links should be disabled when the service is down.
 Key: AMBARI-8380
 URL: https://issues.apache.org/jira/browse/AMBARI-8380
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Richard Zang
Assignee: Richard Zang
 Fix For: 2.0.0


When the service is down, quick links should be disabled. Otherwise the link is 
taking to 404 page.



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

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/
---

(Updated Nov. 19, 2014, 12:31 a.m.)


Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
Sid Wagle.


Bugs: AMBARI-8379
https://issues.apache.org/jira/browse/AMBARI-8379


Repository: ambari


Description
---

Summary of changes needed and implications

changes in falcon/conf/startup.properties:

1) For Falcon lineage to work below changes are needed on Ambari deployed 
configs for Falcon
Implications : Lineage feature of Falcon is blocked without these changes

MetadataMappingService is required for lineage:
```
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\

org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
org.apache.falcon.service.ProcessSubscriberService,\
org.apache.falcon.entity.store.ConfigurationStore,\
org.apache.falcon.rerun.service.RetryService,\
org.apache.falcon.rerun.service.LateRunService,\
org.apache.falcon.service.LogCleanupService,\
org.apache.falcon.metadata.MetadataMappingService
```

```
# Graph Database Properties #
# Graph implementation
*.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory

# Graph Storage
*.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
*.falcon.graph.storage.backend=berkeleyje
*.falcon.graph.serialize.path=/grid/0/data/lineage
*.falcon.graph.preserve.history=false
```

The properties that need a directory in the local file system should detect a 
mount point that is available on the Falcon server, and the python scripts need 
to crease these directories when the Falcon service is configured.

The folder permission are,
owner:falcon user
group:hadoop
permissions:775


Diffs
-

  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
 37dd213 
  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
 2316326 
  
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
 ec8b9c7 
  ambari-web/app/data/HDP2/site_properties.js e9b8234 
  ambari-web/app/models/service_config.js 255a679 

Diff: https://reviews.apache.org/r/28197/diff/


Testing (updated)
---

Ran ambari-server unit tests, all of which passed.
OK
--
Total run:664
Total errors:0
Total failures:0
OK

Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one of 
which was the Falcon server, and the other the client.
The falcon-startup.properties contains the correct values, and the Falcon 
Service Check passed.

http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1


* *.application.services: 
"org.apache.falcon.security.AuthenticationInitializationService,\ 
org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
org.apache.falcon.service.ProcessSubscriberService,\ 
org.apache.falcon.entity.store.ConfigurationStore,\ 
org.apache.falcon.rerun.service.RetryService,\ 
org.apache.falcon.rerun.service.LateRunService,\ 
org.apache.falcon.service.LogCleanupService,\ 
org.apache.falcon.metadata.MetadataMappingService",
* *.falcon.graph.blueprints.graph: "com.thinkaurelius.titan.core.TitanFactory",
* *.falcon.graph.preserve.history: "false",
* *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
* *.falcon.graph.storage.backend: "berkeleyje",
* *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",


Further, the permissions are correct,
ls -la /hadoop/falcon/data/
drwxrwxr-x 3 falcon hadoop 4096 Nov 18 23:54 lineage
ls -la /hadoop/falcon/data/lineage/
drwxrwxr-x 2 falcon hadoop 4096 Nov 19 00:03 graphdb


Thanks,

Alejandro Fernandez

Re: Review Request 28197: Falcon lineage needs changes to startup.properties

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/#review62068
---



ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py


If the properties don't exist, an exception will only be thrown while 
trying to access them, so be robust about it.



ambari-web/app/data/HDP2/site_properties.js


Notice that the 2 directory properties have a "defaultDirectory" attribute.



ambari-web/app/models/service_config.js


This is needed to get the first mount point.


- Alejandro Fernandez


On Nov. 19, 2014, 12:25 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28197/
> ---
> 
> (Updated Nov. 19, 2014, 12:25 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-8379
> https://issues.apache.org/jira/browse/AMBARI-8379
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Summary of changes needed and implications
> 
> changes in falcon/conf/startup.properties:
> 
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> 
> MetadataMappingService is required for lineage:
> ```
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> ```
> 
> ```
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> 
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> ```
> 
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> 
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
>  37dd213 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
>  2316326 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
>  ec8b9c7 
>   ambari-web/app/data/HDP2/site_properties.js e9b8234 
>   ambari-web/app/models/service_config.js 255a679 
> 
> Diff: https://reviews.apache.org/r/28197/diff/
> 
> 
> Testing
> ---
> 
> Ran ambari-server unit tests, all of which passed.
> OK
> --
> Total run:664
> Total errors:0
> Total failures:0
> OK
> 
> Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one 
> of which was the Falcon server, and the other the client.
> The falcon-startup.properties contains the correct values.
> 
> http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1
> 
> 
> * *.application.services: 
> "org.apache.falcon.security.AuthenticationInitializationService,\ 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
> org.apache.falcon.service.ProcessSubscriberService,\ 
> org.apache.falcon.entity.store.ConfigurationStore,\ 
> org.apache.falcon.rerun.service.RetryService,\ 
> org.apache.falcon.rerun.service.LateRunService,\ 
> org.apache.falcon.service.LogCleanupService,\ 
> org.apache.falcon.metadata.MetadataMappingService",
> * *.falcon.graph.blueprints.graph: 
> "com.thinkaurelius.titan.core.TitanFactory",
> * *.falcon.graph.preserve.history: "false",
> * *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
> * *.falcon.graph.storage.backend: "berkeleyje",
> * *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",
> 
> 
> Further, the permissi

[jira] [Commented] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Yusaku Sako (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217123#comment-14217123
 ] 

Yusaku Sako commented on AMBARI-8378:
-

Committed to trunk and branch-1.7.0.

> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

Review Request 28197: Falcon lineage needs changes to startup.properties

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28197/
---

Review request for Ambari, Jaimin Jetly, Mahadev Konar, Srimanth Gunturi, and 
Sid Wagle.


Bugs: AMBARI-8379
https://issues.apache.org/jira/browse/AMBARI-8379


Repository: ambari


Description
---

Summary of changes needed and implications

changes in falcon/conf/startup.properties:

1) For Falcon lineage to work below changes are needed on Ambari deployed 
configs for Falcon
Implications : Lineage feature of Falcon is blocked without these changes

MetadataMappingService is required for lineage:
```
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\

org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
org.apache.falcon.service.ProcessSubscriberService,\
org.apache.falcon.entity.store.ConfigurationStore,\
org.apache.falcon.rerun.service.RetryService,\
org.apache.falcon.rerun.service.LateRunService,\
org.apache.falcon.service.LogCleanupService,\
org.apache.falcon.metadata.MetadataMappingService
```

```
# Graph Database Properties #
# Graph implementation
*.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory

# Graph Storage
*.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
*.falcon.graph.storage.backend=berkeleyje
*.falcon.graph.serialize.path=/grid/0/data/lineage
*.falcon.graph.preserve.history=false
```

The properties that need a directory in the local file system should detect a 
mount point that is available on the Falcon server, and the python scripts need 
to crease these directories when the Falcon service is configured.

The folder permission are,
owner:falcon user
group:hadoop
permissions:775


Diffs
-

  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/falcon.py
 37dd213 
  
ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/package/scripts/params.py
 2316326 
  
ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml
 ec8b9c7 
  ambari-web/app/data/HDP2/site_properties.js e9b8234 
  ambari-web/app/models/service_config.js 255a679 

Diff: https://reviews.apache.org/r/28197/diff/


Testing
---

Ran ambari-server unit tests, all of which passed.
OK
--
Total run:664
Total errors:0
Total failures:0
OK

Also used the Install Wizard to deploy an HDP 2.2 cluster with 2 nodes, one of 
which was the Falcon server, and the other the client.
The falcon-startup.properties contains the correct values.

http://c6411.ambari.apache.org:8080/api/v1/clusters/dev/configurations?type=falcon-startup.properties&tag=version1


* *.application.services: 
"org.apache.falcon.security.AuthenticationInitializationService,\ 
org.apache.falcon.workflow.WorkflowJobEndNotificationService, \ 
org.apache.falcon.service.ProcessSubscriberService,\ 
org.apache.falcon.entity.store.ConfigurationStore,\ 
org.apache.falcon.rerun.service.RetryService,\ 
org.apache.falcon.rerun.service.LateRunService,\ 
org.apache.falcon.service.LogCleanupService,\ 
org.apache.falcon.metadata.MetadataMappingService",
* *.falcon.graph.blueprints.graph: "com.thinkaurelius.titan.core.TitanFactory",
* *.falcon.graph.preserve.history: "false",
* *.falcon.graph.serialize.path: "/hadoop/falcon/data/lineage",
* *.falcon.graph.storage.backend: "berkeleyje",
* *.falcon.graph.storage.directory: "/hadoop/falcon/data/lineage/graphdb",


Further, the permissions are correct,
ls -la /hadoop/falcon/data/
drwxrwxr-x 3 falcon hadoop 4096 Nov 18 23:54 lineage
ls -la /hadoop/falcon/data/lineage/
drwxrwxr-x 2 falcon hadoop 4096 Nov 19 00:03 graphdb


Thanks,

Alejandro Fernandez

[jira] [Updated] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-8379:

Attachment: AMBARI-8379.patch

> Falcon lineage needs changes to startup.properties
> --
>
> Key: AMBARI-8379
> URL: https://issues.apache.org/jira/browse/AMBARI-8379
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8379.patch
>
>
> Summary of changes needed and implications
> changes in falcon/conf/startup.properties:
> 1) For Falcon lineage to work below changes are needed on Ambari deployed 
> configs for Falcon
> Implications : Lineage feature of Falcon is blocked without these changes
> MetadataMappingService is required for lineage:
> {code}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> 
> org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService
> {code}
> {code}
> # Graph Database Properties #
> # Graph implementation
> *.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory
> # Graph Storage
> *.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
> *.falcon.graph.storage.backend=berkeleyje
> *.falcon.graph.serialize.path=/grid/0/data/lineage
> *.falcon.graph.preserve.history=false
> {code}
> The properties that need a directory in the local file system should detect a 
> mount point that is available on the Falcon server, and the python scripts 
> need to crease these directories when the Falcon service is configured.
> The folder permission are,
> owner:falcon user
> group:hadoop
> permissions:775



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

[jira] [Commented] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217104#comment-14217104
 ] 

Hudson commented on AMBARI-8378:


FAILURE: Integrated in Ambari-trunk-Commit-docker #266 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/266/])
AMBARI-8378. Flume version is incorrect in HDP 2.2 stack. (mahadev) (mahadev: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3d99629705a8ea59f8fce91fa3e64728f9ed5de1)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/FLUME/metainfo.xml


> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

[jira] [Commented] (AMBARI-8015) Dashboard: add a widget for YARN links (similar to the HDFS Links)

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217103#comment-14217103
 ] 

Hudson commented on AMBARI-8015:


FAILURE: Integrated in Ambari-trunk-Commit-docker #266 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/266/])
AMBARI-8015 Dashboard: add a widget for YARN links (similar to the HDFS Links) 
(rpidva via jaoki) (jaoki: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c0dc64ca3f9b634ed3e98fc614c0e7feb7fd5651)
* ambari-web/app/views/main/dashboard/widgets.js
* ambari-web/app/views.js
* ambari-web/app/messages.js
* ambari-web/app/views/main/dashboard/widgets/yarn_links.js
* ambari-web/app/templates/main/dashboard/widgets/yarn_links.hbs


> Dashboard: add a widget for YARN links (similar to the HDFS Links)
> --
>
> Key: AMBARI-8015
> URL: https://issues.apache.org/jira/browse/AMBARI-8015
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Mingjiang Shi
>Assignee: Rishi Pidva
> Fix For: 2.0.0
>
> Attachments: AMBARI-8015-1.patch, tested on my environment.png, 
> yarn_links.png
>
>
> There is an HDFS Links widget. It would be good to have a similar widget for 
> YARN.



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

[jira] [Commented] (AMBARI-8278) Database Host for HadoopMetrics, Hive Oozie should be set to corresponding server host name

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217102#comment-14217102
 ] 

Hudson commented on AMBARI-8278:


FAILURE: Integrated in Ambari-trunk-Commit-docker #266 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/266/])
AMBARI-8278 - Database Host for HadoopMetrics, Hive Oozie should be set to 
corresponding server host name (abaranchuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4ca08bbe4b0960e441310e9c8bb32a158a8ca02c)
* ambari-web/app/models/service_config.js


> Database Host for HadoopMetrics, Hive Oozie should be set to corresponding 
> server host name
> ---
>
> Key: AMBARI-8278
> URL: https://issues.apache.org/jira/browse/AMBARI-8278
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: branch-windows-dev
>Reporter: Artem Baranchuk
>Assignee: Artem Baranchuk
> Fix For: branch-windows-dev
>
>




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

[jira] [Commented] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217098#comment-14217098
 ] 

Hudson commented on AMBARI-8378:


SUCCESS: Integrated in Ambari-branch-1.7.0-docker #174 (See 
[https://builds.apache.org/job/Ambari-branch-1.7.0-docker/174/])
AMBARI-8378. Flume version is incorrect in HDP 2.2 stack. (mahadev) (mahadev: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6edd9aae509e94f73cc406faa28492fd11e3f1e2)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/FLUME/metainfo.xml


> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

[jira] [Commented] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217096#comment-14217096
 ] 

Hudson commented on AMBARI-8378:


SUCCESS: Integrated in Ambari-branch-1.7.0 #410 (See 
[https://builds.apache.org/job/Ambari-branch-1.7.0/410/])
AMBARI-8378. Flume version is incorrect in HDP 2.2 stack. (mahadev) (mahadev: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6edd9aae509e94f73cc406faa28492fd11e3f1e2)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/FLUME/metainfo.xml


> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

[jira] [Created] (AMBARI-8379) Falcon lineage needs changes to startup.properties

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-8379:
---

 Summary: Falcon lineage needs changes to startup.properties
 Key: AMBARI-8379
 URL: https://issues.apache.org/jira/browse/AMBARI-8379
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 1.7.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Priority: Blocker
 Fix For: 1.7.0


Summary of changes needed and implications

changes in falcon/conf/startup.properties:

1) For Falcon lineage to work below changes are needed on Ambari deployed 
configs for Falcon
Implications : Lineage feature of Falcon is blocked without these changes

MetadataMappingService is required for lineage:
{code}
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\

org.apache.falcon.workflow.WorkflowJobEndNotificationService,\
org.apache.falcon.service.ProcessSubscriberService,\
org.apache.falcon.entity.store.ConfigurationStore,\
org.apache.falcon.rerun.service.RetryService,\
org.apache.falcon.rerun.service.LateRunService,\
org.apache.falcon.service.LogCleanupService,\
org.apache.falcon.metadata.MetadataMappingService
{code}

{code}
# Graph Database Properties #
# Graph implementation
*.falcon.graph.blueprints.graph=com.thinkaurelius.titan.core.TitanFactory

# Graph Storage
*.falcon.graph.storage.directory=/grid/0/data/lineage/graphdb
*.falcon.graph.storage.backend=berkeleyje
*.falcon.graph.serialize.path=/grid/0/data/lineage
*.falcon.graph.preserve.history=false
{code}

The properties that need a directory in the local file system should detect a 
mount point that is available on the Falcon server, and the python scripts need 
to crease these directories when the Falcon service is configured.

The folder permission are,
owner:falcon user
group:hadoop
permissions:775



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

[jira] [Commented] (AMBARI-7878) BIGTOP stack definition should be updated

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217078#comment-14217078
 ] 

Hudson commented on AMBARI-7878:


SUCCESS: Integrated in Ambari-trunk-Commit #976 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/976/])
AMBARI-7878 BIGTOP stack definition should be updated (adenisso via jaoki) 
(jaoki: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=32b1fc38e374bfc2285c37f8dd83c04b35ab3c92)
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/package/scripts/yarn.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/configuration-mapred/mapred-site.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/templates/catalina.properties.j2
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/status_params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/files/checkForFormat.sh
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/hive.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/hive_service.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/files/changeToSecureUid.sh
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/hook.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/package/scripts/application_timeline_server.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/hbase_service.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/files/startRrdcached.sh
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/MAHOUT/metainfo.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/templates/oozie-log4j.properties.j2
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/metainfo.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/WEBHCAT/package/scripts/webhcat.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/ZOOKEEPER/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/MAHOUT/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/PIG/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/scripts/ganglia_monitor.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/package/scripts/status_params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/configuration/capacity-scheduler.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/WEBHCAT/package/scripts/__init__.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/ZOOKEEPER/configuration/zookeeper-env.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/files/oozieSmoke2.sh
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/webhcat_service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/shared_initialization.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/postgresql_service.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/ZOOKEEPER/package/templates/zookeeper_client_jaas.conf.j2
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/configuration/hbase-site.xml
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/metainfo.xml
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/SQOOP/metainfo.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/configuration/hive-site.xml
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/metainfo.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/MAHOUT/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/hook.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/package/scripts/flume_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/WEBHCAT/package/scripts/status_params.py
* 
ambari-server/s

[jira] [Commented] (AMBARI-8278) Database Host for HadoopMetrics, Hive Oozie should be set to corresponding server host name

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217077#comment-14217077
 ] 

Hudson commented on AMBARI-8278:


SUCCESS: Integrated in Ambari-trunk-Commit #976 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/976/])
AMBARI-8278 - Database Host for HadoopMetrics, Hive Oozie should be set to 
corresponding server host name (abaranchuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4ca08bbe4b0960e441310e9c8bb32a158a8ca02c)
* ambari-web/app/models/service_config.js


> Database Host for HadoopMetrics, Hive Oozie should be set to corresponding 
> server host name
> ---
>
> Key: AMBARI-8278
> URL: https://issues.apache.org/jira/browse/AMBARI-8278
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: branch-windows-dev
>Reporter: Artem Baranchuk
>Assignee: Artem Baranchuk
> Fix For: branch-windows-dev
>
>




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

Review Request 28194: Alerts UI: Alert Definition API should provide a 'description' field

[Jonathan Hurley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28194/
---

Review request for Ambari, Alejandro Fernandez and Srimanth Gunturi.


Bugs: AMBARI-8377
https://issues.apache.org/jira/browse/AMBARI-8377


Repository: ambari


Description
---

Alerts UI needs a title and a description for alert definitions. We have the 
{{label}} property for the title. We need a {{description}} property to 
describe what this alert-definition does. 
Default alert-definitions provided in stack could have better description about 
themselves.

{{AlertDefinition/description}} will be added for this. We'll include 
descriptions on {{alerts.json}} in HDFS for this Jira, and then a new Jira will 
cover getting descriptions into the other JSON files.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/AlertDefinitionResponse.java
 c6de8fe 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProvider.java
 ccc71f1 
  
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertDefinitionEntity.java
 a66a916 
  
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinition.java
 9f2ec07 
  
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionFactory.java
 c694f90 
  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog200.java
 a85a5d0 
  ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 4fa4be1 
  ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql 5092332 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql fb666df 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
bb3fa5f 
  ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql 2993cbf 
  ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/alerts.json 
ed0f4a6 
  
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
 faaafa6 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProviderTest.java
 c1567dc 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertGroupResourceProviderTest.java
 0643301 
  
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertDefinitionEqualityTest.java
 1ee1224 
  
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/AlertDataManagerTest.java
 f2c4053 
  
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java
 64bdbca 
  ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HDFS/alerts.json 
202488c 

Diff: https://reviews.apache.org/r/28194/diff/


Testing
---

mvn clean test

[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 12:54 min
[INFO] Finished at: 2014-11-18T09:04:37-05:00
[INFO] Final Memory: 30M/606M
[INFO] 


Thanks,

Jonathan Hurley

[jira] [Updated] (AMBARI-8015) Dashboard: add a widget for YARN links (similar to the HDFS Links)

[jun aoki (JIRA)]

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

jun aoki updated AMBARI-8015:
-
Attachment: tested on my environment.png

> Dashboard: add a widget for YARN links (similar to the HDFS Links)
> --
>
> Key: AMBARI-8015
> URL: https://issues.apache.org/jira/browse/AMBARI-8015
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Mingjiang Shi
>Assignee: Rishi Pidva
> Fix For: 2.0.0
>
> Attachments: AMBARI-8015-1.patch, tested on my environment.png, 
> yarn_links.png
>
>
> There is an HDFS Links widget. It would be good to have a similar widget for 
> YARN.



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

[jira] [Commented] (AMBARI-8370) Failing during creation of MS SQL DB

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217038#comment-14217038
 ] 

Hudson commented on AMBARI-8370:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #265 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/265/])
AMBARI-8370 - Failing during creation of MS SQL DB (abaranchuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c9e24d5a1cb4348ba90f0532021a858f42118502)
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql


> Failing during creation of MS SQL DB
> 
>
> Key: AMBARI-8370
> URL: https://issues.apache.org/jira/browse/AMBARI-8370
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Artem Baranchuk
>Assignee: Artem Baranchuk
> Fix For: 2.0.0
>
>
> Exception during execution of Ambari-DDL-SQLServer-CREATE.sql
> {noformat}
> Msg 1767, Level 16, State 0, Line 231
> Foreign key 'FK__upgrade__cluster__5AE78E74' references invalid table 
> 'ambari.clusters'.
> Msg 1750, Level 16, State 0, Line 231
> Could not create constraint. See previous errors.
> Msg 8197, Level 16, State 4, Procedure trigger_workflow_delete, Line 2
> The object 'workflow' does not exist or is invalid for this operation.
> Msg 8197, Level 16, State 4, Procedure trigger_job_delete, Line 2
> The object 'job' does not exist or is invalid for this operation.
> Msg 8197, Level 16, State 4, Procedure trigger_task_delete, Line 2
> The object 'task' does not exist or is invalid for this operation.
> {noformat}



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

[jira] [Commented] (AMBARI-7878) BIGTOP stack definition should be updated

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217039#comment-14217039
 ] 

Hudson commented on AMBARI-7878:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #265 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/265/])
AMBARI-7878 BIGTOP stack definition should be updated (adenisso via jaoki) 
(jaoki: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=32b1fc38e374bfc2285c37f8dd83c04b35ab3c92)
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/ZOOKEEPER/package/scripts/params.py
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/SQOOP/metainfo.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/configuration/webhcat-site.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/hbase_decommission.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/WEBHCAT/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/SQOOP/configuration/sqoop-env.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/PIG/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/hcat.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/package/scripts/application_timeline_server.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/MAHOUT/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/webhcat_service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/configuration/hive-site.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/configuration/oozie-env.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/package/scripts/service.py
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/stack_advisor.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/PIG/package/scripts/pig.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/configuration/capacity-scheduler.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/scripts/oozie.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/hook.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/postgresql_service.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/WEBHCAT/package/scripts/webhcat.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/ZOOKEEPER/package/templates/zookeeper_client_jaas.conf.j2
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/files/startRrdcached.sh
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/namenode.py
* ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/metainfo.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/hive.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/status_params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/hbase_service.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/templates/catalina.properties.j2
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/webhcat_service.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/scripts/service_check.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/scripts/hive_service.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/configuration-mapred/mapred-site.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/SQOOP/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/shared_initialization.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/WEBHCAT/package/files/templetonSmoke.sh
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/configuration/ganglia-env.xml
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HIVE/package/files/templetonSmoke.sh
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/configuration/flume-env.xml
* 
am

[jira] [Resolved] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Mahadev konar (JIRA)]

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

Mahadev konar resolved AMBARI-8378.
---
Resolution: Fixed

> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

[jira] [Commented] (AMBARI-8370) Failing during creation of MS SQL DB

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217024#comment-14217024
 ] 

Hudson commented on AMBARI-8370:


SUCCESS: Integrated in Ambari-trunk-Commit #975 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/975/])
AMBARI-8370 - Failing during creation of MS SQL DB (abaranchuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c9e24d5a1cb4348ba90f0532021a858f42118502)
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql


> Failing during creation of MS SQL DB
> 
>
> Key: AMBARI-8370
> URL: https://issues.apache.org/jira/browse/AMBARI-8370
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Artem Baranchuk
>Assignee: Artem Baranchuk
> Fix For: 2.0.0
>
>
> Exception during execution of Ambari-DDL-SQLServer-CREATE.sql
> {noformat}
> Msg 1767, Level 16, State 0, Line 231
> Foreign key 'FK__upgrade__cluster__5AE78E74' references invalid table 
> 'ambari.clusters'.
> Msg 1750, Level 16, State 0, Line 231
> Could not create constraint. See previous errors.
> Msg 8197, Level 16, State 4, Procedure trigger_workflow_delete, Line 2
> The object 'workflow' does not exist or is invalid for this operation.
> Msg 8197, Level 16, State 4, Procedure trigger_job_delete, Line 2
> The object 'job' does not exist or is invalid for this operation.
> Msg 8197, Level 16, State 4, Procedure trigger_task_delete, Line 2
> The object 'task' does not exist or is invalid for this operation.
> {noformat}



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

[jira] [Commented] (AMBARI-7878) BIGTOP stack definition should be updated

[jun aoki (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216999#comment-14216999
 ] 

jun aoki commented on AMBARI-7878:
--

Committed to trunk
32b1fc38e374bfc2285c37f8dd83c04b35ab3c92


> BIGTOP stack definition should be updated
> -
>
> Key: AMBARI-7878
> URL: https://issues.apache.org/jira/browse/AMBARI-7878
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
> Fix For: 2.0.0
>
> Attachments: AMBARI-7878.branch-1.7.0.patch, AMBARI-7878.trunk.patch, 
> AMBARI-7878.trunk.patch.v2
>
>
> The definition for the BIGTOP stack needs to be updated with recent changes.



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

[jira] [Commented] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Yusaku Sako (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216995#comment-14216995
 ] 

Yusaku Sako commented on AMBARI-8378:
-

+1 for the patch.

> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

[jira] [Updated] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-8378:

Priority: Blocker  (was: Major)

> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
>Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

[jira] [Commented] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Jeff Sposetti (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216986#comment-14216986
 ] 

Jeff Sposetti commented on AMBARI-8378:
---

+1

> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

[jira] [Updated] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Mahadev konar (JIRA)]

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

Mahadev konar updated AMBARI-8378:
--
Attachment: AMBARI-8378.patch

> Flume version is incorrect in HDP 2.2 stack
> ---
>
> Key: AMBARI-8378
> URL: https://issues.apache.org/jira/browse/AMBARI-8378
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Mahadev konar
>Assignee: Mahadev konar
> Fix For: 1.7.0
>
> Attachments: AMBARI-8378.patch
>
>
> Flume version is incorrect in HDP 2.2 stack



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

[jira] [Created] (AMBARI-8378) Flume version is incorrect in HDP 2.2 stack

[Mahadev konar (JIRA)]

Mahadev konar created AMBARI-8378:
-

 Summary: Flume version is incorrect in HDP 2.2 stack
 Key: AMBARI-8378
 URL: https://issues.apache.org/jira/browse/AMBARI-8378
 Project: Ambari
  Issue Type: Bug
Affects Versions: 1.7.0
Reporter: Mahadev konar
Assignee: Mahadev konar
 Fix For: 1.7.0


Flume version is incorrect in HDP 2.2 stack



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

Re: Review Request 28059: AMBARI-7872: Create stack definitions for PHD-3.0.0.0

[Rishi Pidva]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28059/
---

(Updated Nov. 18, 2014, 2:13 p.m.)


Review request for Ambari.


Bugs: AMBARI-7872
https://issues.apache.org/jira/browse/AMBARI-7872


Repository: ambari


Description
---

Stack definitions for PHD-3.0.0.0


Diffs (updated)
-

  ambari-server/pom.xml 196e9e1 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/blueprints/multinode-default.json
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/blueprints/singlenode-default.json
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/configuration/cluster-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/after-INSTALL/scripts/hook.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/after-INSTALL/scripts/params.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/after-INSTALL/scripts/shared_initialization.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-ANY/files/changeToSecureUid.sh
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-ANY/scripts/hook.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-ANY/scripts/params.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-ANY/scripts/shared_initialization.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-INSTALL/scripts/hook.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-INSTALL/scripts/params.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-INSTALL/scripts/repo_initialization.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-INSTALL/scripts/shared_initialization.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-INSTALL/templates/repo_suse_rhel.j2
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-INSTALL/templates/repo_ubuntu.j2
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-RESTART/scripts/hook.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/files/checkForFormat.sh
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/files/task-log4j.properties
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/scripts/hook.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/scripts/params.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/scripts/shared_initialization.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/templates/commons-logging.properties.j2
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/templates/exclude_hosts_list.j2
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/templates/hadoop-metrics2.properties.j2
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/templates/health_check-v2.j2
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/templates/health_check.j2
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/hooks/before-START/templates/include_hosts_list.j2
 PRE-CREATION 
  ambari-server/src/main/resources/stacks/PHD/3.0.0.0/metainfo.xml PRE-CREATION 
  ambari-server/src/main/resources/stacks/PHD/3.0.0.0/repos/repoinfo.xml 
PRE-CREATION 
  ambari-server/src/main/resources/stacks/PHD/3.0.0.0/role_command_order.json 
PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services/FLUME/configuration/flume-conf.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services/FLUME/configuration/flume-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services/FLUME/configuration/flume-log4j.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services/FLUME/metainfo.xml 
PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services/FLUME/metrics.json 
PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services/FLUME/package/scripts/flume.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services/FLUME/package/scripts/flume_check.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services/FLUME/package/scripts/flume_handler.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services/FLUME/package/scripts/params.py
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/PHD/3.0.0.0/services

[jira] [Updated] (AMBARI-7872) Create stack definitions for PHD-3.0.0.0

[Rishi Pidva (JIRA)]

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

Rishi Pidva updated AMBARI-7872:

Attachment: AMBARI-7872.trunk.v2.patch

Attaching the new patch AMBARI-7872.trunk.v2.patch

> Create stack definitions for PHD-3.0.0.0
> 
>
> Key: AMBARI-7872
> URL: https://issues.apache.org/jira/browse/AMBARI-7872
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 1.7.0
>Reporter: Mahesh Kumar Vasanthu Somashekar
>Assignee: Mahesh Kumar Vasanthu Somashekar
> Fix For: 2.0.0
>
> Attachments: AMBARI-7872-branch-1.7.patch, AMBARI-7872-trunk.patch, 
> AMBARI-7872.trunk.v2.patch
>
>
> Create service definitions for PHD-3.0.0.0 stack.



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

[jira] [Updated] (AMBARI-8325) Ambari SCOM doesn't compile in trunk

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-8325:
--
Attachment: AMBARI-8325.2.patch

> Ambari SCOM doesn't compile in trunk
> 
>
> Key: AMBARI-8325
> URL: https://issues.apache.org/jira/browse/AMBARI-8325
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: 2.0.0
> Environment: Linux/Windows
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8325.2.patch, AMBARI-8325.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Ambari SCOM compilation fails in trunk
> INFO] 
> [INFO] Building Ambari SCOM Server 1.0.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 
> ambari-scom-server ---
> [INFO] Deleting 
> /Users/jluniya/build/trunk/ambari/contrib/ambari-scom/ambari-scom-server/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
> ambari-scom-server ---
> [debug] execute contextualize
> [WARNING] Using platform encoding (MacRoman actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] Copying 4 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
> ambari-scom-server ---
> [WARNING] File encoding has not been set, using platform encoding MacRoman, 
> i.e. build is platform dependent!
> [INFO] Compiling 21 source files to 
> /Users/jluniya/build/trunk/ambari/contrib/ambari-scom/ambari-scom-server/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR] 
> /Users/jluniya/build/trunk/ambari/contrib/ambari-scom/ambari-scom-server/src/main/java/org/apache/ambari/scom/AmbariServer.java:[314,11]
>  cannot find symbol
> symbol  : method createDefaultRoles()
> location: class org.apache.ambari.server.security.authorization.Users
> [ERROR] 
> /Users/jluniya/build/trunk/ambari/contrib/ambari-scom/ambari-scom-server/src/main/java/org/apache/ambari/scom/AmbariServer.java:[318,34]
>  cannot find symbol
> symbol  : method getLocalUser(java.lang.String)
> location: class org.apache.ambari.server.security.authorization.Users
> [ERROR] 
> /Users/jluniya/build/trunk/ambari/contrib/ambari-scom/ambari-scom-server/src/main/java/org/apache/ambari/scom/SQLProviderModule.java:[116,20]
>  cannot find symbol
> symbol  : constructor 
> JMXPropertyProvider(java.util.Map>,org.apache.ambari.server.controller.internal.URLStreamProvider,org.apache.ambari.scom.SQLProviderModule,java.lang.String,,java.lang.String,java.lang.String,java.util.Set)
> location: class org.apache.ambari.server.controller.jmx.JMXPropertyProvider
> [ERROR] 
> /Users/jluniya/build/trunk/ambari/contrib/ambari-scom/ambari-scom-server/src/main/java/org/apache/ambari/scom/SQLProviderModule.java:[134,20]
>  cannot find symbol
> symbol  : constructor 
> JMXPropertyProvider(java.util.Map>,org.apache.ambari.server.controller.internal.URLStreamProvider,org.apache.ambari.scom.SQLProviderModule,java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.util.Set)
> location: class org.apache.ambari.server.controller.jmx.JMXPropertyProvider
> [INFO] 4 errors



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

[jira] [Commented] (AMBARI-8375) AlertGroup REST Endpoint Should Return Alert Definition Source Type

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216895#comment-14216895
 ] 

Hudson commented on AMBARI-8375:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #264 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/264/])
AMBARI-8375 - AlertGroup REST Endpoint Should Return Alert Definition Source 
Type (jonathanhurley) (jhurley: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8b6e7e9e2144aad895b37f8fb99edfbbf4657334)
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AlertDefinitionResponse.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertGroupResourceProviderTest.java


> AlertGroup REST Endpoint Should Return Alert Definition Source Type
> ---
>
> Key: AMBARI-8375
> URL: https://issues.apache.org/jira/browse/AMBARI-8375
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8375.patch
>
>
> Information about alert definitions should contain it's {{type}}.
> {code:title="source_type" : "PORT" or "WEB" or "SCRIPT" or 
> "METRIC"|borderStyle=solid}
> http://localhost:8080/api/v1/clusters/c1/alert_groups?fields=*
>  "AlertGroup" : {
> "cluster_name" : "c1",
> "default" : true,
> "definitions" : [
>   {
> "name" : "ganglia_monitor_mapreduce_history_server",
> "label" : "Ganglia History Server Process Monitor",
> "enabled" : true,
> "service_name" : "GANGLIA",
> "component_name" : "GANGLIA_SERVER",
> "id" : 1,
> "source_type" : "PORT"
>   },
> ...
> {code}



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

[jira] [Commented] (AMBARI-8362) Alerts: Targets Should Support A Severity Level

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216894#comment-14216894
 ] 

Hudson commented on AMBARI-8362:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #264 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/264/])
AMBARI-8362 - Alerts: Targets Should Support A Severity Level (jonathanhurley) 
(jhurley: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7eee111cdb767e403aabd00c73d21729d2b3750d)
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog200.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java
* 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/AlertStateChangedListener.java
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertTargetEntity.java
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* 
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-DROP.sql


> Alerts: Targets Should Support A Severity Level
> ---
>
> Key: AMBARI-8362
> URL: https://issues.apache.org/jira/browse/AMBARI-8362
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8362.patch, AMBARI-8362.patch
>
>
> Alert targets should have an optional field that represents the severity 
> levels that they care about. This will allow users to create different 
> targets that are only alerted when an alert's state has transitioned to their 
> support criticality level. 
> For example, a user may want to have 2 different email targets, "Tier-1 
> Support" and "Tier-2 Support" where T1 receives WARNINGs only and T2 receives 
> CRITICALS and UNKNOWNS.
> We will extend the AlertTarget resource to provide this extra option. It will 
> be a list of supported criticality levels. A null or empty list implies all 
> levels are triggerable.
> An example of creating a target that only cares about OK and WARNING states.
> {code}
> {
>   "AlertTarget": {
> "name": "Administrators",
> "description": "The Admins",
> "notification_type": "EMAIL",
> "alert_states": ["OK", "WARNING"],
> "properties":{
>   "foo": "bar",
>   "foobar" : "baz"
> }
>   }
> }
> {code}



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

[jira] [Commented] (AMBARI-8376) Alerts UI: Alert instances not showing up in Alert Definition details page

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216896#comment-14216896
 ] 

Hudson commented on AMBARI-8376:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #264 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/264/])
AMBARI-8376. Alerts UI: Alert instances not showing up in Alert Definition 
details page (sgunturi: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=36f6b878760ed8b9c6ac07b3efe610fbed5cfc9d)
* ambari-web/app/mappers/alert_instances_mapper.js
* ambari-web/app/models/alert_instance.js
* ambari-web/app/controllers/main/alerts/definition_details_controller.js
* ambari-web/app/controllers/main/alerts/alert_instances_controller.js
* ambari-web/test/controllers/main/alerts/alert_instances_controller_test.js
* ambari-web/app/views/common/table_view.js
* ambari-web/app/templates/main/alerts/definition_details.hbs
* ambari-web/app/routes/main.js
* ambari-web/app/views/main/alerts/definition_details_view.js
* ambari-web/app/templates/main/host/host_alerts.hbs
* ambari-web/test/views/common/table_view_test.js
* ambari-web/app/utils/ajax/ajax.js


> Alerts UI: Alert instances not showing up in Alert Definition details page
> --
>
> Key: AMBARI-8376
> URL: https://issues.apache.org/jira/browse/AMBARI-8376
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Srimanth Gunturi
>Assignee: Srimanth Gunturi
> Fix For: 1.7.0
>
> Attachments: AMBARI-8376.patch
>
>
> I went to an alert-definition that had 2 OK instances. However in the table 
> at the bottom I do not see details about that instance. This table should be 
> dynamically updating.



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

[jira] [Commented] (AMBARI-7878) BIGTOP stack definition should be updated

[jun aoki (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216888#comment-14216888
 ] 

jun aoki commented on AMBARI-7878:
--

+1 
I have tested with HDP 2.1 and found no regression. 

> BIGTOP stack definition should be updated
> -
>
> Key: AMBARI-7878
> URL: https://issues.apache.org/jira/browse/AMBARI-7878
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
> Fix For: 2.0.0
>
> Attachments: AMBARI-7878.branch-1.7.0.patch, AMBARI-7878.trunk.patch, 
> AMBARI-7878.trunk.patch.v2
>
>
> The definition for the BIGTOP stack needs to be updated with recent changes.



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

[jira] [Commented] (AMBARI-8376) Alerts UI: Alert instances not showing up in Alert Definition details page

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216880#comment-14216880
 ] 

Hudson commented on AMBARI-8376:


SUCCESS: Integrated in Ambari-trunk-Commit #974 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/974/])
AMBARI-8376. Alerts UI: Alert instances not showing up in Alert Definition 
details page (sgunturi: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=36f6b878760ed8b9c6ac07b3efe610fbed5cfc9d)
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/models/alert_instance.js
* ambari-web/app/views/main/alerts/definition_details_view.js
* ambari-web/test/views/common/table_view_test.js
* ambari-web/app/controllers/main/alerts/alert_instances_controller.js
* ambari-web/app/templates/main/host/host_alerts.hbs
* ambari-web/test/controllers/main/alerts/alert_instances_controller_test.js
* ambari-web/app/routes/main.js
* ambari-web/app/views/common/table_view.js
* ambari-web/app/templates/main/alerts/definition_details.hbs
* ambari-web/app/controllers/main/alerts/definition_details_controller.js
* ambari-web/app/mappers/alert_instances_mapper.js


> Alerts UI: Alert instances not showing up in Alert Definition details page
> --
>
> Key: AMBARI-8376
> URL: https://issues.apache.org/jira/browse/AMBARI-8376
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Srimanth Gunturi
>Assignee: Srimanth Gunturi
> Fix For: 1.7.0
>
> Attachments: AMBARI-8376.patch
>
>
> I went to an alert-definition that had 2 OK instances. However in the table 
> at the bottom I do not see details about that instance. This table should be 
> dynamically updating.



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

[jira] [Commented] (AMBARI-8375) AlertGroup REST Endpoint Should Return Alert Definition Source Type

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216879#comment-14216879
 ] 

Hudson commented on AMBARI-8375:


SUCCESS: Integrated in Ambari-trunk-Commit #974 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/974/])
AMBARI-8375 - AlertGroup REST Endpoint Should Return Alert Definition Source 
Type (jonathanhurley) (jhurley: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8b6e7e9e2144aad895b37f8fb99edfbbf4657334)
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AlertDefinitionResponse.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertGroupResourceProviderTest.java


> AlertGroup REST Endpoint Should Return Alert Definition Source Type
> ---
>
> Key: AMBARI-8375
> URL: https://issues.apache.org/jira/browse/AMBARI-8375
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8375.patch
>
>
> Information about alert definitions should contain it's {{type}}.
> {code:title="source_type" : "PORT" or "WEB" or "SCRIPT" or 
> "METRIC"|borderStyle=solid}
> http://localhost:8080/api/v1/clusters/c1/alert_groups?fields=*
>  "AlertGroup" : {
> "cluster_name" : "c1",
> "default" : true,
> "definitions" : [
>   {
> "name" : "ganglia_monitor_mapreduce_history_server",
> "label" : "Ganglia History Server Process Monitor",
> "enabled" : true,
> "service_name" : "GANGLIA",
> "component_name" : "GANGLIA_SERVER",
> "id" : 1,
> "source_type" : "PORT"
>   },
> ...
> {code}



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

[jira] [Commented] (AMBARI-8362) Alerts: Targets Should Support A Severity Level

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216878#comment-14216878
 ] 

Hudson commented on AMBARI-8362:


SUCCESS: Integrated in Ambari-trunk-Commit #974 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/974/])
AMBARI-8362 - Alerts: Targets Should Support A Severity Level (jonathanhurley) 
(jhurley: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7eee111cdb767e403aabd00c73d21729d2b3750d)
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-DROP.sql
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/AlertStateChangedListener.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertTargetEntity.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog200.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java


> Alerts: Targets Should Support A Severity Level
> ---
>
> Key: AMBARI-8362
> URL: https://issues.apache.org/jira/browse/AMBARI-8362
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8362.patch, AMBARI-8362.patch
>
>
> Alert targets should have an optional field that represents the severity 
> levels that they care about. This will allow users to create different 
> targets that are only alerted when an alert's state has transitioned to their 
> support criticality level. 
> For example, a user may want to have 2 different email targets, "Tier-1 
> Support" and "Tier-2 Support" where T1 receives WARNINGs only and T2 receives 
> CRITICALS and UNKNOWNS.
> We will extend the AlertTarget resource to provide this extra option. It will 
> be a list of supported criticality levels. A null or empty list implies all 
> levels are triggerable.
> An example of creating a target that only cares about OK and WARNING states.
> {code}
> {
>   "AlertTarget": {
> "name": "Administrators",
> "description": "The Admins",
> "notification_type": "EMAIL",
> "alert_states": ["OK", "WARNING"],
> "properties":{
>   "foo": "bar",
>   "foobar" : "baz"
> }
>   }
> }
> {code}



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

[jira] [Commented] (AMBARI-7878) BIGTOP stack definition should be updated

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216840#comment-14216840
 ] 

Hadoop QA commented on AMBARI-7878:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12682224/AMBARI-7878.trunk.patch.v2
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{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/683//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/683//console

This message is automatically generated.

> BIGTOP stack definition should be updated
> -
>
> Key: AMBARI-7878
> URL: https://issues.apache.org/jira/browse/AMBARI-7878
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
> Fix For: 2.0.0
>
> Attachments: AMBARI-7878.branch-1.7.0.patch, AMBARI-7878.trunk.patch, 
> AMBARI-7878.trunk.patch.v2
>
>
> The definition for the BIGTOP stack needs to be updated with recent changes.



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

[jira] [Updated] (AMBARI-8377) Alerts UI: Alert Definition API should provide a 'description' field

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-8377:

Attachment: AMBARI-8377.patch

> Alerts UI: Alert Definition API should provide a 'description' field
> 
>
> Key: AMBARI-8377
> URL: https://issues.apache.org/jira/browse/AMBARI-8377
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8377.patch, AMBARI-8377.patch
>
>
> Alerts UI needs a title and a description for alert definitions. We have the 
> {{label}} property for the title. We need a {{description}} property to 
> describe what this alert-definition does. 
> Default alert-definitions provided in stack could have better description 
> about themselves.
> {{AlertDefinition/description}} will be added for this. We'll include 
> descriptions on {{alerts.json}} in HDFS for this Jira, and then a new Jira 
> will cover getting descriptions into the other JSON files.



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

[jira] [Commented] (AMBARI-8376) Alerts UI: Alert instances not showing up in Alert Definition details page

[Xi Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216797#comment-14216797
 ] 

Xi Wang commented on AMBARI-8376:
-

+1 for patch

> Alerts UI: Alert instances not showing up in Alert Definition details page
> --
>
> Key: AMBARI-8376
> URL: https://issues.apache.org/jira/browse/AMBARI-8376
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Srimanth Gunturi
>Assignee: Srimanth Gunturi
> Fix For: 1.7.0
>
> Attachments: AMBARI-8376.patch
>
>
> I went to an alert-definition that had 2 OK instances. However in the table 
> at the bottom I do not see details about that instance. This table should be 
> dynamically updating.



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

[jira] [Updated] (AMBARI-8376) Alerts UI: Alert instances not showing up in Alert Definition details page

[Srimanth Gunturi (JIRA)]

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

Srimanth Gunturi updated AMBARI-8376:
-
Attachment: AMBARI-8376.patch

> Alerts UI: Alert instances not showing up in Alert Definition details page
> --
>
> Key: AMBARI-8376
> URL: https://issues.apache.org/jira/browse/AMBARI-8376
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Srimanth Gunturi
>Assignee: Srimanth Gunturi
> Fix For: 1.7.0
>
> Attachments: AMBARI-8376.patch
>
>
> I went to an alert-definition that had 2 OK instances. However in the table 
> at the bottom I do not see details about that instance. This table should be 
> dynamically updating.



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

[jira] [Commented] (AMBARI-8377) Alerts UI: Alert Definition API should provide a 'description' field

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216782#comment-14216782
 ] 

Hadoop QA commented on AMBARI-8377:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12682232/AMBARI-8377.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/682//console

This message is automatically generated.

> Alerts UI: Alert Definition API should provide a 'description' field
> 
>
> Key: AMBARI-8377
> URL: https://issues.apache.org/jira/browse/AMBARI-8377
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8377.patch
>
>
> Alerts UI needs a title and a description for alert definitions. We have the 
> {{label}} property for the title. We need a {{description}} property to 
> describe what this alert-definition does. 
> Default alert-definitions provided in stack could have better description 
> about themselves.
> {{AlertDefinition/description}} will be added for this. We'll include 
> descriptions on {{alerts.json}} in HDFS for this Jira, and then a new Jira 
> will cover getting descriptions into the other JSON files.



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

Re: Review Request 28181: AlertGroup REST Endpoint Should Return Alert Definition Source Type

[Srimanth Gunturi]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28181/#review62004
---

Ship it!


Ship It!

- Srimanth Gunturi


On Nov. 18, 2014, 7:01 p.m., Jonathan Hurley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28181/
> ---
> 
> (Updated Nov. 18, 2014, 7:01 p.m.)
> 
> 
> Review request for Ambari, Oleg Nechiporenko and Srimanth Gunturi.
> 
> 
> Bugs: AMBARI-8375
> https://issues.apache.org/jira/browse/AMBARI-8375
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Information about alert definitions should contain it's {{type}}.
> 
> {code:title="source_type" : "PORT" or "WEB" or "SCRIPT" or 
> "METRIC"|borderStyle=solid}
> http://localhost:8080/api/v1/clusters/c1/alert_groups?fields=*
>  "AlertGroup" : {
> "cluster_name" : "c1",
> "default" : true,
> "definitions" : [
>   {
> "name" : "ganglia_monitor_mapreduce_history_server",
> "label" : "Ganglia History Server Process Monitor",
> "enabled" : true,
> "service_name" : "GANGLIA",
> "component_name" : "GANGLIA_SERVER",
> "id" : 1,
> "source_type" : "PORT"
>   },
> ...
> {code}
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/AlertDefinitionResponse.java
>  908fed8 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertGroupResourceProviderTest.java
>  422c6f2 
> 
> Diff: https://reviews.apache.org/r/28181/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Jonathan Hurley
> 
>

[jira] [Commented] (AMBARI-8297) ambari hadoop deploy fails in docker

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216760#comment-14216760
 ] 

Hudson commented on AMBARI-8297:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #263 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/263/])
AMBARI-8297 ambari hadoop deploy fails in docker (jaoki) (jaoki: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d531181dad51878498336a243ec3fb0de7094a17)
* dev-support/docker/docker/blueprints/single-node-HDP-2.1-blueprint1.json


> ambari hadoop deploy fails in docker
> 
>
> Key: AMBARI-8297
> URL: https://issues.apache.org/jira/browse/AMBARI-8297
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: jun aoki
>Assignee: jun aoki
> Fix For: 2.0.0
>
> Attachments: remove-nagios_AMBARI-8297.patch
>
>
> As stated here 
> https://cwiki.apache.org/confluence/display/AMBARI/Development+in+Docker
> The ambari docker container should be able to deploy a Hadoop cluster in the 
> container (tested on 1.6.1), but it is broken on trunk due to nagios being 
> retired.
> The following docker command will fail on the latest code.
> {code}
> docker run --privileged -t -p 80:80 -p 5005:5005 -p 8080:8080 -h 
> node1.mydomain.com --name ambari1 -v ${AMBARI_SRC:-$(pwd)}:/tmp/ambari 
> ambari/build /tmp/ambari-build-docker/bin/ambaribuild.py deploy -b
> ...
> {
>   "status" : 400,
>   "message" : "The component 'NAGIOS_SERVER' in host group 'host_group_1' is 
> not valid for the specified stack"
> }HTTP/1.1 400 Bad Request
> Set-Cookie: AMBARISESSIONID=8xe0aw0vuopcytvhlzetau5q;Path=/
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> {code}



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

[jira] [Updated] (AMBARI-8377) Alerts UI: Alert Definition API should provide a 'description' field

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-8377:

Attachment: AMBARI-8377.patch

> Alerts UI: Alert Definition API should provide a 'description' field
> 
>
> Key: AMBARI-8377
> URL: https://issues.apache.org/jira/browse/AMBARI-8377
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8377.patch
>
>
> Alerts UI needs a title and a description for alert definitions. We have the 
> {{label}} property for the title. We need a {{description}} property to 
> describe what this alert-definition does. 
> Default alert-definitions provided in stack could have better description 
> about themselves.
> {{AlertDefinition/description}} will be added for this. We'll include 
> descriptions on {{alerts.json}} in HDFS for this Jira, and then a new Jira 
> will cover getting descriptions into the other JSON files.



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

[jira] [Commented] (AMBARI-8297) ambari hadoop deploy fails in docker

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216743#comment-14216743
 ] 

Hudson commented on AMBARI-8297:


SUCCESS: Integrated in Ambari-trunk-Commit #973 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/973/])
AMBARI-8297 ambari hadoop deploy fails in docker (jaoki) (jaoki: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d531181dad51878498336a243ec3fb0de7094a17)
* dev-support/docker/docker/blueprints/single-node-HDP-2.1-blueprint1.json


> ambari hadoop deploy fails in docker
> 
>
> Key: AMBARI-8297
> URL: https://issues.apache.org/jira/browse/AMBARI-8297
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: jun aoki
>Assignee: jun aoki
> Fix For: 2.0.0
>
> Attachments: remove-nagios_AMBARI-8297.patch
>
>
> As stated here 
> https://cwiki.apache.org/confluence/display/AMBARI/Development+in+Docker
> The ambari docker container should be able to deploy a Hadoop cluster in the 
> container (tested on 1.6.1), but it is broken on trunk due to nagios being 
> retired.
> The following docker command will fail on the latest code.
> {code}
> docker run --privileged -t -p 80:80 -p 5005:5005 -p 8080:8080 -h 
> node1.mydomain.com --name ambari1 -v ${AMBARI_SRC:-$(pwd)}:/tmp/ambari 
> ambari/build /tmp/ambari-build-docker/bin/ambaribuild.py deploy -b
> ...
> {
>   "status" : 400,
>   "message" : "The component 'NAGIOS_SERVER' in host group 'host_group_1' is 
> not valid for the specified stack"
> }HTTP/1.1 400 Bad Request
> Set-Cookie: AMBARISESSIONID=8xe0aw0vuopcytvhlzetau5q;Path=/
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> {code}



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

[jira] [Created] (AMBARI-8377) Alerts UI: Alert Definition API should provide a 'description' field

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-8377:
---

 Summary: Alerts UI: Alert Definition API should provide a 
'description' field
 Key: AMBARI-8377
 URL: https://issues.apache.org/jira/browse/AMBARI-8377
 Project: Ambari
  Issue Type: Task
  Components: alerts, ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
 Fix For: 2.0.0


Alerts UI needs a title and a description for alert definitions. We have the 
{{label}} property for the title. We need a {{description}} property to 
describe what this alert-definition does. 
Default alert-definitions provided in stack could have better description about 
themselves.

{{AlertDefinition/description}} will be added for this. We'll include 
descriptions on {{alerts.json}} in HDFS for this Jira, and then a new Jira will 
cover getting descriptions into the other JSON files.



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

[jira] [Created] (AMBARI-8376) Alerts UI: Alert instances not showing up in Alert Definition details page

[Srimanth Gunturi (JIRA)]

Srimanth Gunturi created AMBARI-8376:


 Summary: Alerts UI: Alert instances not showing up in Alert 
Definition details page
 Key: AMBARI-8376
 URL: https://issues.apache.org/jira/browse/AMBARI-8376
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 1.7.0
Reporter: Srimanth Gunturi
Assignee: Srimanth Gunturi
 Fix For: 1.7.0


I went to an alert-definition that had 2 OK instances. However in the table at 
the bottom I do not see details about that instance. This table should be 
dynamically updating.



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

[jira] [Commented] (AMBARI-8371) Unit tests for HA wizard views

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216695#comment-14216695
 ] 

Hudson commented on AMBARI-8371:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #262 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/262/])
AMBARI-8371 Unit tests for HA wizard views. (atkach) (atkach: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d9eb57388316f5cc680d6b210f3d0ab5e64f7668)
* ambari-web/app/assets/test/tests.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/step6_view_test.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/step1_view_test.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/step8_view_test.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/step6_view.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/step3_view_test.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/step4_view.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/wizard_view.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/step3_view.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/step4_view_test.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/step1_view.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/wizard_view_test.js


> Unit tests for HA wizard views
> --
>
> Key: AMBARI-8371
> URL: https://issues.apache.org/jira/browse/AMBARI-8371
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.0.0
>
> Attachments: AMBARI-8371.patch
>
>
> Cover with unit tests following files:
> * app/views/main/admin/highAvailability/nameNode/step1_view
> * app/views/main/admin/highAvailability/nameNode/step3_view
> * app/views/main/admin/highAvailability/nameNode/step4_view
> * app/views/main/admin/highAvailability/nameNode/step6_view
> * app/views/main/admin/highAvailability/nameNode/step8_view
> * app/views/main/admin/highAvailability/nameNode/wizard_view



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

Re: Review Request 28182: AMBARI-7878: BIGTOP stack definition should be updated

[Alexander Denissov]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28182/
---

(Updated Nov. 18, 2014, 7:56 p.m.)


Review request for Ambari.


Bugs: AMBARI-7878
https://issues.apache.org/jira/browse/AMBARI-7878


Repository: ambari


Description
---

Updated review request with updated patch. These changes are to the BIGTOP 
stack definition to reflect new features and bug fixes done on HDP stack 
between Sep 10 and Oct 18.


Diffs
-

  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/hook.py
 cf83e19 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/params.py
 1c611d4 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/shared_initialization.py
 1ba0ae7 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/files/changeToSecureUid.sh
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/hook.py
 0f97e28 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/params.py
 af67cb6 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/shared_initialization.py
 74bdce0 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/files/changeToSecureUid.sh
 154c1c0 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/hook.py
 a8a5662 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/params.py
 38d3137 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/shared_initialization.py
 720777f 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/files/checkForFormat.sh
 f92f613 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/hook.py
 a18a776 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py
 ebcaaec 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/shared_initialization.py
 0d00aca 
  ambari-server/src/main/resources/stacks/BIGTOP/0.8/repos/repoinfo.xml c372719 
  ambari-server/src/main/resources/stacks/BIGTOP/0.8/role_command_order.json 
25611d1 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/configuration/flume-env.xml
 7b11bde 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/metainfo.xml 
3c39550 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/package/scripts/flume.py
 6109d3e 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/package/scripts/flume_check.py
 3036e20 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/package/scripts/params.py
 128eed4 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/configuration/ganglia-env.xml
 e42baa5 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/files/startRrdcached.sh
 262f716 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/scripts/ganglia_monitor.py
 96cfdda 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/scripts/params.py
 e155122 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/configuration/hbase-site.xml
 a0ca6d7 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/metainfo.xml 
3ac282f 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/files/hbaseSmokeVerify.sh
 eedffd3 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/hbase_decommission.py
 4f7ed9e 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/hbase_service.py
 c0db5b5 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/params.py
 364649c 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/service_check.py
 8fb38f7 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/configuration/hadoop-env.xml
 e776148 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/configuration/hdfs-site.xml
 dfe71db 
  ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/metainfo.xml 
a452474 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/files/checkForFormat.sh
 d22d901 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs.py
 6f24f8e 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_datanode.py
 e38d9af 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py
 3456441 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/namenode.py
 8dae3eb 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/packa

Review Request 28182: AMBARI-7878: BIGTOP stack definition should be updated

[Alexander Denissov]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28182/
---

Review request for Ambari.


Bugs: AMBARI-7878
https://issues.apache.org/jira/browse/AMBARI-7878


Repository: ambari


Description
---

Updated review request with updated patch. These changes are to the BIGTOP 
stack definition to reflect new features and bug fixes done on HDP stack 
between Sep 10 and Oct 18.


Diffs
-

  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/hook.py
 cf83e19 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/params.py
 1c611d4 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/shared_initialization.py
 1ba0ae7 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/files/changeToSecureUid.sh
 PRE-CREATION 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/hook.py
 0f97e28 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/params.py
 af67cb6 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-ANY/scripts/shared_initialization.py
 74bdce0 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/files/changeToSecureUid.sh
 154c1c0 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/hook.py
 a8a5662 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/params.py
 38d3137 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/shared_initialization.py
 720777f 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/files/checkForFormat.sh
 f92f613 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/hook.py
 a18a776 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py
 ebcaaec 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/shared_initialization.py
 0d00aca 
  ambari-server/src/main/resources/stacks/BIGTOP/0.8/repos/repoinfo.xml c372719 
  ambari-server/src/main/resources/stacks/BIGTOP/0.8/role_command_order.json 
25611d1 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/configuration/flume-env.xml
 7b11bde 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/metainfo.xml 
3c39550 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/package/scripts/flume.py
 6109d3e 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/package/scripts/flume_check.py
 3036e20 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/FLUME/package/scripts/params.py
 128eed4 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/configuration/ganglia-env.xml
 e42baa5 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/files/startRrdcached.sh
 262f716 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/scripts/ganglia_monitor.py
 96cfdda 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/scripts/params.py
 e155122 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/configuration/hbase-site.xml
 a0ca6d7 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/metainfo.xml 
3ac282f 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/files/hbaseSmokeVerify.sh
 eedffd3 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/hbase_decommission.py
 4f7ed9e 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/hbase_service.py
 c0db5b5 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/params.py
 364649c 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HBASE/package/scripts/service_check.py
 8fb38f7 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/configuration/hadoop-env.xml
 e776148 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/configuration/hdfs-site.xml
 dfe71db 
  ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/metainfo.xml 
a452474 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/files/checkForFormat.sh
 d22d901 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs.py
 6f24f8e 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_datanode.py
 e38d9af 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py
 3456441 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/namenode.py
 8dae3eb 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
 0946d84 
  
amb

[jira] [Updated] (AMBARI-7878) BIGTOP stack definition should be updated

[Alexander Denissov (JIRA)]

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

Alexander Denissov updated AMBARI-7878:
---
Attachment: AMBARI-7878.trunk.patch.v2

The trunk patch has been updated to catch up with the latest trunk so that the 
patch can be applied.

> BIGTOP stack definition should be updated
> -
>
> Key: AMBARI-7878
> URL: https://issues.apache.org/jira/browse/AMBARI-7878
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
> Fix For: 2.0.0
>
> Attachments: AMBARI-7878.branch-1.7.0.patch, AMBARI-7878.trunk.patch, 
> AMBARI-7878.trunk.patch.v2
>
>
> The definition for the BIGTOP stack needs to be updated with recent changes.



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

[jira] [Commented] (AMBARI-8375) AlertGroup REST Endpoint Should Return Alert Definition Source Type

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216677#comment-14216677
 ] 

Hadoop QA commented on AMBARI-8375:
---

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12682216/AMBARI-8375.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 1 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/681//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/681//console

This message is automatically generated.

> AlertGroup REST Endpoint Should Return Alert Definition Source Type
> ---
>
> Key: AMBARI-8375
> URL: https://issues.apache.org/jira/browse/AMBARI-8375
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8375.patch
>
>
> Information about alert definitions should contain it's {{type}}.
> {code:title="source_type" : "PORT" or "WEB" or "SCRIPT" or 
> "METRIC"|borderStyle=solid}
> http://localhost:8080/api/v1/clusters/c1/alert_groups?fields=*
>  "AlertGroup" : {
> "cluster_name" : "c1",
> "default" : true,
> "definitions" : [
>   {
> "name" : "ganglia_monitor_mapreduce_history_server",
> "label" : "Ganglia History Server Process Monitor",
> "enabled" : true,
> "service_name" : "GANGLIA",
> "component_name" : "GANGLIA_SERVER",
> "id" : 1,
> "source_type" : "PORT"
>   },
> ...
> {code}



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

[jira] [Commented] (AMBARI-8297) ambari hadoop deploy fails in docker

[jun aoki (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216657#comment-14216657
 ] 

jun aoki commented on AMBARI-8297:
--

Committed to trunk 
d531181dad51878498336a243ec3fb0de7094a17


> ambari hadoop deploy fails in docker
> 
>
> Key: AMBARI-8297
> URL: https://issues.apache.org/jira/browse/AMBARI-8297
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: jun aoki
>Assignee: jun aoki
> Fix For: 2.0.0
>
> Attachments: remove-nagios_AMBARI-8297.patch
>
>
> As stated here 
> https://cwiki.apache.org/confluence/display/AMBARI/Development+in+Docker
> The ambari docker container should be able to deploy a Hadoop cluster in the 
> container (tested on 1.6.1), but it is broken on trunk due to nagios being 
> retired.
> The following docker command will fail on the latest code.
> {code}
> docker run --privileged -t -p 80:80 -p 5005:5005 -p 8080:8080 -h 
> node1.mydomain.com --name ambari1 -v ${AMBARI_SRC:-$(pwd)}:/tmp/ambari 
> ambari/build /tmp/ambari-build-docker/bin/ambaribuild.py deploy -b
> ...
> {
>   "status" : 400,
>   "message" : "The component 'NAGIOS_SERVER' in host group 'host_group_1' is 
> not valid for the specified stack"
> }HTTP/1.1 400 Bad Request
> Set-Cookie: AMBARISESSIONID=8xe0aw0vuopcytvhlzetau5q;Path=/
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> {code}



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

[jira] [Commented] (AMBARI-8371) Unit tests for HA wizard views

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216651#comment-14216651
 ] 

Hudson commented on AMBARI-8371:


SUCCESS: Integrated in Ambari-trunk-Commit #972 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/972/])
AMBARI-8371 Unit tests for HA wizard views. (atkach) (atkach: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d9eb57388316f5cc680d6b210f3d0ab5e64f7668)
* ambari-web/test/views/main/admin/highAvailability/nameNode/step6_view_test.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/step1_view.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/wizard_view_test.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/wizard_view.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/step6_view.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/step4_view.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/step1_view_test.js
* ambari-web/app/assets/test/tests.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/step4_view_test.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/step3_view_test.js
* ambari-web/test/views/main/admin/highAvailability/nameNode/step8_view_test.js
* ambari-web/app/views/main/admin/highAvailability/nameNode/step3_view.js


> Unit tests for HA wizard views
> --
>
> Key: AMBARI-8371
> URL: https://issues.apache.org/jira/browse/AMBARI-8371
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.0.0
>
> Attachments: AMBARI-8371.patch
>
>
> Cover with unit tests following files:
> * app/views/main/admin/highAvailability/nameNode/step1_view
> * app/views/main/admin/highAvailability/nameNode/step3_view
> * app/views/main/admin/highAvailability/nameNode/step4_view
> * app/views/main/admin/highAvailability/nameNode/step6_view
> * app/views/main/admin/highAvailability/nameNode/step8_view
> * app/views/main/admin/highAvailability/nameNode/wizard_view



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

[jira] [Commented] (AMBARI-8372) Distribute Repositories/Install Components - custom action script - fix failing unit tests (os check broken by 8de3425)

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216620#comment-14216620
 ] 

Hudson commented on AMBARI-8372:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #261 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/261/])
AMBARI-8372. Distribute Repositories/Install Components - custom action script 
- fix failing unit tests (os check broken by 8de3425) (dlysnichenko) 
(dlysnichenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0a3463c973ad1ebdba8314e519d424da6a0aeffb)
* ambari-common/src/main/python/ambari_commons/os_check.py


> Distribute Repositories/Install Components - custom action script - fix 
> failing unit tests (os check broken by 8de3425)
> ---
>
> Key: AMBARI-8372
> URL: https://issues.apache.org/jira/browse/AMBARI-8372
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8372.patch
>
>
> Failing build on Jenkins
> {code}
> ERROR: test_normal_flow (_TestInstallPackages.TestInstallPackages)
> --
> Traceback (most recent call last):
>   File "/media/plextor/ambari/ambari-common/src/test/python/mock/mock.py", 
> line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/custom_actions/_TestInstallPackages.py",
>  line 40, in test_normal_flow
> os_type=('Suse', '11', 'Final'),
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
>  line 118, in executeScript
> method(RMFTestCase.env)
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/stacks/utils/../../../../main/resources/custom_actions/scripts/install_packages.py",
>  line 83, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> Fail: Failed to distribute repositories/install packages
> ==
> FAIL: test_exclude_existing_repo (_TestInstallPackages.TestInstallPackages)
> --
> Traceback (most recent call last):
>   File "/media/plextor/ambari/ambari-common/src/test/python/mock/mock.py", 
> line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/custom_actions/_TestInstallPackages.py",
>  line 89, in test_exclude_existing_repo
> mirror_list=None,
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
>  line 193, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> AssertionError: {'base_url': u'http://host1/hdp', 'repo_template': 
> 'repo_suse_rhel.j2', 'compone [truncated]... != {'base_url': 
> u'http://host1/hdp', 'action': ['create'], 'components': [u'HDP-2.2 
> [truncated]...
>   {'action': ['create'],
>'base_url': u'http://host1/hdp',
>'components': [u'HDP-2.2.0.0-885', 'main'],
>'mirror_list': None,
>'repo_file_name': u'HDP-2.2.0.0-885',
> -  'repo_template': 'repo_suse_rhel.j2'}
> ? - ^^^
> +  'repo_template': 'repo_ubuntu.j2'}
> ?  ^
> --
> {code}



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

[jira] [Created] (AMBARI-8375) AlertGroup REST Endpoint Should Return Alert Definition Source Type

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-8375:
---

 Summary: AlertGroup REST Endpoint Should Return Alert Definition 
Source Type
 Key: AMBARI-8375
 URL: https://issues.apache.org/jira/browse/AMBARI-8375
 Project: Ambari
  Issue Type: Task
  Components: alerts, ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
 Fix For: 2.0.0


Information about alert definitions should contain it's {{type}}.

{code:title="source_type" : "PORT" or "WEB" or "SCRIPT" or 
"METRIC"|borderStyle=solid}
http://localhost:8080/api/v1/clusters/c1/alert_groups?fields=*
 "AlertGroup" : {
"cluster_name" : "c1",
"default" : true,
"definitions" : [
  {
"name" : "ganglia_monitor_mapreduce_history_server",
"label" : "Ganglia History Server Process Monitor",
"enabled" : true,
"service_name" : "GANGLIA",
"component_name" : "GANGLIA_SERVER",
"id" : 1,
"source_type" : "PORT"
  },
...
{code}



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

[jira] [Commented] (AMBARI-8361) Configs: UI breaks during particular flow

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216610#comment-14216610
 ] 

Hadoop QA commented on AMBARI-8361:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12682212/AMBARI-8361.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{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 .

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/680//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/680//console

This message is automatically generated.

> Configs: UI breaks during particular flow
> -
>
> Key: AMBARI-8361
> URL: https://issues.apache.org/jira/browse/AMBARI-8361
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8361.patch, AMBARI-8361.patch, 
> broken-versions.tiff
>
>
> Configs UI breaks with the following flow:
> 1) go to tez
> 2) edit tez.am.resource.memory.mb and make 1
> 3) click save
> 4) that prompts the warning that this is not a recommended value
> 5) click cancel
> 6) browse to pig
> 7) you are prompted you have unsaved changes, click discard
> 9) Pig configs ui ends up broken
> have to browse away and come back for it to straighten out. See attached for 
> example of broken-ness



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

Review Request 28181: AlertGroup REST Endpoint Should Return Alert Definition Source Type

[Jonathan Hurley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28181/
---

Review request for Ambari, Oleg Nechiporenko and Srimanth Gunturi.


Bugs: AMBARI-8375
https://issues.apache.org/jira/browse/AMBARI-8375


Repository: ambari


Description
---

Information about alert definitions should contain it's {{type}}.

{code:title="source_type" : "PORT" or "WEB" or "SCRIPT" or 
"METRIC"|borderStyle=solid}
http://localhost:8080/api/v1/clusters/c1/alert_groups?fields=*
 "AlertGroup" : {
"cluster_name" : "c1",
"default" : true,
"definitions" : [
  {
"name" : "ganglia_monitor_mapreduce_history_server",
"label" : "Ganglia History Server Process Monitor",
"enabled" : true,
"service_name" : "GANGLIA",
"component_name" : "GANGLIA_SERVER",
"id" : 1,
"source_type" : "PORT"
  },
...
{code}


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/AlertDefinitionResponse.java
 908fed8 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertGroupResourceProviderTest.java
 422c6f2 

Diff: https://reviews.apache.org/r/28181/diff/


Testing
---

mvn clean test


Thanks,

Jonathan Hurley

[jira] [Updated] (AMBARI-8375) AlertGroup REST Endpoint Should Return Alert Definition Source Type

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-8375:

Attachment: AMBARI-8375.patch

> AlertGroup REST Endpoint Should Return Alert Definition Source Type
> ---
>
> Key: AMBARI-8375
> URL: https://issues.apache.org/jira/browse/AMBARI-8375
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8375.patch
>
>
> Information about alert definitions should contain it's {{type}}.
> {code:title="source_type" : "PORT" or "WEB" or "SCRIPT" or 
> "METRIC"|borderStyle=solid}
> http://localhost:8080/api/v1/clusters/c1/alert_groups?fields=*
>  "AlertGroup" : {
> "cluster_name" : "c1",
> "default" : true,
> "definitions" : [
>   {
> "name" : "ganglia_monitor_mapreduce_history_server",
> "label" : "Ganglia History Server Process Monitor",
> "enabled" : true,
> "service_name" : "GANGLIA",
> "component_name" : "GANGLIA_SERVER",
> "id" : 1,
> "source_type" : "PORT"
>   },
> ...
> {code}



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

[jira] [Commented] (AMBARI-8361) Configs: UI breaks during particular flow

[Xi Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216584#comment-14216584
 ] 

Xi Wang commented on AMBARI-8361:
-

Attach the patch again

> Configs: UI breaks during particular flow
> -
>
> Key: AMBARI-8361
> URL: https://issues.apache.org/jira/browse/AMBARI-8361
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8361.patch, AMBARI-8361.patch, 
> broken-versions.tiff
>
>
> Configs UI breaks with the following flow:
> 1) go to tez
> 2) edit tez.am.resource.memory.mb and make 1
> 3) click save
> 4) that prompts the warning that this is not a recommended value
> 5) click cancel
> 6) browse to pig
> 7) you are prompted you have unsaved changes, click discard
> 9) Pig configs ui ends up broken
> have to browse away and come back for it to straighten out. See attached for 
> example of broken-ness



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

[jira] [Updated] (AMBARI-8361) Configs: UI breaks during particular flow

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-8361:

Attachment: AMBARI-8361.patch

> Configs: UI breaks during particular flow
> -
>
> Key: AMBARI-8361
> URL: https://issues.apache.org/jira/browse/AMBARI-8361
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8361.patch, AMBARI-8361.patch, 
> broken-versions.tiff
>
>
> Configs UI breaks with the following flow:
> 1) go to tez
> 2) edit tez.am.resource.memory.mb and make 1
> 3) click save
> 4) that prompts the warning that this is not a recommended value
> 5) click cancel
> 6) browse to pig
> 7) you are prompted you have unsaved changes, click discard
> 9) Pig configs ui ends up broken
> have to browse away and come back for it to straighten out. See attached for 
> example of broken-ness



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

[jira] [Commented] (AMBARI-8369) (EC2)Hosts have external host names on Hosts page

[Andrii Tkach (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216583#comment-14216583
 ] 

Andrii Tkach commented on AMBARI-8369:
--

committed to trunk.

> (EC2)Hosts have external host names on Hosts page
> -
>
> Key: AMBARI-8369
> URL: https://issues.apache.org/jira/browse/AMBARI-8369
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8369.patch
>
>
> Precondition:
> Deploy cluster with default settings and all components.
> STR:
> 1)Go on Hosts page
> 2)Check hosts names
> Actual result:
> Hosts have external host names on Hosts page
> Expected result:
> Hosts have internal host names on Hosts page



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

[jira] [Commented] (AMBARI-8374) creating cluster failed with zookeeper installation failure

[Dilli Arumugam (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216582#comment-14216582
 ] 

Dilli Arumugam commented on AMBARI-8374:


ambari-server --hash
8de3425f3fe106e54261927b44481685b1cc

> creating cluster failed with zookeeper installation failure
> ---
>
> Key: AMBARI-8374
> URL: https://issues.apache.org/jira/browse/AMBARI-8374
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.0.0
>Reporter: Dilli Arumugam
> Fix For: 2.0.0
>
>
> Attempting to create HDP 2.2 cluster with Ambari trunk build as of 11/17/14.
> Cluster creation failed with zookeeper server and client failing to install.
> Failure output:
> 2014-11-18 18:10:04,553 - Error while executing command 'install':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 152, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/ZOOKEEPER/package/scripts/zookeeper_server.py",
>  line 31, in install
> self.configure(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/ZOOKEEPER/package/scripts/zookeeper_server.py",
>  line 35, in configure
> zookeeper(type='server')
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/ZOOKEEPER/package/scripts/zookeeper.py",
>  line 61, in zookeeper
> group=params.user_group
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 119, in __new__
> env.resources[r_type][name] = obj
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 79, in __getattr__
> raise Fail("Configuration parameter '"+self.name+"' was not found in 
> configurations dictionary!")
> Fail: Configuration parameter 'dataDir' was not found in configurations 
> dictionary!
> stdout:   /var/lib/ambari-agent/data/output-119.txt
> 2014-11-18 18:10:02,622 - Execute['mkdir -p 
> /var/lib/ambari-agent/data/tmp/AMBARI-artifacts/; curl -kf -x "" --retry 
> 10 
> http://c6401.ambari.apache.org:8080/resources//UnlimitedJCEPolicyJDK7.zip -o 
> /var/lib/ambari-agent/data/tmp/AMBARI-artifacts//UnlimitedJCEPolicyJDK7.zip'] 
> {'environment': ..., 'not_if': 'test -e 
> /var/lib/ambari-agent/data/tmp/AMBARI-artifacts//UnlimitedJCEPolicyJDK7.zip', 
> 'ignore_failures': True, 'path': ['/bin', '/usr/bin/']}
> 2014-11-18 18:10:02,632 - Skipping Execute['mkdir -p 
> /var/lib/ambari-agent/data/tmp/AMBARI-artifacts/; curl -kf -x "" --retry 
> 10 
> http://c6401.ambari.apache.org:8080/resources//UnlimitedJCEPolicyJDK7.zip -o 
> /var/lib/ambari-agent/data/tmp/AMBARI-artifacts//UnlimitedJCEPolicyJDK7.zip'] 
> due to not_if
> 2014-11-18 18:10:02,633 - Group['hadoop'] {'ignore_failures': False}
> 2014-11-18 18:10:02,634 - Modifying group hadoop
> 2014-11-18 18:10:02,651 - Group['nobody'] {'ignore_failures': False}
> 2014-11-18 18:10:02,651 - Modifying group nobody
> 2014-11-18 18:10:02,667 - Group['users'] {'ignore_failures': False}
> 2014-11-18 18:10:02,668 - Modifying group users
> 2014-11-18 18:10:02,685 - Group['knox'] {'ignore_failures': False}
> 2014-11-18 18:10:02,686 - Modifying group knox
> 2014-11-18 18:10:02,699 - User['nobody'] {'gid': 'hadoop', 'ignore_failures': 
> False, 'groups': [u'nobody']}
> 2014-11-18 18:10:02,700 - Modifying user nobody
> 2014-11-18 18:10:02,715 - User['oozie'] {'gid': 'hadoop', 'ignore_failures': 
> False, 'groups': [u'users']}
> 2014-11-18 18:10:02,716 - Modifying user oozie
> 2014-11-18 18:10:02,732 - User['hive'] {'gid': 'hadoop', 'ignore_failures': 
> False, 'groups': [u'hadoop']}
> 2014-11-18 18:10:02,733 - Modifying user hive
> 2014-11-18 18:10:02,750 - User['mapred'] {'gid': 'hadoop', 'ignore_failures': 
> False, 'groups': [u'hadoop']}
> 2014-11-18 18:10:02,751 - Modifying user mapred
> 2014-11-18 18:10:02,768 - User['hbase'] {'gid': 'hadoop', 'ignore_failures': 
> False, 'groups': [u'hadoop']}
> 2014-11-18 18:10:02,769 - Modifying user hbase
> 2014-11-18 18:10:02,782 - User['ambari-qa'] {'gid': 'hadoop', 
> 'ignore_failures': False, 'groups': [u'users']}
> 2014-11-18 18:10:02,783 - Modifying user ambari-qa
> 2014-11-18 18:10:02,801 - User['zookeeper'] {'gid': 'hadoop', 
> 'ignore_failures': False, 'groups': [u'hadoop']}
> 2014-11-18 18:10:02,802 - Modifying user zookeeper
> 2014-11-18 18:10:02,818 - User['tez'] {'gid': 'hadoop', 'ignore_failures': 
> False, 'groups': [u'users']}
> 2014-11-18 18:10:02,818 - Modifying user tez
> 2014-11-18 18:10:02,834 - User['hdfs'] {'gid': 'hadoop', 'ignore_failures': 
> False, 'groups': [u'hadoop']}
> 2014-11-18 18:10:02,834 - Modifying user hdfs
> 2014-11-18 18:10:02,852 - User['knox'] {'gid': 'hadoop', 'ignor

[jira] [Commented] (AMBARI-8372) Distribute Repositories/Install Components - custom action script - fix failing unit tests (os check broken by 8de3425)

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216575#comment-14216575
 ] 

Hudson commented on AMBARI-8372:


FAILURE: Integrated in Ambari-trunk-Commit #971 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/971/])
AMBARI-8372. Distribute Repositories/Install Components - custom action script 
- fix failing unit tests (os check broken by 8de3425) (dlysnichenko) 
(dlysnichenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0a3463c973ad1ebdba8314e519d424da6a0aeffb)
* ambari-common/src/main/python/ambari_commons/os_check.py


> Distribute Repositories/Install Components - custom action script - fix 
> failing unit tests (os check broken by 8de3425)
> ---
>
> Key: AMBARI-8372
> URL: https://issues.apache.org/jira/browse/AMBARI-8372
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8372.patch
>
>
> Failing build on Jenkins
> {code}
> ERROR: test_normal_flow (_TestInstallPackages.TestInstallPackages)
> --
> Traceback (most recent call last):
>   File "/media/plextor/ambari/ambari-common/src/test/python/mock/mock.py", 
> line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/custom_actions/_TestInstallPackages.py",
>  line 40, in test_normal_flow
> os_type=('Suse', '11', 'Final'),
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
>  line 118, in executeScript
> method(RMFTestCase.env)
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/stacks/utils/../../../../main/resources/custom_actions/scripts/install_packages.py",
>  line 83, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> Fail: Failed to distribute repositories/install packages
> ==
> FAIL: test_exclude_existing_repo (_TestInstallPackages.TestInstallPackages)
> --
> Traceback (most recent call last):
>   File "/media/plextor/ambari/ambari-common/src/test/python/mock/mock.py", 
> line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/custom_actions/_TestInstallPackages.py",
>  line 89, in test_exclude_existing_repo
> mirror_list=None,
>   File 
> "/media/plextor/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
>  line 193, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> AssertionError: {'base_url': u'http://host1/hdp', 'repo_template': 
> 'repo_suse_rhel.j2', 'compone [truncated]... != {'base_url': 
> u'http://host1/hdp', 'action': ['create'], 'components': [u'HDP-2.2 
> [truncated]...
>   {'action': ['create'],
>'base_url': u'http://host1/hdp',
>'components': [u'HDP-2.2.0.0-885', 'main'],
>'mirror_list': None,
>'repo_file_name': u'HDP-2.2.0.0-885',
> -  'repo_template': 'repo_suse_rhel.j2'}
> ? - ^^^
> +  'repo_template': 'repo_ubuntu.j2'}
> ?  ^
> --
> {code}



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

[jira] [Resolved] (AMBARI-8146) Automated (Rolling) Upgrades support in Ambari

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez resolved AMBARI-8146.
-
Resolution: Duplicate

> Automated (Rolling) Upgrades support in Ambari
> --
>
> Key: AMBARI-8146
> URL: https://issues.apache.org/jira/browse/AMBARI-8146
> Project: Ambari
>  Issue Type: Epic
>  Components: ambari-server, ambari-web
>Affects Versions: 2.0.0
>Reporter: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.0.0
>
>
> Automated (Rolling) Upgrades support in Ambari.



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