[jira] [Created] (AMBARI-8272) When a host is deleted, nagios server is not restarting

[Dmytro Sen (JIRA)]

Dmytro Sen created AMBARI-8272:
--

 Summary: When a host is deleted, nagios server is not restarting
 Key: AMBARI-8272
 URL: https://issues.apache.org/jira/browse/AMBARI-8272
 Project: Ambari
  Issue Type: Bug
  Components: alerts, stacks
Affects Versions: 1.7.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
 Fix For: 2.0.0


In a cluster of 3 nodes, delete one of the host from the Host details page and 
selected Host Actions -> Delete Host.
Because of dependencies some services requires restart. When it try to restart 
the nagios server, it fails with the following error



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

Review Request 27861: When a host is deleted, nagios server is not restarting

[Dmytro Sen]

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

Review request for Ambari, Dmitro Lisnichenko and Vitalyi Brodetskyi.


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


Repository: ambari


Description
---

In a cluster of 3 nodes, delete one of the host from the Host details page and 
selected Host Actions -> Delete Host.
Because of dependencies some services requires restart. When it try to restart 
the nagios server, it fails with the following error


Diffs
-

  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/templates/hadoop-services.cfg.j2
 045e9ad 
  
ambari-server/src/main/resources/stacks/HDP/1.3.2/services/NAGIOS/package/templates/hadoop-services.cfg.j2
 48bba18 
  
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/NAGIOS/package/templates/hadoop-services.cfg.j2
 0d8b2e8 

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


Testing
---

--
Ran 251 tests in 3.213s

OK
--
Total run:693
Total errors:0
Total failures:0
OK


Thanks,

Dmytro Sen

Re: Review Request 27861: When a host is deleted, nagios server is not restarting

[Vitalyi Brodetskyi]

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

Ship it!


Ship It!

- Vitalyi Brodetskyi


On Лис. 11, 2014, 10:45 до полудня, Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27861/
> ---
> 
> (Updated Лис. 11, 2014, 10:45 до полудня)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-8272
> https://issues.apache.org/jira/browse/AMBARI-8272
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In a cluster of 3 nodes, delete one of the host from the Host details page 
> and selected Host Actions -> Delete Host.
> Because of dependencies some services requires restart. When it try to 
> restart the nagios server, it fails with the following error
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/templates/hadoop-services.cfg.j2
>  045e9ad 
>   
> ambari-server/src/main/resources/stacks/HDP/1.3.2/services/NAGIOS/package/templates/hadoop-services.cfg.j2
>  48bba18 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/NAGIOS/package/templates/hadoop-services.cfg.j2
>  0d8b2e8 
> 
> Diff: https://reviews.apache.org/r/27861/diff/
> 
> 
> Testing
> ---
> 
> --
> Ran 251 tests in 3.213s
> 
> OK
> --
> Total run:693
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Created] (AMBARI-8273) 'History Server' panel disappeared after deploy Ambari (Stack 1.3)

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-8273:
---

 Summary: 'History Server' panel disappeared after deploy Ambari 
(Stack 1.3)
 Key: AMBARI-8273
 URL: https://issues.apache.org/jira/browse/AMBARI-8273
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 1.7.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.0.0






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

[jira] [Updated] (AMBARI-8273) 'History Server' panel disappeared after deploy Ambari (Stack 1.3)

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-8273:

Attachment: AMBARI-8273.patch

> 'History Server' panel disappeared after deploy Ambari (Stack 1.3)
> --
>
> Key: AMBARI-8273
> URL: https://issues.apache.org/jira/browse/AMBARI-8273
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8273.patch
>
>




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

Re: Review Request 27861: When a host is deleted, nagios server is not restarting

[Dmitro Lisnichenko]

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

Ship it!


Ship It!

- Dmitro Lisnichenko


On Nov. 11, 2014, 10:45 a.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27861/
> ---
> 
> (Updated Nov. 11, 2014, 10:45 a.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-8272
> https://issues.apache.org/jira/browse/AMBARI-8272
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In a cluster of 3 nodes, delete one of the host from the Host details page 
> and selected Host Actions -> Delete Host.
> Because of dependencies some services requires restart. When it try to 
> restart the nagios server, it fails with the following error
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/templates/hadoop-services.cfg.j2
>  045e9ad 
>   
> ambari-server/src/main/resources/stacks/HDP/1.3.2/services/NAGIOS/package/templates/hadoop-services.cfg.j2
>  48bba18 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/NAGIOS/package/templates/hadoop-services.cfg.j2
>  0d8b2e8 
> 
> Diff: https://reviews.apache.org/r/27861/diff/
> 
> 
> Testing
> ---
> 
> --
> Ran 251 tests in 3.213s
> 
> OK
> --
> Total run:693
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Resolved] (AMBARI-8272) When a host is deleted, nagios server is not restarting

[Dmytro Sen (JIRA)]

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

Dmytro Sen resolved AMBARI-8272.

Resolution: Fixed

Committed to trunk

> When a host is deleted, nagios server is not restarting
> ---
>
> Key: AMBARI-8272
> URL: https://issues.apache.org/jira/browse/AMBARI-8272
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts, stacks
>Affects Versions: 1.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.0.0
>
>
> In a cluster of 3 nodes, delete one of the host from the Host details page 
> and selected Host Actions -> Delete Host.
> Because of dependencies some services requires restart. When it try to 
> restart the nagios server, it fails with the following error



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

[jira] [Commented] (AMBARI-8273) 'History Server' panel disappeared after deploy Ambari (Stack 1.3)

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8273:
---

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

This message is automatically generated.

> 'History Server' panel disappeared after deploy Ambari (Stack 1.3)
> --
>
> Key: AMBARI-8273
> URL: https://issues.apache.org/jira/browse/AMBARI-8273
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8273.patch
>
>




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

[jira] [Commented] (AMBARI-8273) 'History Server' panel disappeared after deploy Ambari (Stack 1.3)

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-8273:
-

Patch was tested manualy on real cluster. That behavior should be tested by 
integration tests, not unit tests.

> 'History Server' panel disappeared after deploy Ambari (Stack 1.3)
> --
>
> Key: AMBARI-8273
> URL: https://issues.apache.org/jira/browse/AMBARI-8273
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8273.patch
>
>




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

[jira] [Commented] (AMBARI-8273) 'History Server' panel disappeared after deploy Ambari (Stack 1.3)

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-8273:
--

+1 for the patch

> 'History Server' panel disappeared after deploy Ambari (Stack 1.3)
> --
>
> Key: AMBARI-8273
> URL: https://issues.apache.org/jira/browse/AMBARI-8273
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8273.patch
>
>




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

[jira] [Commented] (AMBARI-8273) 'History Server' panel disappeared after deploy Ambari (Stack 1.3)

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-8273:
-

committed to trunk

> 'History Server' panel disappeared after deploy Ambari (Stack 1.3)
> --
>
> Key: AMBARI-8273
> URL: https://issues.apache.org/jira/browse/AMBARI-8273
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8273.patch
>
>




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

[jira] [Commented] (AMBARI-8272) When a host is deleted, nagios server is not restarting

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8272:


SUCCESS: Integrated in Ambari-trunk-Commit #905 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/905/])
AMBARI-8272 When a host is deleted, nagios server is not restarting (dsen) 
(dsen: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=69fe8e4048d2ac9c747dc97d275f4761874007b3)
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/NAGIOS/package/templates/hadoop-services.cfg.j2
* 
ambari-server/src/main/resources/stacks/HDP/1.3.2/services/NAGIOS/package/templates/hadoop-services.cfg.j2
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/templates/hadoop-services.cfg.j2


> When a host is deleted, nagios server is not restarting
> ---
>
> Key: AMBARI-8272
> URL: https://issues.apache.org/jira/browse/AMBARI-8272
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts, stacks
>Affects Versions: 1.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.0.0
>
>
> In a cluster of 3 nodes, delete one of the host from the Host details page 
> and selected Host Actions -> Delete Host.
> Because of dependencies some services requires restart. When it try to 
> restart the nagios server, it fails with the following error



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

[jira] [Commented] (AMBARI-8272) When a host is deleted, nagios server is not restarting

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8272:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #197 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/197/])
AMBARI-8272 When a host is deleted, nagios server is not restarting (dsen) 
(dsen: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=69fe8e4048d2ac9c747dc97d275f4761874007b3)
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/templates/hadoop-services.cfg.j2
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/NAGIOS/package/templates/hadoop-services.cfg.j2
* 
ambari-server/src/main/resources/stacks/HDP/1.3.2/services/NAGIOS/package/templates/hadoop-services.cfg.j2


> When a host is deleted, nagios server is not restarting
> ---
>
> Key: AMBARI-8272
> URL: https://issues.apache.org/jira/browse/AMBARI-8272
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts, stacks
>Affects Versions: 1.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.0.0
>
>
> In a cluster of 3 nodes, delete one of the host from the Host details page 
> and selected Host Actions -> Delete Host.
> Because of dependencies some services requires restart. When it try to 
> restart the nagios server, it fails with the following error



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

[jira] [Created] (AMBARI-8274) Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-8274:


 Summary: Enable Kerberos Wizard: Downloaded CSV file is empty for 
HDP 1.3.*
 Key: AMBARI-8274
 URL: https://issues.apache.org/jira/browse/AMBARI-8274
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 1.7.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
 Fix For: 1.7.0






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

[jira] [Updated] (AMBARI-8274) Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-8274:
-
Attachment: AMBARI-8274_branch-1.7.0.patch

> Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*
> --
>
> Key: AMBARI-8274
> URL: https://issues.apache.org/jira/browse/AMBARI-8274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8274_branch-1.7.0.patch
>
>




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

[jira] [Updated] (AMBARI-8274) Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-8274:
-
Attachment: AMBARI-8274.patch

> Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*
> --
>
> Key: AMBARI-8274
> URL: https://issues.apache.org/jira/browse/AMBARI-8274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8274.patch, AMBARI-8274_branch-1.7.0.patch
>
>




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

Review Request 27864: Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*

[Andrii Tkach]

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

Review request for Ambari, Oleg Nechiporenko and Yusaku Sako.


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


Repository: ambari


Description
---

Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*


Diffs
-

  ambari-web/app/data/secure_mapping.js cfca947 
  ambari-web/app/data/secure_properties.js 5d01943 

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


Testing
---

Tested manually


Thanks,

Andrii Tkach

[jira] [Commented] (AMBARI-8273) 'History Server' panel disappeared after deploy Ambari (Stack 1.3)

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8273:


SUCCESS: Integrated in Ambari-trunk-Commit #906 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/906/])
AMBARI-8273. 'History Server' panel disappeared after deploy Ambari (Stack 
1.3). (akovalenko) (akovalenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=11e7c9f60fc26e0964200b6f5d78c28f8f3e9dde)
* ambari-web/app/controllers/main/service/info/configs.js


> 'History Server' panel disappeared after deploy Ambari (Stack 1.3)
> --
>
> Key: AMBARI-8273
> URL: https://issues.apache.org/jira/browse/AMBARI-8273
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8273.patch
>
>




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

Re: Review Request 27864: Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*

[Oleg Nechiporenko]

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

Ship it!


Ship It!

- Oleg Nechiporenko


On Nov. 11, 2014, 12:46 p.m., Andrii Tkach wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27864/
> ---
> 
> (Updated Nov. 11, 2014, 12:46 p.m.)
> 
> 
> Review request for Ambari, Oleg Nechiporenko and Yusaku Sako.
> 
> 
> Bugs: AMBARI-8274
> https://issues.apache.org/jira/browse/AMBARI-8274
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*
> 
> 
> Diffs
> -
> 
>   ambari-web/app/data/secure_mapping.js cfca947 
>   ambari-web/app/data/secure_properties.js 5d01943 
> 
> Diff: https://reviews.apache.org/r/27864/diff/
> 
> 
> Testing
> ---
> 
> Tested manually
> 
> 
> Thanks,
> 
> Andrii Tkach
> 
>

[jira] [Commented] (AMBARI-8274) Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8274:
---

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

This message is automatically generated.

> Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*
> --
>
> Key: AMBARI-8274
> URL: https://issues.apache.org/jira/browse/AMBARI-8274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8274.patch, AMBARI-8274_branch-1.7.0.patch
>
>




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

[jira] [Commented] (AMBARI-8273) 'History Server' panel disappeared after deploy Ambari (Stack 1.3)

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8273:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #198 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/198/])
AMBARI-8273. 'History Server' panel disappeared after deploy Ambari (Stack 
1.3). (akovalenko) (akovalenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=11e7c9f60fc26e0964200b6f5d78c28f8f3e9dde)
* ambari-web/app/controllers/main/service/info/configs.js


> 'History Server' panel disappeared after deploy Ambari (Stack 1.3)
> --
>
> Key: AMBARI-8273
> URL: https://issues.apache.org/jira/browse/AMBARI-8273
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8273.patch
>
>




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

[jira] [Updated] (AMBARI-7753) DataNode decommision error in secured cluster

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-7753:
---
Fix Version/s: 2.0.0

> DataNode decommision error in secured cluster
> -
>
> Key: AMBARI-7753
> URL: https://issues.apache.org/jira/browse/AMBARI-7753
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, stacks
>Affects Versions: 1.6.1
> Environment: Ambari-1.6.1 with HDP-2.1.5
>Reporter: jaehoon ko
>  Labels: patch
> Fix For: 2.0.0
>
> Attachments: AMBARI-7753.patch
>
>
> Decommissioning a DataNode from a secured cluster returns errors with the 
> following messages
> {code}
> STDERR: 
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 111, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
>  line 66, in decommission
> namenode(action="decommission")
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 70, in namenode
> decommission()
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 145, in 
> decommission
> user=hdfs_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 148, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 149, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 115, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in 
> Kerberos database while getting initial 
> credentials
> {code}
> {code}
> STDOUT:
> 2014-10-13 10:37:31,793 - File['/etc/hadoop/conf/dfs.exclude'] {'owner': 
> 'hdfs', 'content': Template
> ('exclude_hosts_list.j2'), 'group': 'hadoop'}
> 2014-10-13 10:37:31,796 - Writing File['/etc/hadoop/conf/dfs.exclude'] 
> because contents don't match
> 2014-10-13 10:37:31,797 - Execute['/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;'] {'user': 'hdfs'}
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 111, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
>  line 66, in decommission
> namenode(action="decommission")
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 70, in namenode
> decommission()
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 145, in 
> decommission
> user=hdfs_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 148, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 149, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 115, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in 
> Kerberos database while getting initial 
> credentials
> {code}
> The reason is that Ambar-agent uses DataNode principal to perform HDFS 
> refresh, which should be done as NameNode. This error can be solved by 
> letting Ambari-agent uses NameNode kerberos principal and keytab. Note that 
> [AMBARI-5729|https://issues.apache.org/jira/browse/AMBARI-5729] solves 
> similar issue for NodeManager.



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

Review Request 27866: DataNode decommision error in secured cluster

[Dmytro Sen]

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

Review request for Ambari, Dmitro Lisnichenko and Vitalyi Brodetskyi.


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


Repository: ambari


Description
---

Decommissioning a DataNode from a secured cluster returns errors with the 
following messages
STDERR: 
2014-10-13 10:37:31,896 - Error while executing command 'decommission':
Traceback (most recent call last):
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 111, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
 line 66, in decommission
namenode(action="decommission")
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
 line 70, in namenode
decommission()
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
 line 145, in 

decommission
user=hdfs_user
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 148, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 149, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 115, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
 line 239, in action_run
raise ex
Fail: Execution of '/usr/bin/kinit -kt /etc/security/keytabs/dn.service.keytab 
dn/master-

6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in 
Kerberos database while getting initial 

credentials


Diffs
-

  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py
 c4b48c6 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
 edc823b 
  
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py
 9a48f7b 
  
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py
 45f9d36 
  ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py aba2301 

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


Testing
---

--
Ran 251 tests in 3.139s

OK
--
Total run:693
Total errors:0
Total failures:0
OK


Thanks,

Dmytro Sen

Re: Review Request 27866: DataNode decommision error in secured cluster

[Vitalyi Brodetskyi]

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

Ship it!


Ship It!

- Vitalyi Brodetskyi


On Лис. 11, 2014, 1:36 після полудня, Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27866/
> ---
> 
> (Updated Лис. 11, 2014, 1:36 після полудня)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-7753
> https://issues.apache.org/jira/browse/AMBARI-7753
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Decommissioning a DataNode from a secured cluster returns errors with the 
> following messages
> STDERR: 
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 111, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
>  line 66, in decommission
> namenode(action="decommission")
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 70, in namenode
> decommission()
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 145, in 
> 
> decommission
> user=hdfs_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 148, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 149, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 115, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in 
> Kerberos database while getting initial 
> 
> credentials
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py
>  c4b48c6 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
>  edc823b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py
>  9a48f7b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py
>  45f9d36 
>   ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py aba2301 
> 
> Diff: https://reviews.apache.org/r/27866/diff/
> 
> 
> Testing
> ---
> 
> --
> Ran 251 tests in 3.139s
> 
> OK
> --
> Total run:693
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Updated] (AMBARI-8247) Provide a way to get service-specific Kerberos descriptor via REST API

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-8247:
-
Attachment: AMBARI-8247_01.patch

* Added {{kerberos_descriptor}} block to {{ServiceStack}} API response. 
* Added reference to the _kerberos descriptor file_ to 
{{org.apache.ambari.server.stack.ServiceDirectory}},  
{{org.apache.ambari.server.state.ServiceInfo}} and 
{{org.apache.ambari.server.stack.ServiceModule}}, which is expected to be a 
JSON-formatted file in a service definition named {{kerberos.json}} and meeting 
the appropriate kerberos descriptor specification
* Added/Updated appropriate unit tests.

Patch file [^AMBARI-8247_01.patch]

> Provide a way to get service-specific Kerberos descriptor via REST API
> --
>
> Key: AMBARI-8247
> URL: https://issues.apache.org/jira/browse/AMBARI-8247
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: api, service, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8247_01.patch
>
>
> Provide a way for a caller via the REST API to get information about a 
> service's Kerberos descriptor.  This information should probably be attached 
> to a service resource response.



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

Re: Review Request 27700: Allow for server-side commands

[Robert Levas]

> On Nov. 10, 2014, 11:32 a.m., Robert Nettleton wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionExecutor.java,
> >  line 41
> > 
> >
> > I think the methods in this class might need to be re-arranged, such 
> > that the public methods are ordered before private methods.  
> > 
> > I'm not totally sure about this, but most of the Ambari code I've seen 
> > follows this standard.

I didn't notice this convention in the coding guide Wiki - 
https://cwiki.apache.org/confluence/display/AMBARI/Coding+Guidelines+for+Ambari 
- but will reorder my methods.


> On Nov. 10, 2014, 11:32 a.m., Robert Nettleton wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionExecutor.java,
> >  line 44
> > 
> >
> > Should these two timeout values be configurable?  Are there any cases 
> > where this might require some tuning, based on the size of the cluster 
> > being started?

The time out values are configurable:
* EXECUTION_TIMEOUT_MS - from determineTimeout method, where the 
EXECUTION_TIMEOUT_MS is used if a timeout value is not set in the command 
parameters (ExecutionCommand.KeyNames.COMMAND_TIMEOUT)
* POLLING_TIMEOUT_MS - from the constructor.


> On Nov. 10, 2014, 11:32 a.m., Robert Nettleton wrote:
> > ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionDBAccessorImpl.java,
> >  line 305
> > 
> >
> > Is there any way to re-write this test, so that it doesn't spawn a new 
> > thread?  
> > 
> > Since the change is related to concurrency, perhaps there isn't another 
> > way around this, but it might make sense to see if this can be tested in a 
> > slightly different fashion.
> > 
> > I know we've had problems in the past with unit tests that spawn 
> > threads, so I thought it made sense to mention this here.

Similar tests to this create a thread as well - see testHostRoleScheduled and 
testCustomActionScheduled.


> On Nov. 10, 2014, 11:32 a.m., Robert Nettleton wrote:
> > ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java,
> >  line 654
> > 
> >
> > I'm a little worried by the presence of the sleep here.  
> > 
> > It might be worth considering making this a functional test instead?  
> > 
> > Again, just concerned about the unit tests having intermittent failures 
> > due to concurrency problems.

We really need to sleep here so that the scheduler and executer have time to 
run - which are in different threads.  The idea is that a tasks a scheuled and 
we are polling its status to see when it is completed.. then we make sure its 
status is what was expected. I don't think there is another way around it.


> On Nov. 10, 2014, 11:32 a.m., Robert Nettleton wrote:
> > ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java,
> >  line 740
> > 
> >
> > Same concern here about the sleep() call as above.

Same response as above.. ;)


> On Nov. 10, 2014, 11:32 a.m., Robert Nettleton wrote:
> > ambari-server/src/test/python/org/apache/ambari/server/serveraction/ServerActionExecutorTest.java,
> >  line 47
> > 
> >
> > See my note above regarding the method ordering for classes in Ambari.

Will be reordered.


> On Nov. 10, 2014, 11:32 a.m., Robert Nettleton wrote:
> > ambari-server/src/test/python/org/apache/ambari/server/serveraction/ServerActionExecutorTest.java,
> >  line 159
> > 
> >
> > Does the mock action object keep these tests from being truly 
> > concurrent?  
> > 
> > Is there any change of an intermittent failure in these types of tests?

The MockServerAction does not care about being in a thread or not.  Technically 
I might even consider removing the MockServerAction class and using a Mock 
instead.


- Robert


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


On Nov. 10, 2014, 9:05 a.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27700/
> ---
> 
> (Updated Nov. 10, 2014, 9:05 a.m.)
> 
> 
> Review request for Ambari, dilli dorai, Jonathan Hurley, John Speidel, Nate 
> Cole, Robert Nettleto

[jira] [Updated] (AMBARI-7985) Allow for server-side commands

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-7985:
-
Attachment: AMBARI-7985_03.patch

Reordered methods so that public methods appear before private methods - as 
requested.

> Allow for server-side commands
> --
>
> Key: AMBARI-7985
> URL: https://issues.apache.org/jira/browse/AMBARI-7985
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: ambari-server, commands, server, server-side, tasks
> Fix For: 2.0.0
>
> Attachments: AMBARI-7985_01.patch, AMBARI-7985_01.patch, 
> AMBARI-7985_02.patch, AMBARI-7985_03.patch
>
>
> Ambari currently handles _client-/agent-side_ commands; however there is no 
> ability to handle _server-side_ commands. Server-side commands should be 
> specified as a task in a stage and managed along with the stage.
> *Use Case:*  Generate principals and keytabs on the Ambari server before 
> sending the keytabs to their relevant hosts.
> *Implementation:*  To add the concept of a server-side task:
> * update {{org.apache.ambari.server.serveraction.ServerAction}} to be an 
> _abstract class_
> ** _server-side_ tasks must implement this class 
> * reuse existing _host_role_command_ and _execution_command_ data
> ** _server-side_ tasks are to have a role of {{AMBARI_SERVER_ACTION}}
> ** _server-side_  execution command data should be encapsulated as JSON and 
> specify the ServerAction implementation class and any needed payload data
> * {{org.apache.ambari.server.actionmanager.ActionScheduler}} and 
> {{org.apache.ambari.server.serveraction.ServerActionManagerImpl}} need to be 
> updated to handle the execution of server-side tasks
> ** each _server-side_ task should be executed in its own thread.
> *** _server_side_ tasks should be executed in (staged) order, serially - not 
> in parallel
> *** _server_side_ tasks should ensure not to mess up _stage_ ordering



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

[jira] [Commented] (AMBARI-8247) Provide a way to get service-specific Kerberos descriptor via REST API

[Robert Levas (JIRA)]

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

Robert Levas commented on AMBARI-8247:
--

[~jspeidel], 

I hope that I implemented this properly, according to the API conventions.  

Essentially in 
{{org.apache.ambari.server.controller.internal.StackServiceResourceProvider}} I 
am setting a {{Map}} of the contents of the {{kerberos.json}} file into the 
{{Resource}} using the {{propertyId}} of {{StackServices/kerberos_descriptor}}. 

> Provide a way to get service-specific Kerberos descriptor via REST API
> --
>
> Key: AMBARI-8247
> URL: https://issues.apache.org/jira/browse/AMBARI-8247
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: api, service, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8247_01.patch
>
>
> Provide a way for a caller via the REST API to get information about a 
> service's Kerberos descriptor.  This information should probably be attached 
> to a service resource response.



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

Re: Review Request 27866: DataNode decommision error in secured cluster

[Dmitro Lisnichenko]

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

Ship it!


Ship It!

- Dmitro Lisnichenko


On Nov. 11, 2014, 1:36 p.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27866/
> ---
> 
> (Updated Nov. 11, 2014, 1:36 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-7753
> https://issues.apache.org/jira/browse/AMBARI-7753
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Decommissioning a DataNode from a secured cluster returns errors with the 
> following messages
> STDERR: 
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 111, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
>  line 66, in decommission
> namenode(action="decommission")
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 70, in namenode
> decommission()
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 145, in 
> 
> decommission
> user=hdfs_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 148, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 149, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 115, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in 
> Kerberos database while getting initial 
> 
> credentials
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py
>  c4b48c6 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
>  edc823b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py
>  9a48f7b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py
>  45f9d36 
>   ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py aba2301 
> 
> Diff: https://reviews.apache.org/r/27866/diff/
> 
> 
> Testing
> ---
> 
> --
> Ran 251 tests in 3.139s
> 
> OK
> --
> Total run:693
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Updated] (AMBARI-7450) Add UI Wizard to facilitate configuring cluster to use Kerberos

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-7450:
-
Assignee: Jaimin D Jetly  (was: Robert Levas)

> Add UI Wizard to facilitate configuring cluster to use Kerberos
> ---
>
> Key: AMBARI-7450
> URL: https://issues.apache.org/jira/browse/AMBARI-7450
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Jaimin D Jetly
>  Labels: kerberos, ui, wizard
> Fix For: 2.0.0
>
> Attachments: kerberos-enable-security-wizard-v2.pdf
>
>
> Create a wizard in the web-base interface to help users configure Kerberos on 
> the cluster. 
> See [Ambari Cluster Kerberization Technical 
> Document|https://issues.apache.org/jira/secure/attachment/12667192/AmbariClusterKerberization.pdf]
>  for more information.



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

Re: Can't require('fs') in ambari-web controllers

[Tim]

Yusaku Sako,

I've been learning about ember and how client side frameworks work only
recently. We have a script we'd like to run with user input during ambari
setup in order to prepare the nodes. We have three or four different LANs
for each node, and the script makes sure we're using the right LAN and
hostname on each node. This isn't a use case that makes sense for anyone
but Unisys and our clusters.

So, I've added a step 3.5 to the install wizard in ambari-web which seems
to work fine. However, it needs to give ambari-server the user input, have
ambari-server save it to a file, and then wait for ambari-server to invoke
and finish running the script.

I've tried looking at how the other install wizard steps interact with
ambari-server, but it doesn't make sense just yet. If you could let me know
where to look in ambari-server, that would be help a lot.

Thanks,
Tim Schoenheider

2014-11-10 18:33 GMT-06:00 Yusaku Sako :

> If you can describe your concrete use case, we may be able to help you with
> what kind of changes should be made where.
>
> Yusaku
>
> On Mon, Nov 10, 2014 at 4:30 PM, Yusaku Sako 
> wrote:
>
> > Hi Tim,
> >
> > Ambari-web code runs on the browser (it's not server-side JavaScript).
> > Ambari-web communicates with ambari-server over REST and REST only.
> > So if you want to log stuff on the server, you need to modify
> > ambari-server code.
> >
> > Yusaku
> >
> > On Sun, Nov 9, 2014 at 10:31 AM, Tim  wrote:
> >
> >> Srimanth Gunturi,
> >>
> >> We have a bash script that we'd like to run during the ambari install
> >> wizard. I'm trying to add another step to the wizard that can invoke the
> >> script. I'm not understanding ember as a client-side framework and how
> >> ambari does things on the server (such as writing to disk). We wouldn't
> >> submit these changes back to the community since they're oddly specific
> to
> >> our setup.
> >>
> >> Thanks,
> >> Tim Schoenheider
> >>
> >> 2014-11-08 14:01 GMT-06:00 Srimanth Gunturi :
> >>
> >> > Hi Tim,
> >> > I was hoping if you could elaborate on the use-case of why Ambari UI
> >> should
> >> > access the filesystem?
> >> > Regards,
> >> > Srimanth
> >> >
> >> >
> >> > On Sat, Nov 8, 2014 at 11:44 AM, Tim  wrote:
> >> >
> >> > > Hello again,
> >> > >
> >> > > I'm trying to do something like "var fs = require('fs')" somewhere
> in
> >> > > ambari-web so that I can write to a file in a controller. Adding it
> to
> >> > > "ambari-web\app\controllers\wizard\step3_controller.js", I get
> >> > >
> >> > > Uncaught Error: Cannot find module "fs" from
> >> > > "controllers/wizard/step3_controller"
> >> > >
> >> > >
> >> > > I get similar errors/exceptions when adding to app.js or
> installer.js
> >> > too.
> >> > > My question is, how can I either require this module or write to a
> >> file
> >> > in
> >> > > one of ambari's controllers?
> >> > >
> >> > > Is it likely that something is wrong with my setup/node
> installation?
> >> It
> >> > > seems that this should always work.
> >> > >
> >> > > I've tried this on a clean ambari-web without any of my changes,
> >> > following
> >> > >
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/AMBARI/Coding+Guidelines+for+Ambari
> >> > > to acquire and build it.
> >> > >
> >> > > Thanks,
> >> > > Tim Schoenheider
> >> > >
> >> >
> >> > --
> >> > CONFIDENTIALITY NOTICE
> >> > NOTICE: This message is intended for the use of the individual or
> >> entity to
> >> > which it is addressed and may contain information that is
> confidential,
> >> > privileged and exempt from disclosure under applicable law. If the
> >> reader
> >> > of this message is not the intended recipient, you are hereby notified
> >> that
> >> > any printing, copying, dissemination, distribution, disclosure or
> >> > forwarding of this communication is strictly prohibited. If you have
> >> > received this communication in error, please contact the sender
> >> immediately
> >> > and delete it from your system. Thank You.
> >> >
> >>
> >
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

[jira] [Created] (AMBARI-8275) Ambari does not allow Heterogenous Storage directory configuration

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-8275:


 Summary: Ambari does not allow Heterogenous Storage directory 
configuration
 Key: AMBARI-8275
 URL: https://issues.apache.org/jira/browse/AMBARI-8275
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 1.7.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
 Fix For: 1.7.0


Add uppercase to the validation



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

[jira] [Updated] (AMBARI-8275) Ambari does not allow Heterogenous Storage directory configuration

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-8275:
-
Attachment: AMBARI-8275_branch-1.7.0.patch
AMBARI-8275.patch

> Ambari does not allow Heterogenous Storage directory configuration
> --
>
> Key: AMBARI-8275
> URL: https://issues.apache.org/jira/browse/AMBARI-8275
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8275.patch, AMBARI-8275_branch-1.7.0.patch
>
>
> Add uppercase to the validation



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

[jira] [Commented] (AMBARI-8275) Ambari does not allow Heterogenous Storage directory configuration

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-8275:
-

+1 for the patch

> Ambari does not allow Heterogenous Storage directory configuration
> --
>
> Key: AMBARI-8275
> URL: https://issues.apache.org/jira/browse/AMBARI-8275
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8275.patch, AMBARI-8275_branch-1.7.0.patch
>
>
> Add uppercase to the validation



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

[jira] [Updated] (AMBARI-7985) Allow for server-side commands

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-7985:
-
Attachment: AMBARI-7985_03.patch

> Allow for server-side commands
> --
>
> Key: AMBARI-7985
> URL: https://issues.apache.org/jira/browse/AMBARI-7985
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: ambari-server, commands, server, server-side, tasks
> Fix For: 2.0.0
>
> Attachments: AMBARI-7985_01.patch, AMBARI-7985_01.patch, 
> AMBARI-7985_02.patch, AMBARI-7985_03.patch
>
>
> Ambari currently handles _client-/agent-side_ commands; however there is no 
> ability to handle _server-side_ commands. Server-side commands should be 
> specified as a task in a stage and managed along with the stage.
> *Use Case:*  Generate principals and keytabs on the Ambari server before 
> sending the keytabs to their relevant hosts.
> *Implementation:*  To add the concept of a server-side task:
> * update {{org.apache.ambari.server.serveraction.ServerAction}} to be an 
> _abstract class_
> ** _server-side_ tasks must implement this class 
> * reuse existing _host_role_command_ and _execution_command_ data
> ** _server-side_ tasks are to have a role of {{AMBARI_SERVER_ACTION}}
> ** _server-side_  execution command data should be encapsulated as JSON and 
> specify the ServerAction implementation class and any needed payload data
> * {{org.apache.ambari.server.actionmanager.ActionScheduler}} and 
> {{org.apache.ambari.server.serveraction.ServerActionManagerImpl}} need to be 
> updated to handle the execution of server-side tasks
> ** each _server-side_ task should be executed in its own thread.
> *** _server_side_ tasks should be executed in (staged) order, serially - not 
> in parallel
> *** _server_side_ tasks should ensure not to mess up _stage_ ordering



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

[jira] [Updated] (AMBARI-7985) Allow for server-side commands

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-7985:
-
Attachment: (was: AMBARI-7985_03.patch)

> Allow for server-side commands
> --
>
> Key: AMBARI-7985
> URL: https://issues.apache.org/jira/browse/AMBARI-7985
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: ambari-server, commands, server, server-side, tasks
> Fix For: 2.0.0
>
> Attachments: AMBARI-7985_01.patch, AMBARI-7985_01.patch, 
> AMBARI-7985_02.patch, AMBARI-7985_03.patch
>
>
> Ambari currently handles _client-/agent-side_ commands; however there is no 
> ability to handle _server-side_ commands. Server-side commands should be 
> specified as a task in a stage and managed along with the stage.
> *Use Case:*  Generate principals and keytabs on the Ambari server before 
> sending the keytabs to their relevant hosts.
> *Implementation:*  To add the concept of a server-side task:
> * update {{org.apache.ambari.server.serveraction.ServerAction}} to be an 
> _abstract class_
> ** _server-side_ tasks must implement this class 
> * reuse existing _host_role_command_ and _execution_command_ data
> ** _server-side_ tasks are to have a role of {{AMBARI_SERVER_ACTION}}
> ** _server-side_  execution command data should be encapsulated as JSON and 
> specify the ServerAction implementation class and any needed payload data
> * {{org.apache.ambari.server.actionmanager.ActionScheduler}} and 
> {{org.apache.ambari.server.serveraction.ServerActionManagerImpl}} need to be 
> updated to handle the execution of server-side tasks
> ** each _server-side_ task should be executed in its own thread.
> *** _server_side_ tasks should be executed in (staged) order, serially - not 
> in parallel
> *** _server_side_ tasks should ensure not to mess up _stage_ ordering



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

[jira] [Commented] (AMBARI-8275) Ambari does not allow Heterogenous Storage directory configuration

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-8275:
--

+1 for the patch.

> Ambari does not allow Heterogenous Storage directory configuration
> --
>
> Key: AMBARI-8275
> URL: https://issues.apache.org/jira/browse/AMBARI-8275
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8275.patch, AMBARI-8275_branch-1.7.0.patch
>
>
> Add uppercase to the validation



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

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

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-8276:
---

 Summary: Alerts: Remove Nagios Service From The Stack
 Key: AMBARI-8276
 URL: https://issues.apache.org/jira/browse/AMBARI-8276
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
 Fix For: 2.0.0


With the new alerting framework in place, the Nagios stack files can start to 
be removed. This involves many different steps between the server, the web 
client, and the agent.

In this Jira, we will track the removal of the stack resources. This means:

- Remove files in src/main/resources/stacks/*/services/NAGIOS
- Remove files in test/main/resources/stacks/*/services/NAGIOS
- Associated tests that depend on Nagios must be either removed if irrelevent 
or rewritten

This effort should leave Ambari in a state where the web client and blueprints 
can still successfully install a non-Nagios cluster. Once installed, the 
cluster will operate normally with the exception that alerts will not be 
surfaced by the web client until they have switched over to the new alert 
framework.



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

[jira] [Commented] (AMBARI-8249) Usability: Configs Tab UI responsiveness issues

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander commented on AMBARI-8249:
-

Committed to trunk 

> Usability: Configs Tab UI responsiveness issues
> ---
>
> Key: AMBARI-8249
> URL: https://issues.apache.org/jira/browse/AMBARI-8249
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8249.patch, AMBARI-8249_1.7.0.patch
>
>
> The Ambari "Properties filter" (Configs tab) is slow / cpu hog. It would be 
> really handy if it worked fast. I especially like the fact that is also 
> searches the notes, which means we can lookup properties by canonical name.  
> In addition to the properties filter, we need to review the whole Configs tab 
> user experience for responsiveness.



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

[jira] [Created] (AMBARI-8277) Create facility to get and set kerberos plans via REST API

[Robert Levas (JIRA)]

Robert Levas created AMBARI-8277:


 Summary: Create facility to get and set kerberos plans via REST API
 Key: AMBARI-8277
 URL: https://issues.apache.org/jira/browse/AMBARI-8277
 Project: Ambari
  Issue Type: New Feature
  Components: ambari-server
Affects Versions: 2.0.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Blocker
 Fix For: 2.0.0


To help with _kerberizing_ a cluster, a {{Kerberos Plan}} may be used set 
relevant security properties for a service.

A {{Kerberos Plan}} is essentially composite {{Kerberos Descriptor}} consisting 
of details for an entire cluster (as opposed to just a single service).  The 
details that a Kerberos Plan encapsulates are as follows:
* Cluster-wide Kerberos Identities
* Cluster-wide Kerberos-related configurations
* Service-specific Kerberos Identities
* Service-specific Kerberos-related configurations

An (pseudo) Kerberos Plan may be as follows:

{
  "identities": [
... cluster-wide identity specifications ...
  ],
  "configurations": [
... cluster-wide configuration specifications ...
  ],
  "services": [
{
  ... service-specific specifications ...
  "components": [
... component-specific specifications ...
 ]
}
  ]
}




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

[jira] [Commented] (AMBARI-8275) Ambari does not allow Heterogenous Storage directory configuration

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8275:
---

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12680794/AMBARI-8275_branch-1.7.0.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 .

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

This message is automatically generated.

> Ambari does not allow Heterogenous Storage directory configuration
> --
>
> Key: AMBARI-8275
> URL: https://issues.apache.org/jira/browse/AMBARI-8275
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8275.patch, AMBARI-8275_branch-1.7.0.patch
>
>
> Add uppercase to the validation



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

[jira] [Updated] (AMBARI-8277) Create facility to get and set kerberos plans via REST API

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-8277:
-
Description: 
To help with _kerberizing_ a cluster, a {{Kerberos Plan}} may be used set 
relevant security properties for a service.

A {{Kerberos Plan}} is essentially composite {{Kerberos Descriptor}} consisting 
of details for an entire cluster (as opposed to just a single service).  The 
details that a Kerberos Plan encapsulates are as follows:
* Cluster-wide Kerberos Identities
* Cluster-wide Kerberos-related configurations
* Service-specific Kerberos Identities
* Service-specific Kerberos-related configurations

An (pseudo) Kerberos Plan may be as follows:
{code}
{
  "identities": [
... cluster-wide identity specifications ...
  ],
  "configurations": [
... cluster-wide configuration specifications ...
  ],
  "services": [
{
  ... service-specific specifications ...
  "components": [
... component-specific specifications ...
 ]
}
  ]
}
{code}

  was:
To help with _kerberizing_ a cluster, a {{Kerberos Plan}} may be used set 
relevant security properties for a service.

A {{Kerberos Plan}} is essentially composite {{Kerberos Descriptor}} consisting 
of details for an entire cluster (as opposed to just a single service).  The 
details that a Kerberos Plan encapsulates are as follows:
* Cluster-wide Kerberos Identities
* Cluster-wide Kerberos-related configurations
* Service-specific Kerberos Identities
* Service-specific Kerberos-related configurations

An (pseudo) Kerberos Plan may be as follows:
{code}
  "identities": [
... cluster-wide identity specifications ...
  ],
  "configurations": [
... cluster-wide configuration specifications ...
  ],
  "services": [
{
  ... service-specific specifications ...
  "components": [
... component-specific specifications ...
 ]
}
  ]
}
{code}


> Create facility to get and set kerberos plans via REST API
> --
>
> Key: AMBARI-8277
> URL: https://issues.apache.org/jira/browse/AMBARI-8277
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
>  Labels: api, kerberos, kerberos_plan, resource
> Fix For: 2.0.0
>
>
> To help with _kerberizing_ a cluster, a {{Kerberos Plan}} may be used set 
> relevant security properties for a service.
> A {{Kerberos Plan}} is essentially composite {{Kerberos Descriptor}} 
> consisting of details for an entire cluster (as opposed to just a single 
> service).  The details that a Kerberos Plan encapsulates are as follows:
> * Cluster-wide Kerberos Identities
> * Cluster-wide Kerberos-related configurations
> * Service-specific Kerberos Identities
> * Service-specific Kerberos-related configurations
> An (pseudo) Kerberos Plan may be as follows:
> {code}
> {
>   "identities": [
> ... cluster-wide identity specifications ...
>   ],
>   "configurations": [
> ... cluster-wide configuration specifications ...
>   ],
>   "services": [
> {
>   ... service-specific specifications ...
>   "components": [
> ... component-specific specifications ...
>  ]
> }
>   ]
> }
> {code}



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

[jira] [Updated] (AMBARI-8277) Create facility to get and set kerberos plans via REST API

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-8277:
-
Description: 
To help with _kerberizing_ a cluster, a {{Kerberos Plan}} may be used set 
relevant security properties for a service.

A {{Kerberos Plan}} is essentially composite {{Kerberos Descriptor}} consisting 
of details for an entire cluster (as opposed to just a single service).  The 
details that a Kerberos Plan encapsulates are as follows:
* Cluster-wide Kerberos Identities
* Cluster-wide Kerberos-related configurations
* Service-specific Kerberos Identities
* Service-specific Kerberos-related configurations

An (pseudo) Kerberos Plan may be as follows:
{code}
  "identities": [
... cluster-wide identity specifications ...
  ],
  "configurations": [
... cluster-wide configuration specifications ...
  ],
  "services": [
{
  ... service-specific specifications ...
  "components": [
... component-specific specifications ...
 ]
}
  ]
}
{code}

  was:
To help with _kerberizing_ a cluster, a {{Kerberos Plan}} may be used set 
relevant security properties for a service.

A {{Kerberos Plan}} is essentially composite {{Kerberos Descriptor}} consisting 
of details for an entire cluster (as opposed to just a single service).  The 
details that a Kerberos Plan encapsulates are as follows:
* Cluster-wide Kerberos Identities
* Cluster-wide Kerberos-related configurations
* Service-specific Kerberos Identities
* Service-specific Kerberos-related configurations

An (pseudo) Kerberos Plan may be as follows:

{
  "identities": [
... cluster-wide identity specifications ...
  ],
  "configurations": [
... cluster-wide configuration specifications ...
  ],
  "services": [
{
  ... service-specific specifications ...
  "components": [
... component-specific specifications ...
 ]
}
  ]
}



> Create facility to get and set kerberos plans via REST API
> --
>
> Key: AMBARI-8277
> URL: https://issues.apache.org/jira/browse/AMBARI-8277
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
>  Labels: api, kerberos, kerberos_plan, resource
> Fix For: 2.0.0
>
>
> To help with _kerberizing_ a cluster, a {{Kerberos Plan}} may be used set 
> relevant security properties for a service.
> A {{Kerberos Plan}} is essentially composite {{Kerberos Descriptor}} 
> consisting of details for an entire cluster (as opposed to just a single 
> service).  The details that a Kerberos Plan encapsulates are as follows:
> * Cluster-wide Kerberos Identities
> * Cluster-wide Kerberos-related configurations
> * Service-specific Kerberos Identities
> * Service-specific Kerberos-related configurations
> An (pseudo) Kerberos Plan may be as follows:
> {code}
>   "identities": [
> ... cluster-wide identity specifications ...
>   ],
>   "configurations": [
> ... cluster-wide configuration specifications ...
>   ],
>   "services": [
> {
>   ... service-specific specifications ...
>   "components": [
> ... component-specific specifications ...
>  ]
> }
>   ]
> }
> {code}



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

[jira] [Commented] (AMBARI-7985) Allow for server-side commands

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-7985:
---

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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Allow for server-side commands
> --
>
> Key: AMBARI-7985
> URL: https://issues.apache.org/jira/browse/AMBARI-7985
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: ambari-server, commands, server, server-side, tasks
> Fix For: 2.0.0
>
> Attachments: AMBARI-7985_01.patch, AMBARI-7985_01.patch, 
> AMBARI-7985_02.patch, AMBARI-7985_03.patch
>
>
> Ambari currently handles _client-/agent-side_ commands; however there is no 
> ability to handle _server-side_ commands. Server-side commands should be 
> specified as a task in a stage and managed along with the stage.
> *Use Case:*  Generate principals and keytabs on the Ambari server before 
> sending the keytabs to their relevant hosts.
> *Implementation:*  To add the concept of a server-side task:
> * update {{org.apache.ambari.server.serveraction.ServerAction}} to be an 
> _abstract class_
> ** _server-side_ tasks must implement this class 
> * reuse existing _host_role_command_ and _execution_command_ data
> ** _server-side_ tasks are to have a role of {{AMBARI_SERVER_ACTION}}
> ** _server-side_  execution command data should be encapsulated as JSON and 
> specify the ServerAction implementation class and any needed payload data
> * {{org.apache.ambari.server.actionmanager.ActionScheduler}} and 
> {{org.apache.ambari.server.serveraction.ServerActionManagerImpl}} need to be 
> updated to handle the execution of server-side tasks
> ** each _server-side_ task should be executed in its own thread.
> *** _server_side_ tasks should be executed in (staged) order, serially - not 
> in parallel
> *** _server_side_ tasks should ensure not to mess up _stage_ ordering



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

[jira] [Commented] (AMBARI-7753) DataNode decommision error in secured cluster

[Hudson (JIRA)]

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

Hudson commented on AMBARI-7753:


FAILURE: Integrated in Ambari-trunk-Commit #907 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/907/])
AMBARI-7753 DataNode decommision error in secured cluster (dsen) (dsen: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ba5bc737a13578ca27a2f0f15227248e022d4f38)
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py


> DataNode decommision error in secured cluster
> -
>
> Key: AMBARI-7753
> URL: https://issues.apache.org/jira/browse/AMBARI-7753
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, stacks
>Affects Versions: 1.6.1
> Environment: Ambari-1.6.1 with HDP-2.1.5
>Reporter: jaehoon ko
>  Labels: patch
> Fix For: 2.0.0
>
> Attachments: AMBARI-7753.patch
>
>
> Decommissioning a DataNode from a secured cluster returns errors with the 
> following messages
> {code}
> STDERR: 
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 111, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
>  line 66, in decommission
> namenode(action="decommission")
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 70, in namenode
> decommission()
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 145, in 
> decommission
> user=hdfs_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 148, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 149, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 115, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in 
> Kerberos database while getting initial 
> credentials
> {code}
> {code}
> STDOUT:
> 2014-10-13 10:37:31,793 - File['/etc/hadoop/conf/dfs.exclude'] {'owner': 
> 'hdfs', 'content': Template
> ('exclude_hosts_list.j2'), 'group': 'hadoop'}
> 2014-10-13 10:37:31,796 - Writing File['/etc/hadoop/conf/dfs.exclude'] 
> because contents don't match
> 2014-10-13 10:37:31,797 - Execute['/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;'] {'user': 'hdfs'}
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 111, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
>  line 66, in decommission
> namenode(action="decommission")
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 70, in namenode
> decommission()
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 145, in 
> decommission
> user=hdfs_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 148, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 149, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 115, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbclust

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

[Artem Baranchuk (JIRA)]

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

Artem Baranchuk updated AMBARI-8278:

Summary: Database Host for HadoopMetrics, Hive Oozie should be set to 
corresponding server host name  (was: BUG-27202 - Database Host for 
HadoopMetrics, Hive Oozie should be set to corresponding server host name)

> 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] [Created] (AMBARI-8278) BUG-27202 - Database Host for HadoopMetrics, Hive Oozie should be set to corresponding server host name

[Artem Baranchuk (JIRA)]

Artem Baranchuk created AMBARI-8278:
---

 Summary: BUG-27202 - 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-7753) DataNode decommision error in secured cluster

[Hudson (JIRA)]

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

Hudson commented on AMBARI-7753:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #199 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/199/])
AMBARI-7753 DataNode decommision error in secured cluster (dsen) (dsen: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ba5bc737a13578ca27a2f0f15227248e022d4f38)
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py
* 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py


> DataNode decommision error in secured cluster
> -
>
> Key: AMBARI-7753
> URL: https://issues.apache.org/jira/browse/AMBARI-7753
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, stacks
>Affects Versions: 1.6.1
> Environment: Ambari-1.6.1 with HDP-2.1.5
>Reporter: jaehoon ko
>  Labels: patch
> Fix For: 2.0.0
>
> Attachments: AMBARI-7753.patch
>
>
> Decommissioning a DataNode from a secured cluster returns errors with the 
> following messages
> {code}
> STDERR: 
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 111, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
>  line 66, in decommission
> namenode(action="decommission")
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 70, in namenode
> decommission()
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 145, in 
> decommission
> user=hdfs_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 148, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 149, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 115, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in 
> Kerberos database while getting initial 
> credentials
> {code}
> {code}
> STDOUT:
> 2014-10-13 10:37:31,793 - File['/etc/hadoop/conf/dfs.exclude'] {'owner': 
> 'hdfs', 'content': Template
> ('exclude_hosts_list.j2'), 'group': 'hadoop'}
> 2014-10-13 10:37:31,796 - Writing File['/etc/hadoop/conf/dfs.exclude'] 
> because contents don't match
> 2014-10-13 10:37:31,797 - Execute['/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;'] {'user': 'hdfs'}
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 111, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
>  line 66, in decommission
> namenode(action="decommission")
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 70, in namenode
> decommission()
>   File 
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
>  line 145, in 
> decommission
> user=hdfs_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 148, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 149, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 115, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl

[jira] [Updated] (AMBARI-7985) Allow for server-side commands

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-7985:
-
Attachment: AMBARI-7985_03.patch

Re-attaching patch to trigger Hadoop QA process since last run failed due to 
issues not related to my changes.

bq. [ERROR] Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:0.0.14:install-node-and-npm (install 
node and npm) on project ambari-admin: Could not download Node.js: Could not 
download http://nodejs.org/dist/v0.10.26/node-v0.10.26-linux-x86.tar.gz -> 
[Help 1]



> Allow for server-side commands
> --
>
> Key: AMBARI-7985
> URL: https://issues.apache.org/jira/browse/AMBARI-7985
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: ambari-server, commands, server, server-side, tasks
> Fix For: 2.0.0
>
> Attachments: AMBARI-7985_01.patch, AMBARI-7985_01.patch, 
> AMBARI-7985_02.patch, AMBARI-7985_03.patch, AMBARI-7985_03.patch
>
>
> Ambari currently handles _client-/agent-side_ commands; however there is no 
> ability to handle _server-side_ commands. Server-side commands should be 
> specified as a task in a stage and managed along with the stage.
> *Use Case:*  Generate principals and keytabs on the Ambari server before 
> sending the keytabs to their relevant hosts.
> *Implementation:*  To add the concept of a server-side task:
> * update {{org.apache.ambari.server.serveraction.ServerAction}} to be an 
> _abstract class_
> ** _server-side_ tasks must implement this class 
> * reuse existing _host_role_command_ and _execution_command_ data
> ** _server-side_ tasks are to have a role of {{AMBARI_SERVER_ACTION}}
> ** _server-side_  execution command data should be encapsulated as JSON and 
> specify the ServerAction implementation class and any needed payload data
> * {{org.apache.ambari.server.actionmanager.ActionScheduler}} and 
> {{org.apache.ambari.server.serveraction.ServerActionManagerImpl}} need to be 
> updated to handle the execution of server-side tasks
> ** each _server-side_ task should be executed in its own thread.
> *** _server_side_ tasks should be executed in (staged) order, serially - not 
> in parallel
> *** _server_side_ tasks should ensure not to mess up _stage_ ordering



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

Review Request 27870: Alerts: Remove Nagios Service From The Stack

[Jonathan Hurley]

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

Review request for Ambari, Dmytro Sen, Nate Cole, Srimanth Gunturi, Tom 
Beerbower, and Yusaku Sako.


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


Repository: ambari


Description
---

With the new alerting framework in place, the Nagios stack files can start to 
be removed. This involves many different steps between the server, the web 
client, and the agent.

In this Jira, we will track the removal of the stack resources. This means:

- Remove files in src/main/resources/stacks/*/services/NAGIOS
- Remove files in test/main/resources/stacks/*/services/NAGIOS
- Associated tests that depend on Nagios must be either removed if irrelevent 
or rewritten

This effort should leave Ambari in a state where the web client and blueprints 
can still successfully install a non-Nagios cluster. Once installed, the 
cluster will operate normally with the exception that alerts will not be 
surfaced by the web client until they have switched over to the new alert 
framework.


Diffs
-

  
ambari-server/src/main/resources/custom_action_definitions/system_action_definitions.xml
 c65a496 
  ambari-server/src/main/resources/custom_actions/nagios_update_ignore.py 
b7026e2 
  ambari-server/src/main/resources/custom_actions/validate_configs.py c245dbb 
  ambari-server/src/main/resources/properties.json 36cff96 
  ambari-server/src/main/resources/role_command_order.json c45ba07 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/blueprints/multinode-default.json
 642fcfa 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/blueprints/singlenode-default.json
 3c769dd 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/params.py
 01789a7 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py
 ac8f1c8 
  ambari-server/src/main/resources/stacks/BIGTOP/0.8/role_command_order.json 
69fcdac 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/files/gmondLib.sh
 e7ea83f 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
 83b2ed9 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/configuration/nagios-env.xml
 fad8374 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/metainfo.xml 
bebc7d6 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_aggregate.php
 792b25b 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_ambari_alerts.py
 833a798 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_checkpoint_time.py
 ab889d1 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu.php
 0744e38 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu.pl
 a5680f7 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu_ha.php
 91a7c64 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_datanode_storage.php
 dee22b4 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hdfs_blocks.php
 3693aa0 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hdfs_capacity.php
 af72723 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hive_metastore_status.sh
 640c077 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hue_status.sh
 076d9b3 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_mapred_local_dir_used.sh
 3f9243a 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_name_dir_status.php
 186166d 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_namenodes_ha.sh
 83c1aca 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_nodemanager_health.sh
 eedcd62 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_oozie_status.sh
 820ee99 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_rpcq_latency.php
 463f69b 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_rpcq_latency_ha.php
 3e7616c 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_templeton_status.sh
 3e2ba0f 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_webui.sh
 7044878 
  
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_webui_ha.sh
 d9a814d 
  
ambari-server/s

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

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-8276:

Attachment: AMBARI-8276.patch

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



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

[jira] [Commented] (AMBARI-8249) Usability: Configs Tab UI responsiveness issues

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8249:


SUCCESS: Integrated in Ambari-trunk-Commit #908 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/908/])
AMBARI-8249. Usability: Configs Tab UI responsiveness issues (alexantonenko) 
(hiveww: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6c94df6b24251e8eb111096d81ab61ce3fd4f83e)
* ambari-web/app/views/common/configs/services_config.js
* ambari-web/app/templates/common/configs/service_config_category.hbs
* ambari-web/test/views/common/configs/services_config_test.js
* ambari-web/app/models/service_config.js


> Usability: Configs Tab UI responsiveness issues
> ---
>
> Key: AMBARI-8249
> URL: https://issues.apache.org/jira/browse/AMBARI-8249
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8249.patch, AMBARI-8249_1.7.0.patch
>
>
> The Ambari "Properties filter" (Configs tab) is slow / cpu hog. It would be 
> really handy if it worked fast. I especially like the fact that is also 
> searches the notes, which means we can lookup properties by canonical name.  
> In addition to the properties filter, we need to review the whole Configs tab 
> user experience for responsiveness.



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

[jira] [Commented] (AMBARI-8275) Ambari does not allow Heterogenous Storage directory configuration

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8275:


SUCCESS: Integrated in Ambari-branch-1.7.0 #389 (See 
[https://builds.apache.org/job/Ambari-branch-1.7.0/389/])
AMBARI-8275 Ambari does not allow Heterogenous Storage directory configuration. 
(ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=85adda2e641aea5f12ad425feac4058617413975)
* ambari-web/test/utils/validator_test.js
* ambari-web/app/utils/validator.js


> Ambari does not allow Heterogenous Storage directory configuration
> --
>
> Key: AMBARI-8275
> URL: https://issues.apache.org/jira/browse/AMBARI-8275
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8275.patch, AMBARI-8275_branch-1.7.0.patch
>
>
> Add uppercase to the validation



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

[jira] [Commented] (AMBARI-8247) Provide a way to get service-specific Kerberos descriptor via REST API

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8247:
---

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

This message is automatically generated.

> Provide a way to get service-specific Kerberos descriptor via REST API
> --
>
> Key: AMBARI-8247
> URL: https://issues.apache.org/jira/browse/AMBARI-8247
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: api, service, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8247_01.patch
>
>
> Provide a way for a caller via the REST API to get information about a 
> service's Kerberos descriptor.  This information should probably be attached 
> to a service resource response.



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

[jira] [Updated] (AMBARI-8247) Provide a way to get service-specific Kerberos descriptor via REST API

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-8247:
-
Attachment: AMBARI-8247_02.patch

Small fixes in comments and move constant to more "local" location.

Patch File [^AMBARI-8247_02.patch]

> Provide a way to get service-specific Kerberos descriptor via REST API
> --
>
> Key: AMBARI-8247
> URL: https://issues.apache.org/jira/browse/AMBARI-8247
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: api, service, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8247_01.patch, AMBARI-8247_02.patch
>
>
> Provide a way for a caller via the REST API to get information about a 
> service's Kerberos descriptor.  This information should probably be attached 
> to a service resource response.



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

[jira] [Commented] (AMBARI-8247) Provide a way to get service-specific Kerberos descriptor via REST API

[John Speidel (JIRA)]

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

John Speidel commented on AMBARI-8247:
--

I have a concern about the kerberos descriptor being a field within the stack 
service.  The descriptor is quite lengthy and it seems that it should have it's 
own resource.  Then the stack service resource could provide an href to the 
corresponding kerberos descriptor resource.

If the kerberos descriptor is also applicable to stacks, then a distinct 
kerberos descriptor resource is called for.

> Provide a way to get service-specific Kerberos descriptor via REST API
> --
>
> Key: AMBARI-8247
> URL: https://issues.apache.org/jira/browse/AMBARI-8247
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: api, service, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8247_01.patch, AMBARI-8247_02.patch
>
>
> Provide a way for a caller via the REST API to get information about a 
> service's Kerberos descriptor.  This information should probably be attached 
> to a service resource response.



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

Review Request 27871: Provide a way to get service-specific Kerberos descriptor via REST API

[Robert Levas]

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

Review request for Ambari, dilli dorai, John Speidel, Robert Nettleton, and Tom 
Beerbower.


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


Repository: ambari


Description
---

Provide a way for a caller via the REST API to get information about a 
service's Kerberos descriptor. This information should probably be attached to 
a service resource response.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/StackServiceResponse.java
 2794c18 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackServiceResourceProvider.java
 1296ba1 
  
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceDirectory.java
 843df0b 
  ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java 
279361b 
  ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java 
9277ec6 
  ambari-server/src/main/resources/properties.json 36cff96 
  
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
 4d08d6f 
  
ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java
 225213f 
  ambari-server/src/test/resources/stacks/HDP/2.0.8/services/HDFS/kerberos.json 
PRE-CREATION 
  ambari-server/src/test/resources/stacks/HDP/2.1.1/services/HDFS/metainfo.xml 
PRE-CREATION 

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


Testing
---


Thanks,

Robert Levas

[jira] [Commented] (AMBARI-8249) Usability: Configs Tab UI responsiveness issues

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8249:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #200 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/200/])
AMBARI-8249. Usability: Configs Tab UI responsiveness issues (alexantonenko) 
(hiveww: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6c94df6b24251e8eb111096d81ab61ce3fd4f83e)
* ambari-web/test/views/common/configs/services_config_test.js
* ambari-web/app/templates/common/configs/service_config_category.hbs
* ambari-web/app/views/common/configs/services_config.js
* ambari-web/app/models/service_config.js


> Usability: Configs Tab UI responsiveness issues
> ---
>
> Key: AMBARI-8249
> URL: https://issues.apache.org/jira/browse/AMBARI-8249
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8249.patch, AMBARI-8249_1.7.0.patch
>
>
> The Ambari "Properties filter" (Configs tab) is slow / cpu hog. It would be 
> really handy if it worked fast. I especially like the fact that is also 
> searches the notes, which means we can lookup properties by canonical name.  
> In addition to the properties filter, we need to review the whole Configs tab 
> user experience for responsiveness.



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

[jira] [Commented] (AMBARI-8275) Ambari does not allow Heterogenous Storage directory configuration

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8275:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #200 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/200/])
AMBARI-8275 Ambari does not allow Heterogenous Storage directory configuration. 
(ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2fdf2403a15c884d877a6f878661d79cda4ffedc)
* ambari-web/test/utils/validator_test.js
* ambari-web/app/utils/validator.js


> Ambari does not allow Heterogenous Storage directory configuration
> --
>
> Key: AMBARI-8275
> URL: https://issues.apache.org/jira/browse/AMBARI-8275
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8275.patch, AMBARI-8275_branch-1.7.0.patch
>
>
> Add uppercase to the validation



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

[jira] [Commented] (AMBARI-8275) Ambari does not allow Heterogenous Storage directory configuration

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8275:


SUCCESS: Integrated in Ambari-branch-1.7.0-docker #152 (See 
[https://builds.apache.org/job/Ambari-branch-1.7.0-docker/152/])
AMBARI-8275 Ambari does not allow Heterogenous Storage directory configuration. 
(ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=85adda2e641aea5f12ad425feac4058617413975)
* ambari-web/app/utils/validator.js
* ambari-web/test/utils/validator_test.js


> Ambari does not allow Heterogenous Storage directory configuration
> --
>
> Key: AMBARI-8275
> URL: https://issues.apache.org/jira/browse/AMBARI-8275
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8275.patch, AMBARI-8275_branch-1.7.0.patch
>
>
> Add uppercase to the validation



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

[jira] [Created] (AMBARI-8279) Slider View: "+ Create App" button effect is disabled, but is clickable

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-8279:
---

 Summary: Slider View: "+ Create App" button effect is disabled, 
but is clickable
 Key: AMBARI-8279
 URL: https://issues.apache.org/jira/browse/AMBARI-8279
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 1.7.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.0.0


see attached.
On slider view apps table page, the "+ create app" button is disabled.  
But when clicking on this button, a wizard show up.
The user experience is bad.

The same issue for "Actions" button on a slider app view. 

(A button which is clickable should be like good button.png)



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

[jira] [Updated] (AMBARI-8279) Slider View: "+ Create App" button effect is disabled, but is clickable

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-8279:

Attachment: AMBARI-8279.patch

> Slider View: "+ Create App" button effect is disabled, but is clickable
> ---
>
> Key: AMBARI-8279
> URL: https://issues.apache.org/jira/browse/AMBARI-8279
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.0.0
>
> Attachments: AMBARI-8279.patch, Screen Shot 2014-11-05 at 1.03.34 
> PM.png, Screen Shot 2014-11-05 at 1.03.42 PM.png, Screen Shot 2014-11-05 at 
> 1.03.49 PM.png, Screen Shot 2014-11-05 at 1.26.24 PM.png, good button.png
>
>
> see attached.
> On slider view apps table page, the "+ create app" button is disabled.  
> But when clicking on this button, a wizard show up.
> The user experience is bad.
> The same issue for "Actions" button on a slider app view. 
> (A button which is clickable should be like good button.png)



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

[jira] [Updated] (AMBARI-8279) Slider View: "+ Create App" button effect is disabled, but is clickable

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-8279:

Attachment: good button.png
Screen Shot 2014-11-05 at 1.03.34 PM.png
Screen Shot 2014-11-05 at 1.03.42 PM.png
Screen Shot 2014-11-05 at 1.03.49 PM.png
Screen Shot 2014-11-05 at 1.26.24 PM.png

> Slider View: "+ Create App" button effect is disabled, but is clickable
> ---
>
> Key: AMBARI-8279
> URL: https://issues.apache.org/jira/browse/AMBARI-8279
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.0.0
>
> Attachments: AMBARI-8279.patch, Screen Shot 2014-11-05 at 1.03.34 
> PM.png, Screen Shot 2014-11-05 at 1.03.42 PM.png, Screen Shot 2014-11-05 at 
> 1.03.49 PM.png, Screen Shot 2014-11-05 at 1.26.24 PM.png, good button.png
>
>
> see attached.
> On slider view apps table page, the "+ create app" button is disabled.  
> But when clicking on this button, a wizard show up.
> The user experience is bad.
> The same issue for "Actions" button on a slider app view. 
> (A button which is clickable should be like good button.png)



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

Re: Review Request 27802: Rest api's for host component logs.

[John Speidel]

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


Looking at it from a high level API perspective I have two concerns.
1. "download=true"  Adding this special download keyword isn't a good idea.  
This looks like you are querying for all logs where the property 'download' = 
true.  Instead, you should provide a new renderer.  Renderer's allow for 
different renderings of a resource to be returned to the user.  We currently 
have a default, minimal and blueprint renderer.  A summary renderer is also in 
the works.  See org.apache.ambari.server.api.query.render.Renderer for more.  
Specifying a renderer would look like : 
api/v1/hosts/h1/host_components/hc1/logs/log1?format=file  In this case we are 
asking for the "file" rendering of the log1 resource.  I just picked the 
renderer name "file" as an example. When creating a renderer it is registered 
with a name.
2. Why is so much information returned for the logs collection resource?  
Typically it wouls just be an href the pk and fk's.

- John Speidel


On Nov. 10, 2014, 9:04 a.m., Cabir Zounaidou wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27802/
> ---
> 
> (Updated Nov. 10, 2014, 9:04 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, John 
> Speidel, Mahadev Konar, Nate Cole, Sid Wagle, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-4083
> https://issues.apache.org/jira/browse/AMBARI-4083
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The host component log implements the following two rest api's.
> 
> 1. To retrieve the log entries. 
>   /clusters/{cluster}/hosts/{hostname}/host_components/{component}/logs
>   This api will retrieve the logs if available for the host component from 
> HDFS.  It can fetch only maximum of 5120 bytes.  The window can be adjusted 
> using the query parameters 'offset' and 'length'.  It also provides simple 
> filtering using 'level' query parameter.
>   Sample response will look like below:
>   {
>   "href" : 
> "http://c6501.ambari.apache.org:8080/api/v1/clusters/cl1/hosts/c6503.ambari.apache.org/host_components/HBASE_CLIENT/logs";,
>   "items" : [
> {
>   "href" : 
> "http://c6501.ambari.apache.org:8080/api/v1/clusters/cl1/hosts/c6503.ambari.apache.org/host_components/HBASE_CLIENT/logs/HBASE_CLIENT";,
>   "length" : 5120,
>   "level" : null,
>   "offset" : 153920,
>   "size" : 159040,
>   "HostComponentLog" : {
> "cluster_name" : "cl1",
> "component_name" : "HBASE_CLIENT",
> "entries" : [
>   {
> "timestamp" : "2014-11-01 17:46:38,456",
> "level" : "DEBUG",
> "thread" : "main-EventThread",
> "message" : "master.SplitLogManager: task not yet acquired 
> /hbase-unsecure/splitWAL/WALs%2Fc6503.ambari.apache.org%2C60020%2C1414856039721-splitting%2Fc6503.ambari.apache.org%252C60020%252C1414856039721.1414856049592.meta
>  ver = 0"
>   },
>   {
> "timestamp" : "2014-11-01 17:46:38,459",
> "level" : "DEBUG",
> "thread" : "main-EventThread",
> "message" : "master.SplitLogManager: put up splitlog task at 
> znode 
> /hbase-unsecure/splitWAL/WALs%2Fc6503.ambari.apache.org%2C60020%2C1414856039721-splitting%2Fc6503.ambari.apache.org%252C60020%252C1414856039721.1414856050193.meta"
>   },
>   {
> "timestamp" : "2014-11-01 17:46:38,460",
> "level" : "DEBUG",
> "thread" : "main-EventThread",
> "message" : "master.SplitLogManager: put up splitlog task at 
> znode 
> /hbase-unsecure/splitWAL/WALs%2Fc6503.ambari.apache.org%2C60020%2C1414856039721-splitting%2Fc6503.ambari.apache.org%252C60020%252C1414856039721.1414856105560.meta"
>   },
>   :
>   :
> }]
>   }
> ]
>}
> 2. To download the log file from HDFS use the following the api
>   
> /clusters/{cluster}/hosts/{hostname}/host_components/{component}/logs?download=true
>   The response will automatically download the file with the HDFS file name.
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/main/python/ambari_agent/Controller.py dc3a1cf 
>   
> ambari-server/src/main/java/org/apache/ambari/server/agent/AgentCommand.java 
> e2f013d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
>  e99e39f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatResponse.java
>  56b4f18 
>   
> ambari-server/src/main/java/org/apache/ambari/server/agent/LogConfigCommand.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/agent/RegistrationResponse.java
>  8a

[jira] [Commented] (AMBARI-8275) Ambari does not allow Heterogenous Storage directory configuration

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8275:


SUCCESS: Integrated in Ambari-trunk-Commit #909 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/909/])
AMBARI-8275 Ambari does not allow Heterogenous Storage directory configuration. 
(ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2fdf2403a15c884d877a6f878661d79cda4ffedc)
* ambari-web/test/utils/validator_test.js
* ambari-web/app/utils/validator.js


> Ambari does not allow Heterogenous Storage directory configuration
> --
>
> Key: AMBARI-8275
> URL: https://issues.apache.org/jira/browse/AMBARI-8275
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8275.patch, AMBARI-8275_branch-1.7.0.patch
>
>
> Add uppercase to the validation



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

[jira] [Commented] (AMBARI-8279) Slider View: "+ Create App" button effect is disabled, but is clickable

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-8279:
--

+1 for the patch

> Slider View: "+ Create App" button effect is disabled, but is clickable
> ---
>
> Key: AMBARI-8279
> URL: https://issues.apache.org/jira/browse/AMBARI-8279
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.0.0
>
> Attachments: AMBARI-8279.patch, Screen Shot 2014-11-05 at 1.03.34 
> PM.png, Screen Shot 2014-11-05 at 1.03.42 PM.png, Screen Shot 2014-11-05 at 
> 1.03.49 PM.png, Screen Shot 2014-11-05 at 1.26.24 PM.png, good button.png
>
>
> see attached.
> On slider view apps table page, the "+ create app" button is disabled.  
> But when clicking on this button, a wizard show up.
> The user experience is bad.
> The same issue for "Actions" button on a slider app view. 
> (A button which is clickable should be like good button.png)



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

[jira] [Commented] (AMBARI-7985) Allow for server-side commands

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-7985:
---

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

This message is automatically generated.

> Allow for server-side commands
> --
>
> Key: AMBARI-7985
> URL: https://issues.apache.org/jira/browse/AMBARI-7985
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: ambari-server, commands, server, server-side, tasks
> Fix For: 2.0.0
>
> Attachments: AMBARI-7985_01.patch, AMBARI-7985_01.patch, 
> AMBARI-7985_02.patch, AMBARI-7985_03.patch, AMBARI-7985_03.patch
>
>
> Ambari currently handles _client-/agent-side_ commands; however there is no 
> ability to handle _server-side_ commands. Server-side commands should be 
> specified as a task in a stage and managed along with the stage.
> *Use Case:*  Generate principals and keytabs on the Ambari server before 
> sending the keytabs to their relevant hosts.
> *Implementation:*  To add the concept of a server-side task:
> * update {{org.apache.ambari.server.serveraction.ServerAction}} to be an 
> _abstract class_
> ** _server-side_ tasks must implement this class 
> * reuse existing _host_role_command_ and _execution_command_ data
> ** _server-side_ tasks are to have a role of {{AMBARI_SERVER_ACTION}}
> ** _server-side_  execution command data should be encapsulated as JSON and 
> specify the ServerAction implementation class and any needed payload data
> * {{org.apache.ambari.server.actionmanager.ActionScheduler}} and 
> {{org.apache.ambari.server.serveraction.ServerActionManagerImpl}} need to be 
> updated to handle the execution of server-side tasks
> ** each _server-side_ task should be executed in its own thread.
> *** _server_side_ tasks should be executed in (staged) order, serially - not 
> in parallel
> *** _server_side_ tasks should ensure not to mess up _stage_ ordering



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

[jira] [Created] (AMBARI-8280) Create mock for Admin Web: Stack Versions: Version Detail page

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-8280:


 Summary: Create mock for Admin Web: Stack Versions: Version Detail 
page
 Key: AMBARI-8280
 URL: https://issues.apache.org/jira/browse/AMBARI-8280
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
 Fix For: 2.0.0






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

[jira] [Updated] (AMBARI-8280) Create mock for Admin Web: Stack Versions: Version Detail page

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-8280:
-
Attachment: AMBARI-8280.patch

> Create mock for Admin Web: Stack Versions: Version Detail page
> --
>
> Key: AMBARI-8280
> URL: https://issues.apache.org/jira/browse/AMBARI-8280
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8280.patch
>
>




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

Review Request 27876: Create mock for Admin Web: Stack Versions: Version Detail page

[Andriy Babiichuk]

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

Review request for Ambari and Andrii Tkach.


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


Repository: ambari


Description
---

Create mock for Admin Web: Stack Versions: Version Detail page


Diffs
-

  ambari-web/app/assets/data/stack_versions/stack_version_all.json c2651ea 
  ambari-web/app/assets/test/tests.js 2752a0c 
  ambari-web/app/controllers.js 3e4e0da 
  
ambari-web/app/controllers/main/admin/stack_upgrade/stack_version_details_controller.js
 PRE-CREATION 
  ambari-web/app/mappers/stack_version_mapper.js 856bccb 
  ambari-web/app/messages.js f01f9c2 
  ambari-web/app/models/stack_version/version.js b7ede22 
  ambari-web/app/routes/main.js 76c46a5 
  ambari-web/app/styles/application.less df43c1a 
  ambari-web/app/templates/main/admin/stack_versions/stack_version_details.hbs 
PRE-CREATION 
  ambari-web/app/templates/main/admin/stack_versions/stack_versions.hbs 15eba7b 
  ambari-web/app/views.js 842596b 
  ambari-web/app/views/main/admin.js 7c00ed8 
  ambari-web/app/views/main/admin/stack_versions/stack_version_details_view.js 
PRE-CREATION 
  ambari-web/app/views/main/admin/stack_versions/stack_version_view.js b0793b0 
  ambari-web/app/views/main/menu.js 5ab6375 
  ambari-web/test/views/main/admin/stack_version/stack_version_details_test.js 
PRE-CREATION 

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


Testing
---

  5026 tests complete (6 seconds)
  60 tests pending


Thanks,

Andriy Babiichuk

[jira] [Commented] (AMBARI-8280) Create mock for Admin Web: Stack Versions: Version Detail page

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-8280:
--

https://reviews.apache.org/r/27876/

> Create mock for Admin Web: Stack Versions: Version Detail page
> --
>
> Key: AMBARI-8280
> URL: https://issues.apache.org/jira/browse/AMBARI-8280
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8280.patch
>
>




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

Re: Review Request 27700: Allow for server-side commands

[John Speidel]

> On Nov. 10, 2014, 4:32 p.m., Robert Nettleton wrote:
> > ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java,
> >  line 654
> > 
> >
> > I'm a little worried by the presence of the sleep here.  
> > 
> > It might be worth considering making this a functional test instead?  
> > 
> > Again, just concerned about the unit tests having intermittent failures 
> > due to concurrency problems.
> 
> Robert Levas wrote:
> We really need to sleep here so that the scheduler and executer have time 
> to run - which are in different threads.  The idea is that a tasks a scheuled 
> and we are polling its status to see when it is completed.. then we make sure 
> its status is what was expected. I don't think there is another way around it.

I agree with Bob on this and feel strongly that using sleep statements like 
this result in non-deterministic tests.  
I haven't really looked at the ActionScheduler to provide you a solution but 
can give some genral comments on testing of this nature.
- If you can run the test in a single thread, that is always best.  For 
example, sometimes it is possible to call run directly.
- If a separate thread must be used, it is best to have a deterministic way to 
determine if a task has completed.  For example, if you have access to the task 
perhaps it has state that can be queried.
- If you must use another thread and have no way to determine with certainty 
that a task has completed, use a "wait for" approach.  The idea is that you 
have a loop that does an assertion every couple of ms.  You keep looping until 
the assertion holds or until you "timeout" and fail the test.  The timeout 
should be rather long since it is only applicable in the case of a test 
failure. For the successful scenario, the test will not block for long sine we 
are checking the condition in small intervals.


- John


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


On Nov. 10, 2014, 2:05 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27700/
> ---
> 
> (Updated Nov. 10, 2014, 2:05 p.m.)
> 
> 
> Review request for Ambari, dilli dorai, Jonathan Hurley, John Speidel, Nate 
> Cole, Robert Nettleton, and Sid Wagle.
> 
> 
> Bugs: AMBARI-7985
> https://issues.apache.org/jira/browse/AMBARI-7985
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ambari currently handles client-/agent-side commands; however there is no 
> ability to handle server-side commands. Server-side commands should be 
> specified as a task in a stage and managed along with the stage.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessor.java
>  1f99b4a 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java
>  5e879cc 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionManager.java
>  e2fad5f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
>  81fee75 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/Stage.java 
> bbc5ac3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
>  52b0ba6 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostRoleCommandDAO.java
>  6920a9e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/AbstractServerAction.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerAction.java
>  be885b5 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionExecutor.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionManager.java
>  011cf06 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionManagerImpl.java
>  3a16c77 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentHostEvent.java
>  78590fc 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentHostEventType.java
>  b43ac9c 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostServerActionEvent.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostUpgradeEvent.java
>  8b375fe 
>   
> ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionDBAccessorImpl.java
>  36acbc2 
>   
> ambari-server/src/test/java/org/apache/ambari/se

[jira] [Created] (AMBARI-8281) UI only loads content property from stack for *-env.xml, others are ignored

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-8281:


 Summary: UI only loads content property from stack for *-env.xml, 
others are ignored
 Key: AMBARI-8281
 URL: https://issues.apache.org/jira/browse/AMBARI-8281
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 2.0.0


Currently all properties except _content_ one from *-env.xml configurations 
files should be duplicated in _ambari-web/app/data/HDP2/site_properties.js_ .
Otherwise they are ignored on service deploy (not added to ambari configs).

More details:
It looks like UI has some property values for services hardcoded and hidden 
from user. These include _hbase.tmp.dir_ and bunch of others.
When user makes changes to configs these properties are added to corresponding 
configs and sent to server.
Issue is that UI probably filters them by property name only, so if other 
service has property with same name, this property will not be shown to user 
and, which is more important, will not be sent to server as it is wired to 
another service.

We are adding new service which contains embedded hbase, so we have config with 
all duplicated hbase properties, as result it is impossible to create correct 
configuration via UI.



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

[jira] [Commented] (AMBARI-8280) Create mock for Admin Web: Stack Versions: Version Detail page

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-8280:
--

got +1 from Andrii Tkach


> Create mock for Admin Web: Stack Versions: Version Detail page
> --
>
> Key: AMBARI-8280
> URL: https://issues.apache.org/jira/browse/AMBARI-8280
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8280.patch
>
>




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

[jira] [Updated] (AMBARI-8281) UI only loads content property from stack for *-env.xml, others are ignored

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-8281:
-
Attachment: AMBARI-8281.patch

> UI only loads content property from stack for *-env.xml, others are ignored
> ---
>
> Key: AMBARI-8281
> URL: https://issues.apache.org/jira/browse/AMBARI-8281
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8281.patch
>
>
> Currently all properties except _content_ one from *-env.xml configurations 
> files should be duplicated in _ambari-web/app/data/HDP2/site_properties.js_ .
> Otherwise they are ignored on service deploy (not added to ambari configs).
> More details:
> It looks like UI has some property values for services hardcoded and hidden 
> from user. These include _hbase.tmp.dir_ and bunch of others.
> When user makes changes to configs these properties are added to 
> corresponding configs and sent to server.
> Issue is that UI probably filters them by property name only, so if other 
> service has property with same name, this property will not be shown to user 
> and, which is more important, will not be sent to server as it is wired to 
> another service.
> We are adding new service which contains embedded hbase, so we have config 
> with all duplicated hbase properties, as result it is impossible to create 
> correct configuration via UI.



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

Review Request 27877: UI only loads content property from stack for *-env.xml, others are ignored

[Andriy Babiichuk]

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

Review request for Ambari and Aleksandr Kovalenko.


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


Repository: ambari


Description
---

Currently all properties except _content_ one from *-env.xml configurations 
files should be duplicated in _ambari-web/app/data/HDP2/site_properties.js_ .
Otherwise they are ignored on service deploy (not added to ambari configs).

More details:
It looks like UI has some property values for services hardcoded and hidden 
from user. These include _hbase.tmp.dir_ and bunch of others.
When user makes changes to configs these properties are added to corresponding 
configs and sent to server.
Issue is that UI probably filters them by property name only, so if other 
service has property with same name, this property will not be shown to user 
and, which is more important, will not be sent to server as it is wired to 
another service.

We are adding new service which contains embedded hbase, so we have config with 
all duplicated hbase properties, as result it is impossible to create correct 
configuration via UI.


Diffs
-

  ambari-web/app/data/BIGTOP/site_properties.js c2291b7 
  ambari-web/app/data/HDP2.2/site_properties.js 9c38cde 
  ambari-web/app/data/HDP2/site_properties.js 63ed001 
  ambari-web/app/data/site_properties.js 4151250 
  ambari-web/app/utils/config.js 470d42b 
  ambari-web/test/mock_data_setup/configs_mock_data.js 64cc619 
  ambari-web/test/utils/config_test.js 5dec0ae 

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


Testing
---

  5027 tests complete (6 seconds)
  60 tests pending


Thanks,

Andriy Babiichuk

Re: Review Request 27877: UI only loads content property from stack for *-env.xml, others are ignored

[Aleksandr Kovalenko]

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

Ship it!


Ship It!

- Aleksandr Kovalenko


On Лис. 11, 2014, 5:32 після полудня, Andriy Babiichuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27877/
> ---
> 
> (Updated Лис. 11, 2014, 5:32 після полудня)
> 
> 
> Review request for Ambari and Aleksandr Kovalenko.
> 
> 
> Bugs: AMBARI-8281
> https://issues.apache.org/jira/browse/AMBARI-8281
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Currently all properties except _content_ one from *-env.xml configurations 
> files should be duplicated in _ambari-web/app/data/HDP2/site_properties.js_ .
> Otherwise they are ignored on service deploy (not added to ambari configs).
> 
> More details:
> It looks like UI has some property values for services hardcoded and hidden 
> from user. These include _hbase.tmp.dir_ and bunch of others.
> When user makes changes to configs these properties are added to 
> corresponding configs and sent to server.
> Issue is that UI probably filters them by property name only, so if other 
> service has property with same name, this property will not be shown to user 
> and, which is more important, will not be sent to server as it is wired to 
> another service.
> 
> We are adding new service which contains embedded hbase, so we have config 
> with all duplicated hbase properties, as result it is impossible to create 
> correct configuration via UI.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/data/BIGTOP/site_properties.js c2291b7 
>   ambari-web/app/data/HDP2.2/site_properties.js 9c38cde 
>   ambari-web/app/data/HDP2/site_properties.js 63ed001 
>   ambari-web/app/data/site_properties.js 4151250 
>   ambari-web/app/utils/config.js 470d42b 
>   ambari-web/test/mock_data_setup/configs_mock_data.js 64cc619 
>   ambari-web/test/utils/config_test.js 5dec0ae 
> 
> Diff: https://reviews.apache.org/r/27877/diff/
> 
> 
> Testing
> ---
> 
>   5027 tests complete (6 seconds)
>   60 tests pending
> 
> 
> Thanks,
> 
> Andriy Babiichuk
> 
>

[jira] [Commented] (AMBARI-8281) UI only loads content property from stack for *-env.xml, others are ignored

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-8281:
--

https://reviews.apache.org/r/27877/

> UI only loads content property from stack for *-env.xml, others are ignored
> ---
>
> Key: AMBARI-8281
> URL: https://issues.apache.org/jira/browse/AMBARI-8281
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8281.patch
>
>
> Currently all properties except _content_ one from *-env.xml configurations 
> files should be duplicated in _ambari-web/app/data/HDP2/site_properties.js_ .
> Otherwise they are ignored on service deploy (not added to ambari configs).
> More details:
> It looks like UI has some property values for services hardcoded and hidden 
> from user. These include _hbase.tmp.dir_ and bunch of others.
> When user makes changes to configs these properties are added to 
> corresponding configs and sent to server.
> Issue is that UI probably filters them by property name only, so if other 
> service has property with same name, this property will not be shown to user 
> and, which is more important, will not be sent to server as it is wired to 
> another service.
> We are adding new service which contains embedded hbase, so we have config 
> with all duplicated hbase properties, as result it is impossible to create 
> correct configuration via UI.



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

Re: Review Request 27700: Allow for server-side commands

[Jonathan Hurley]

> On Nov. 10, 2014, 11:32 a.m., Robert Nettleton wrote:
> > ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java,
> >  line 654
> > 
> >
> > I'm a little worried by the presence of the sleep here.  
> > 
> > It might be worth considering making this a functional test instead?  
> > 
> > Again, just concerned about the unit tests having intermittent failures 
> > due to concurrency problems.
> 
> Robert Levas wrote:
> We really need to sleep here so that the scheduler and executer have time 
> to run - which are in different threads.  The idea is that a tasks a scheuled 
> and we are polling its status to see when it is completed.. then we make sure 
> its status is what was expected. I don't think there is another way around it.
> 
> John Speidel wrote:
> I agree with Bob on this and feel strongly that using sleep statements 
> like this result in non-deterministic tests.  
> I haven't really looked at the ActionScheduler to provide you a solution 
> but can give some genral comments on testing of this nature.
> - If you can run the test in a single thread, that is always best.  For 
> example, sometimes it is possible to call run directly.
> - If a separate thread must be used, it is best to have a deterministic 
> way to determine if a task has completed.  For example, if you have access to 
> the task perhaps it has state that can be queried.
> - If you must use another thread and have no way to determine with 
> certainty that a task has completed, use a "wait for" approach.  The idea is 
> that you have a loop that does an assertion every couple of ms.  You keep 
> looping until the assertion holds or until you "timeout" and fail the test.  
> The timeout should be rather long since it is only applicable in the case of 
> a test failure. For the successful scenario, the test will not block for long 
> sine we are checking the condition in small intervals.

Nate and I had a similar issue with testing alert events. Because of the 
asynchronous nature of the eventing system, we would have needed to insert 
Thread.sleep() in a bunch of tests. Instead, we injected a different event 
scheduler which was hard coded to be synchronous. Maybe a similar solution can 
be used here where you can inject a single-threaded version of the class that 
blocks until its thread completes.


- Jonathan


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


On Nov. 10, 2014, 9:05 a.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27700/
> ---
> 
> (Updated Nov. 10, 2014, 9:05 a.m.)
> 
> 
> Review request for Ambari, dilli dorai, Jonathan Hurley, John Speidel, Nate 
> Cole, Robert Nettleton, and Sid Wagle.
> 
> 
> Bugs: AMBARI-7985
> https://issues.apache.org/jira/browse/AMBARI-7985
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ambari currently handles client-/agent-side commands; however there is no 
> ability to handle server-side commands. Server-side commands should be 
> specified as a task in a stage and managed along with the stage.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessor.java
>  1f99b4a 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java
>  5e879cc 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionManager.java
>  e2fad5f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
>  81fee75 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/Stage.java 
> bbc5ac3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
>  52b0ba6 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostRoleCommandDAO.java
>  6920a9e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/AbstractServerAction.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerAction.java
>  be885b5 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionExecutor.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionManager.java
>  011cf06 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionManagerImpl.java
>  3a16c77 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentHostEvent.java
>  78590fc 
>   
> ambari-server/src/main/java/org/apache/am

[jira] [Commented] (AMBARI-8279) Slider View: "+ Create App" button effect is disabled, but is clickable

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8279:


SUCCESS: Integrated in Ambari-trunk-Commit #910 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/910/])
AMBARI-8279. Slider View: "+ Create App" button effect is disabled, but is 
clickable (alexantonenko) (hiveww: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6b98cfc084e9194ff4df578796953d1f8e93d642)
* contrib/views/slider/src/main/resources/ui/app/styles/app.less


> Slider View: "+ Create App" button effect is disabled, but is clickable
> ---
>
> Key: AMBARI-8279
> URL: https://issues.apache.org/jira/browse/AMBARI-8279
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.0.0
>
> Attachments: AMBARI-8279.patch, Screen Shot 2014-11-05 at 1.03.34 
> PM.png, Screen Shot 2014-11-05 at 1.03.42 PM.png, Screen Shot 2014-11-05 at 
> 1.03.49 PM.png, Screen Shot 2014-11-05 at 1.26.24 PM.png, good button.png
>
>
> see attached.
> On slider view apps table page, the "+ create app" button is disabled.  
> But when clicking on this button, a wizard show up.
> The user experience is bad.
> The same issue for "Actions" button on a slider app view. 
> (A button which is clickable should be like good button.png)



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

[jira] [Commented] (AMBARI-8281) UI only loads content property from stack for *-env.xml, others are ignored

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-8281:
--

got +1 form Aleksandr Kovalenko


> UI only loads content property from stack for *-env.xml, others are ignored
> ---
>
> Key: AMBARI-8281
> URL: https://issues.apache.org/jira/browse/AMBARI-8281
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8281.patch
>
>
> Currently all properties except _content_ one from *-env.xml configurations 
> files should be duplicated in _ambari-web/app/data/HDP2/site_properties.js_ .
> Otherwise they are ignored on service deploy (not added to ambari configs).
> More details:
> It looks like UI has some property values for services hardcoded and hidden 
> from user. These include _hbase.tmp.dir_ and bunch of others.
> When user makes changes to configs these properties are added to 
> corresponding configs and sent to server.
> Issue is that UI probably filters them by property name only, so if other 
> service has property with same name, this property will not be shown to user 
> and, which is more important, will not be sent to server as it is wired to 
> another service.
> We are adding new service which contains embedded hbase, so we have config 
> with all duplicated hbase properties, as result it is impossible to create 
> correct configuration via UI.



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

[jira] [Created] (AMBARI-8282) Set property for windows stack

[Eugene Chekanskiy (JIRA)]

Eugene Chekanskiy created AMBARI-8282:
-

 Summary: Set  property for windows stack
 Key: AMBARI-8282
 URL: https://issues.apache.org/jira/browse/AMBARI-8282
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: branch-windows-dev
Reporter: Eugene Chekanskiy
Assignee: Eugene Chekanskiy
 Fix For: branch-windows-dev






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

[jira] [Created] (AMBARI-8283) Missing translations for validations issues

[Jaimin D Jetly (JIRA)]

Jaimin D Jetly created AMBARI-8283:
--

 Summary: Missing translations for validations issues
 Key: AMBARI-8283
 URL: https://issues.apache.org/jira/browse/AMBARI-8283
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Jaimin D Jetly
Assignee: Jaimin D Jetly
 Fix For: 2.0.0






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

[jira] [Created] (AMBARI-8284) %HOSTGROUP::name% token substition not occuring for hive-site property "javax.jdo.option.ConnectionUR"

[Michael Harp (JIRA)]

Michael Harp created AMBARI-8284:


 Summary: %HOSTGROUP::name% token substition not occuring for 
hive-site property "javax.jdo.option.ConnectionUR"
 Key: AMBARI-8284
 URL: https://issues.apache.org/jira/browse/AMBARI-8284
 Project: Ambari
  Issue Type: Bug
  Components: blueprints
Affects Versions: 1.7.0
Reporter: Michael Harp


To reproduce, include "javax.jdo.option.ConnectionURL": 
"jdbc:postgresql:%HOSTGROUP::host_group_master1%:5432/hive” in blueprint 
configuration, example here https://gist.github.com/miharp/d3809efaad78ea876837




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

[jira] [Commented] (AMBARI-8279) Slider View: "+ Create App" button effect is disabled, but is clickable

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8279:


FAILURE: Integrated in Ambari-trunk-Commit-docker #201 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/201/])
AMBARI-8279. Slider View: "+ Create App" button effect is disabled, but is 
clickable (alexantonenko) (hiveww: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6b98cfc084e9194ff4df578796953d1f8e93d642)
* contrib/views/slider/src/main/resources/ui/app/styles/app.less


> Slider View: "+ Create App" button effect is disabled, but is clickable
> ---
>
> Key: AMBARI-8279
> URL: https://issues.apache.org/jira/browse/AMBARI-8279
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 1.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.0.0
>
> Attachments: AMBARI-8279.patch, Screen Shot 2014-11-05 at 1.03.34 
> PM.png, Screen Shot 2014-11-05 at 1.03.42 PM.png, Screen Shot 2014-11-05 at 
> 1.03.49 PM.png, Screen Shot 2014-11-05 at 1.26.24 PM.png, good button.png
>
>
> see attached.
> On slider view apps table page, the "+ create app" button is disabled.  
> But when clicking on this button, a wizard show up.
> The user experience is bad.
> The same issue for "Actions" button on a slider app view. 
> (A button which is clickable should be like good button.png)



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

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8276:
---

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

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

{color:green}+1 tests included{color}.  The patch appears to include 54 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

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

This message is automatically generated.

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



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

[jira] [Updated] (AMBARI-8284) %HOSTGROUP::name% token substition not occuring for hive-site property "javax.jdo.option.ConnectionURL"

[Michael Harp (JIRA)]

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

Michael Harp updated AMBARI-8284:
-
Summary: %HOSTGROUP::name% token substition not occuring for hive-site 
property "javax.jdo.option.ConnectionURL"  (was: %HOSTGROUP::name% token 
substition not occuring for hive-site property "javax.jdo.option.ConnectionUR")

> %HOSTGROUP::name% token substition not occuring for hive-site property 
> "javax.jdo.option.ConnectionURL"
> ---
>
> Key: AMBARI-8284
> URL: https://issues.apache.org/jira/browse/AMBARI-8284
> Project: Ambari
>  Issue Type: Bug
>  Components: blueprints
>Affects Versions: 1.7.0
>Reporter: Michael Harp
>
> To reproduce, include "javax.jdo.option.ConnectionURL": 
> "jdbc:postgresql:%HOSTGROUP::host_group_master1%:5432/hive” in blueprint 
> configuration, example here 
> https://gist.github.com/miharp/d3809efaad78ea876837



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

[jira] [Created] (AMBARI-8285) %HOSTGROUP::name% token substition not occuring for oozie-site property "oozie.service.JPAService.jdbc.url"

[Michael Harp (JIRA)]

Michael Harp created AMBARI-8285:


 Summary: %HOSTGROUP::name% token substition not occuring for 
oozie-site property "oozie.service.JPAService.jdbc.url"
 Key: AMBARI-8285
 URL: https://issues.apache.org/jira/browse/AMBARI-8285
 Project: Ambari
  Issue Type: Bug
  Components: blueprints
Affects Versions: 1.7.0
Reporter: Michael Harp


To reproduce, include "oozie.service.JPAService.jdbc.url": 
"%HOSTGROUP::host_group_master1%:5432/oozie" in blueprint configuration, 
example here https://gist.github.com/miharp/d3809efaad78ea876837



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

Re: Review Request 27876: Create mock for Admin Web: Stack Versions: Version Detail page

[Andrii Tkach]

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

Ship it!


Ship It!

- Andrii Tkach


On Ноя. 11, 2014, 5:20 п.п., Andriy Babiichuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27876/
> ---
> 
> (Updated Ноя. 11, 2014, 5:20 п.п.)
> 
> 
> Review request for Ambari and Andrii Tkach.
> 
> 
> Bugs: AMBARI-8280
> https://issues.apache.org/jira/browse/AMBARI-8280
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Create mock for Admin Web: Stack Versions: Version Detail page
> 
> 
> Diffs
> -
> 
>   ambari-web/app/assets/data/stack_versions/stack_version_all.json c2651ea 
>   ambari-web/app/assets/test/tests.js 2752a0c 
>   ambari-web/app/controllers.js 3e4e0da 
>   
> ambari-web/app/controllers/main/admin/stack_upgrade/stack_version_details_controller.js
>  PRE-CREATION 
>   ambari-web/app/mappers/stack_version_mapper.js 856bccb 
>   ambari-web/app/messages.js f01f9c2 
>   ambari-web/app/models/stack_version/version.js b7ede22 
>   ambari-web/app/routes/main.js 76c46a5 
>   ambari-web/app/styles/application.less df43c1a 
>   
> ambari-web/app/templates/main/admin/stack_versions/stack_version_details.hbs 
> PRE-CREATION 
>   ambari-web/app/templates/main/admin/stack_versions/stack_versions.hbs 
> 15eba7b 
>   ambari-web/app/views.js 842596b 
>   ambari-web/app/views/main/admin.js 7c00ed8 
>   
> ambari-web/app/views/main/admin/stack_versions/stack_version_details_view.js 
> PRE-CREATION 
>   ambari-web/app/views/main/admin/stack_versions/stack_version_view.js 
> b0793b0 
>   ambari-web/app/views/main/menu.js 5ab6375 
>   
> ambari-web/test/views/main/admin/stack_version/stack_version_details_test.js 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/27876/diff/
> 
> 
> Testing
> ---
> 
>   5026 tests complete (6 seconds)
>   60 tests pending
> 
> 
> Thanks,
> 
> Andriy Babiichuk
> 
>

Re: Review Request 27540: AMBARI-8120 - Configs tab doesn't appear for all services

[Florian Barca]

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

Ship it!


Ship It!

- Florian Barca


On Nov. 4, 2014, 7:36 p.m., Artem Baranchuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27540/
> ---
> 
> (Updated Nov. 4, 2014, 7:36 p.m.)
> 
> 
> Review request for Ambari, Aleksandr Kovalenko, Florian Barca, Jayush Luniya, 
> and Mahadev Konar.
> 
> 
> Bugs: AMBARI-8120
> https://issues.apache.org/jira/browse/AMBARI-8120
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> AMBARI-8120 - Configs tab doesn't appear for all services
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/YARN/configuration-mapred/mapred-site.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/YARN/configuration/mapred-site.xml
>  8e909bc 
>   
> ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/YARN/metainfo.xml 
> 31eb346 
>   ambari-web/app/assets/data/configuration/cluster_env_site.json PRE-CREATION 
>   ambari-web/app/controllers/main/service/info/configs.js c9ec483 
>   ambari-web/app/utils/ajax/ajax.js f264dc4 
> 
> Diff: https://reviews.apache.org/r/27540/diff/
> 
> 
> Testing
> ---
> 
> [INFO] Ambari Server . SUCCESS 
> [28:51.093s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Artem Baranchuk
> 
>

[jira] [Updated] (AMBARI-8269) Merge branch-windows-dev changes to trunk

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-8269:
--
Attachment: AMBARI-8269.1.patch

Uploading patch with latest in trunk.

> Merge branch-windows-dev changes to trunk
> -
>
> Key: AMBARI-8269
> URL: https://issues.apache.org/jira/browse/AMBARI-8269
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-agent, ambari-server, ambari-web, contrib
>Affects Versions: 2.0.0
> Environment: Windows/Linux
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.0.0
>
> Attachments: AMBARI-8269.1.patch, AMBARI-8269.patch
>
>




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

Re: Review Request 27864: Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*

[Alejandro Fernandez]

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

Ship it!


Ship It!

- Alejandro Fernandez


On Nov. 11, 2014, 12:46 p.m., Andrii Tkach wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27864/
> ---
> 
> (Updated Nov. 11, 2014, 12:46 p.m.)
> 
> 
> Review request for Ambari, Oleg Nechiporenko and Yusaku Sako.
> 
> 
> Bugs: AMBARI-8274
> https://issues.apache.org/jira/browse/AMBARI-8274
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Enable Kerberos Wizard: Downloaded CSV file is empty for HDP 1.3.*
> 
> 
> Diffs
> -
> 
>   ambari-web/app/data/secure_mapping.js cfca947 
>   ambari-web/app/data/secure_properties.js 5d01943 
> 
> Diff: https://reviews.apache.org/r/27864/diff/
> 
> 
> Testing
> ---
> 
> Tested manually
> 
> 
> Thanks,
> 
> Andrii Tkach
> 
>

[jira] [Commented] (AMBARI-8280) Create mock for Admin Web: Stack Versions: Version Detail page

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8280:


SUCCESS: Integrated in Ambari-trunk-Commit #911 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/911/])
AMBARI-8280 Create mock for Admin Web: Stack Versions: Version Detail page. 
(ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fc0cda8793c740838074500e6941e6ee9c9715bd)
* ambari-web/app/mappers/stack_version_mapper.js
* ambari-web/app/controllers.js
* ambari-web/app/templates/main/admin/stack_versions/stack_version_details.hbs
* ambari-web/app/styles/application.less
* ambari-web/app/views.js
* ambari-web/app/views/main/admin/stack_versions/stack_version_view.js
* ambari-web/app/routes/main.js
* ambari-web/app/templates/main/admin/stack_versions/stack_versions.hbs
* ambari-web/app/views/main/admin/stack_versions/stack_version_details_view.js
* 
ambari-web/app/controllers/main/admin/stack_upgrade/stack_version_details_controller.js
* ambari-web/app/assets/data/stack_versions/stack_version_all.json
* ambari-web/test/views/main/admin/stack_version/stack_version_details_test.js
* ambari-web/app/views/main/menu.js
* ambari-web/app/assets/test/tests.js
* ambari-web/app/models/stack_version/version.js
* ambari-web/app/messages.js
* ambari-web/app/views/main/admin.js


> Create mock for Admin Web: Stack Versions: Version Detail page
> --
>
> Key: AMBARI-8280
> URL: https://issues.apache.org/jira/browse/AMBARI-8280
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8280.patch
>
>




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

Re: Review Request 27870: Alerts: Remove Nagios Service From The Stack

[Alejandro Fernandez]

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

Ship it!


Ship It!

- Alejandro Fernandez


On Nov. 11, 2014, 4:08 p.m., Jonathan Hurley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27870/
> ---
> 
> (Updated Nov. 11, 2014, 4:08 p.m.)
> 
> 
> Review request for Ambari, Dmytro Sen, Nate Cole, Srimanth Gunturi, Tom 
> Beerbower, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-8276
> https://issues.apache.org/jira/browse/AMBARI-8276
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> With the new alerting framework in place, the Nagios stack files can start to 
> be removed. This involves many different steps between the server, the web 
> client, and the agent.
> 
> In this Jira, we will track the removal of the stack resources. This means:
> 
> - Remove files in src/main/resources/stacks/*/services/NAGIOS
> - Remove files in test/main/resources/stacks/*/services/NAGIOS
> - Associated tests that depend on Nagios must be either removed if irrelevent 
> or rewritten
> 
> This effort should leave Ambari in a state where the web client and 
> blueprints can still successfully install a non-Nagios cluster. Once 
> installed, the cluster will operate normally with the exception that alerts 
> will not be surfaced by the web client until they have switched over to the 
> new alert framework.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/custom_action_definitions/system_action_definitions.xml
>  c65a496 
>   ambari-server/src/main/resources/custom_actions/nagios_update_ignore.py 
> b7026e2 
>   ambari-server/src/main/resources/custom_actions/validate_configs.py c245dbb 
>   ambari-server/src/main/resources/properties.json 36cff96 
>   ambari-server/src/main/resources/role_command_order.json c45ba07 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/blueprints/multinode-default.json
>  642fcfa 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/blueprints/singlenode-default.json
>  3c769dd 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/params.py
>  01789a7 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py
>  ac8f1c8 
>   ambari-server/src/main/resources/stacks/BIGTOP/0.8/role_command_order.json 
> 69fcdac 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/files/gmondLib.sh
>  e7ea83f 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
>  83b2ed9 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/configuration/nagios-env.xml
>  fad8374 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/metainfo.xml
>  bebc7d6 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_aggregate.php
>  792b25b 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_ambari_alerts.py
>  833a798 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_checkpoint_time.py
>  ab889d1 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu.php
>  0744e38 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu.pl
>  a5680f7 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu_ha.php
>  91a7c64 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_datanode_storage.php
>  dee22b4 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hdfs_blocks.php
>  3693aa0 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hdfs_capacity.php
>  af72723 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hive_metastore_status.sh
>  640c077 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hue_status.sh
>  076d9b3 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_mapred_local_dir_used.sh
>  3f9243a 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_name_dir_status.php
>  186166d 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_namenodes_ha.sh
>  83c1aca 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_nodemanager_health.sh
>  eedcd62 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_oozie_st

Re: Review Request 27870: Alerts: Remove Nagios Service From The Stack

[Nate Cole]

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

Ship it!


Ship It!

- Nate Cole


On Nov. 11, 2014, 11:08 a.m., Jonathan Hurley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27870/
> ---
> 
> (Updated Nov. 11, 2014, 11:08 a.m.)
> 
> 
> Review request for Ambari, Dmytro Sen, Nate Cole, Srimanth Gunturi, Tom 
> Beerbower, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-8276
> https://issues.apache.org/jira/browse/AMBARI-8276
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> With the new alerting framework in place, the Nagios stack files can start to 
> be removed. This involves many different steps between the server, the web 
> client, and the agent.
> 
> In this Jira, we will track the removal of the stack resources. This means:
> 
> - Remove files in src/main/resources/stacks/*/services/NAGIOS
> - Remove files in test/main/resources/stacks/*/services/NAGIOS
> - Associated tests that depend on Nagios must be either removed if irrelevent 
> or rewritten
> 
> This effort should leave Ambari in a state where the web client and 
> blueprints can still successfully install a non-Nagios cluster. Once 
> installed, the cluster will operate normally with the exception that alerts 
> will not be surfaced by the web client until they have switched over to the 
> new alert framework.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/custom_action_definitions/system_action_definitions.xml
>  c65a496 
>   ambari-server/src/main/resources/custom_actions/nagios_update_ignore.py 
> b7026e2 
>   ambari-server/src/main/resources/custom_actions/validate_configs.py c245dbb 
>   ambari-server/src/main/resources/properties.json 36cff96 
>   ambari-server/src/main/resources/role_command_order.json c45ba07 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/blueprints/multinode-default.json
>  642fcfa 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/blueprints/singlenode-default.json
>  3c769dd 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/params.py
>  01789a7 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py
>  ac8f1c8 
>   ambari-server/src/main/resources/stacks/BIGTOP/0.8/role_command_order.json 
> 69fcdac 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/files/gmondLib.sh
>  e7ea83f 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
>  83b2ed9 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/configuration/nagios-env.xml
>  fad8374 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/metainfo.xml
>  bebc7d6 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_aggregate.php
>  792b25b 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_ambari_alerts.py
>  833a798 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_checkpoint_time.py
>  ab889d1 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu.php
>  0744e38 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu.pl
>  a5680f7 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu_ha.php
>  91a7c64 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_datanode_storage.php
>  dee22b4 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hdfs_blocks.php
>  3693aa0 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hdfs_capacity.php
>  af72723 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hive_metastore_status.sh
>  640c077 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hue_status.sh
>  076d9b3 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_mapred_local_dir_used.sh
>  3f9243a 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_name_dir_status.php
>  186166d 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_namenodes_ha.sh
>  83c1aca 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_nodemanager_health.sh
>  eedcd62 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_oozie_status.sh

Re: Review Request 27870: Alerts: Remove Nagios Service From The Stack

[Tom Beerbower]

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

Ship it!


Ship It!

- Tom Beerbower


On Nov. 11, 2014, 4:08 p.m., Jonathan Hurley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27870/
> ---
> 
> (Updated Nov. 11, 2014, 4:08 p.m.)
> 
> 
> Review request for Ambari, Dmytro Sen, Nate Cole, Srimanth Gunturi, Tom 
> Beerbower, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-8276
> https://issues.apache.org/jira/browse/AMBARI-8276
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> With the new alerting framework in place, the Nagios stack files can start to 
> be removed. This involves many different steps between the server, the web 
> client, and the agent.
> 
> In this Jira, we will track the removal of the stack resources. This means:
> 
> - Remove files in src/main/resources/stacks/*/services/NAGIOS
> - Remove files in test/main/resources/stacks/*/services/NAGIOS
> - Associated tests that depend on Nagios must be either removed if irrelevent 
> or rewritten
> 
> This effort should leave Ambari in a state where the web client and 
> blueprints can still successfully install a non-Nagios cluster. Once 
> installed, the cluster will operate normally with the exception that alerts 
> will not be surfaced by the web client until they have switched over to the 
> new alert framework.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/custom_action_definitions/system_action_definitions.xml
>  c65a496 
>   ambari-server/src/main/resources/custom_actions/nagios_update_ignore.py 
> b7026e2 
>   ambari-server/src/main/resources/custom_actions/validate_configs.py c245dbb 
>   ambari-server/src/main/resources/properties.json 36cff96 
>   ambari-server/src/main/resources/role_command_order.json c45ba07 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/blueprints/multinode-default.json
>  642fcfa 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/blueprints/singlenode-default.json
>  3c769dd 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/params.py
>  01789a7 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py
>  ac8f1c8 
>   ambari-server/src/main/resources/stacks/BIGTOP/0.8/role_command_order.json 
> 69fcdac 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/GANGLIA/package/files/gmondLib.sh
>  e7ea83f 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
>  83b2ed9 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/configuration/nagios-env.xml
>  fad8374 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/metainfo.xml
>  bebc7d6 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_aggregate.php
>  792b25b 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_ambari_alerts.py
>  833a798 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_checkpoint_time.py
>  ab889d1 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu.php
>  0744e38 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu.pl
>  a5680f7 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_cpu_ha.php
>  91a7c64 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_datanode_storage.php
>  dee22b4 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hdfs_blocks.php
>  3693aa0 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hdfs_capacity.php
>  af72723 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hive_metastore_status.sh
>  640c077 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_hue_status.sh
>  076d9b3 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_mapred_local_dir_used.sh
>  3f9243a 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_name_dir_status.php
>  186166d 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_namenodes_ha.sh
>  83c1aca 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_nodemanager_health.sh
>  eedcd62 
>   
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/NAGIOS/package/files/check_oozie_status.s

[jira] [Commented] (AMBARI-8280) Create mock for Admin Web: Stack Versions: Version Detail page

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8280:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #202 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/202/])
AMBARI-8280 Create mock for Admin Web: Stack Versions: Version Detail page. 
(ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fc0cda8793c740838074500e6941e6ee9c9715bd)
* ambari-web/app/views/main/admin.js
* ambari-web/app/models/stack_version/version.js
* ambari-web/app/messages.js
* ambari-web/app/assets/data/stack_versions/stack_version_all.json
* ambari-web/app/mappers/stack_version_mapper.js
* ambari-web/app/assets/test/tests.js
* ambari-web/app/controllers.js
* ambari-web/app/views/main/admin/stack_versions/stack_version_details_view.js
* ambari-web/app/views/main/menu.js
* ambari-web/app/views/main/admin/stack_versions/stack_version_view.js
* ambari-web/app/views.js
* ambari-web/app/templates/main/admin/stack_versions/stack_versions.hbs
* ambari-web/app/styles/application.less
* ambari-web/app/routes/main.js
* 
ambari-web/app/controllers/main/admin/stack_upgrade/stack_version_details_controller.js
* ambari-web/app/templates/main/admin/stack_versions/stack_version_details.hbs
* ambari-web/test/views/main/admin/stack_version/stack_version_details_test.js


> Create mock for Admin Web: Stack Versions: Version Detail page
> --
>
> Key: AMBARI-8280
> URL: https://issues.apache.org/jira/browse/AMBARI-8280
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8280.patch
>
>




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

[jira] [Commented] (AMBARI-8247) Provide a way to get service-specific Kerberos descriptor via REST API

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8247:
---

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

This message is automatically generated.

> Provide a way to get service-specific Kerberos descriptor via REST API
> --
>
> Key: AMBARI-8247
> URL: https://issues.apache.org/jira/browse/AMBARI-8247
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: api, service, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8247_01.patch, AMBARI-8247_02.patch
>
>
> Provide a way for a caller via the REST API to get information about a 
> service's Kerberos descriptor.  This information should probably be attached 
> to a service resource response.



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

[jira] [Created] (AMBARI-8286) Alert UI: Create mappers for Alert-Instances

[Oleg Nechiporenko (JIRA)]

Oleg Nechiporenko created AMBARI-8286:
-

 Summary: Alert UI: Create mappers for Alert-Instances
 Key: AMBARI-8286
 URL: https://issues.apache.org/jira/browse/AMBARI-8286
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 1.7.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
 Fix For: 1.7.0


Alert UI needs to map Alert-Instances data to Alert-Instances model 



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

Re: Review Request 27854: Create DAO and Unit Tests for ClusterVersion

[Nate Cole]

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



ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterVersionDAO.java


use DaoUtils



ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterVersionDAO.java


formatting



ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterVersionDAO.java


Use DaoUtils


- Nate Cole


On Nov. 10, 2014, 10:19 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27854/
> ---
> 
> (Updated Nov. 10, 2014, 10:19 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Nate Cole, and Yurii Shylov.
> 
> 
> Bugs: AMBARI-8270
> https://issues.apache.org/jira/browse/AMBARI-8270
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Create DAO and Unit Tests for ClusterVersionEntity that is needed for Rolling 
> Upgrades - Bootstrap
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterVersionDAO.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterVersionEntity.java
>  9daa70e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostVersionEntity.java
>  f0a0695 
>   
> ambari-server/src/test/java/org/apache/ambari/server/orm/dao/ClusterVersionDAOTest.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/27854/diff/
> 
> 
> Testing
> ---
> 
> Ran unit tests.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>