[jira] [Commented] (AMBARI-8621) Kerberos Wizard: Implement and Integrate "Configure Identities" page.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8621:


FAILURE: Integrated in Ambari-trunk-Commit-docker #433 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/433/])
AMBARI-8621. Kerberos Wizard: Implement and Integrate "Configure Identities" 
page. (jaimin: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a665a3cc13abba23224999a18e4eae1f1f8bc754)
* ambari-web/app/models/stack_service.js
* ambari-web/test/mock_data_setup/stack_descriptors.js
* ambari-web/app/controllers/main/admin/kerberos/step4_controller.js
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/mixins/wizard/addSecurityConfigs.js
* ambari-web/app/routes/add_kerberos_routes.js
* ambari-web/app/assets/data/wizard/kerberos/stack_descriptors.json
* ambari-web/app/assets/test/tests.js
* ambari-web/test/mixins/wizard/addSeccurityConfigs_test.js
* ambari-web/app/templates/main/admin/kerberos/step4.hbs


> Kerberos Wizard: Implement and Integrate "Configure Identities" page.
> -
>
> Key: AMBARI-8621
> URL: https://issues.apache.org/jira/browse/AMBARI-8621
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.0.0
>
> Attachments: AMBARI-8621.patch, Screen Shot 2014-12-09 at 4.46.07 
> PM.png
>
>




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

[jira] [Commented] (AMBARI-8621) Kerberos Wizard: Implement and Integrate "Configure Identities" page.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8621:


FAILURE: Integrated in Ambari-trunk-Commit #1156 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1156/])
AMBARI-8621. Kerberos Wizard: Implement and Integrate "Configure Identities" 
page. (jaimin: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a665a3cc13abba23224999a18e4eae1f1f8bc754)
* ambari-web/test/mixins/wizard/addSeccurityConfigs_test.js
* ambari-web/app/templates/main/admin/kerberos/step4.hbs
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/test/mock_data_setup/stack_descriptors.js
* ambari-web/app/models/stack_service.js
* ambari-web/app/mixins/wizard/addSecurityConfigs.js
* ambari-web/app/controllers/main/admin/kerberos/step4_controller.js
* ambari-web/app/assets/data/wizard/kerberos/stack_descriptors.json
* ambari-web/app/routes/add_kerberos_routes.js
* ambari-web/app/assets/test/tests.js


> Kerberos Wizard: Implement and Integrate "Configure Identities" page.
> -
>
> Key: AMBARI-8621
> URL: https://issues.apache.org/jira/browse/AMBARI-8621
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.0.0
>
> Attachments: AMBARI-8621.patch, Screen Shot 2014-12-09 at 4.46.07 
> PM.png
>
>




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

Re: Review Request 28519: Components should indicate Security State (via ambari-agent)

[Jayush Luniya]

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



ambari-agent/src/main/python/ambari_agent/ActionQueue.py


Check if key securityState exists


- Jayush Luniya


On Dec. 9, 2014, 3:55 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28519/
> ---
> 
> (Updated Dec. 9, 2014, 3:55 p.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, Jonathan Hurley, Jayush Luniya, Nate 
> Cole, Robert Nettleton, and Tom Beerbower.
> 
> 
> Bugs: AMBARI-8343
> https://issues.apache.org/jira/browse/AMBARI-8343
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In order to properly handle the automated installation or removal of a 
> security infrastructure (like Kerberos) in the cluster, Ambari needs to know 
> whether each component on the hosts of the cluster is properly _secured_ or 
> not.  This information may be compared with data on the Ambari server to help 
> determine what steps should be taken to ensure the cluster is in the correct 
> _secured_ state.
> 
> To do this, the current and desired component security state is maintained in 
> the Ambari database.  The Ambari server will update the desired state details 
> according to whether the cluster is to be secured or not and whether the 
> relevant service has enough metadata to be secured.  If the desired and 
> actual security state details do not match, the Ambari server will take the 
> necessary steps to work towards synchronization. 
> 
> In order for a component to indicate its security status, a new property 
> needs to be returned in the `STATUS_COMMAND` response message (from the 
> Ambari agent).  This property should be named ‘securityState’ and should have 
> one of the following values:
> 
> * `UNKNOWN` - Indicates that it is not known whether the service or component 
> is secured or not
> * `UNSECURED` - Indicates service or component is not or should not be secured
> * `SECURED_KERBEROS` - Indicates component is or should be secured using 
> Kerberos
> * `ERROR` - Indicates the component is not secured due to an error condition
> 
> To properly set this state value, a call needs to be executed per component 
> querying for its specific state.  Due to the differences on how each 
> component is secured and how it may be determined if security is setup what 
> type is configured, and working is it properly, it is necessary for each 
> component to have its own logic for determining this state. Therefore the 
> ambari-agent process will need to call into the component’s configured 
> (lifecycle) script and wait for its response - not unlike how it determines 
> whether the component is up and running.
> 
> After the infrastructure is in place, each service definition needs to be 
> updated to implement the new security status check function.  The function 
> should perform the following steps:
> 
> * Determine if security is enabled or disabled
> ** If disabled, return "UNSECURED"
> ** If enabled, determine what type of security is enabled
> *** If Kerberos is configured
>  Perform tests (kinit?, ping KDC?) to determine if the configuration 
> appears to be working
> * If working, return “SECURED_KERBEROS”
> * If not working, return “ERROR”
> *** Else, return "UNKNOWN"
> 
> If no function is available, the Ambari agent should return “UNKNOWN”.
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/main/python/ambari_agent/ActionQueue.py 4ecb822 
>   ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py 
> 08dddae 
>   ambari-agent/src/test/python/ambari_agent/TestActionQueue.py 034dba3 
>   ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py 
> 24ee259 
> 
> Diff: https://reviews.apache.org/r/28519/diff/
> 
> 
> Testing
> ---
> 
> Updated the following unit tests:
> * ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py
> * ambari-agent/src/test/python/ambari_agent/TestActionQueue.py
> 
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 03:06 min
> [INFO] Finished at: 2014-11-27T15:35:18+00:00
> [INFO] Final Memory: 80M/411M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

[jira] [Updated] (AMBARI-8627) Allow for service-level Kerberos descriptor to contain multiple services

[Robert Levas (JIRA)]

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

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

Trying to initiate a new QA test run which failed due to issues external to my 
patch.

> Allow for service-level Kerberos descriptor to contain multiple services
> 
>
> Key: AMBARI-8627
> URL: https://issues.apache.org/jira/browse/AMBARI-8627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, kerberos_descriptor, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8627_01.patch, AMBARI-8627_01.patch
>
>
> Current Kerberos descriptor handlers assume only a single service may be 
> identified in a service-level Kerberos descriptor file.  However services 
> like YARN include the MAPREDUCE2 service, thus multiple services need to be 
> acknowledged.



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

[jira] [Created] (AMBARI-8629) Nagios web: Error: Could not read object configuration data!

[Victor (JIRA)]

Victor created AMBARI-8629:
--

 Summary: Nagios web: Error: Could not read object configuration 
data!
 Key: AMBARI-8629
 URL: https://issues.apache.org/jira/browse/AMBARI-8629
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent, ambari-server
Affects Versions: 1.6.1
Reporter: Victor
Priority: Minor
 Attachments: 800px-Nagios-error.png

Nagios web could not shown data in a clean install:

Whoops!

Error: Could not read object configuration data!





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

[jira] [Updated] (AMBARI-8629) Nagios web: Error: Could not read object configuration data!

[Victor (JIRA)]

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

Victor updated AMBARI-8629:
---
Attachment: 800px-Nagios-error.png

> Nagios web: Error: Could not read object configuration data!
> 
>
> Key: AMBARI-8629
> URL: https://issues.apache.org/jira/browse/AMBARI-8629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 1.6.1
>Reporter: Victor
>Priority: Minor
> Attachments: 800px-Nagios-error.png
>
>
> Nagios web could not shown data in a clean install:
> Whoops!
> Error: Could not read object configuration data!



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

[jira] [Updated] (AMBARI-8629) Nagios web: Error: Could not read object configuration data!

[Victor (JIRA)]

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

Victor updated AMBARI-8629:
---
Description: 
Nagios web could not shown data in a clean install:

Whoops!

Error: Could not read object configuration data!


This error appear in any menu section (Map, Hosts, Services.. ) except the home 
page.

  was:
Nagios web could not shown data in a clean install:

Whoops!

Error: Could not read object configuration data!




> Nagios web: Error: Could not read object configuration data!
> 
>
> Key: AMBARI-8629
> URL: https://issues.apache.org/jira/browse/AMBARI-8629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 1.6.1
>Reporter: Victor
>Priority: Minor
> Attachments: 800px-Nagios-error.png
>
>
> Nagios web could not shown data in a clean install:
> Whoops!
> Error: Could not read object configuration data!
> This error appear in any menu section (Map, Hosts, Services.. ) except the 
> home page.



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

[jira] [Updated] (AMBARI-8343) Components should indicate Security State (via ambari-agent)

[Robert Levas (JIRA)]

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

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

Trying to initiate a new QA test run which failed due to issues external to my 
patch.

> Components should indicate Security State (via ambari-agent)
> 
>
> Key: AMBARI-8343
> URL: https://issues.apache.org/jira/browse/AMBARI-8343
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: kerberos, states
> Fix For: 2.0.0
>
> Attachments: AMBARI-8343_01.patch, AMBARI-8343_02.patch, 
> AMBARI-8343_03.patch, AMBARI-8343_03.patch, AMBARI-8343_03.patch
>
>
> In order to properly handle the automated installation or removal of a 
> security infrastructure (like Kerberos) in the cluster, Ambari needs to know 
> whether each component on the hosts of the cluster is properly _secured_ or 
> not.  This information may be compared with data on the Ambari server to help 
> determine what steps should be taken to ensure the cluster is in the correct 
> _secured_ state.
> To do this, the current and desired component security state is maintained in 
> the Ambari database.  The Ambari server will update the desired state details 
> according to whether the cluster is to be secured or not and whether the 
> relevant service has enough metadata to be secured.  If the desired and 
> actual security state details do not match, the Ambari server will take the 
> necessary steps to work towards synchronization. 
> In order for a component to indicate its security status, a new property 
> needs to be returned in the {{STATUS_COMMAND}} response message (from the 
> Ambari agent).  This property should be named ‘securityState’ and should have 
> one of the following values:
> * {{UNKNOWN}} - Indicates that it is not known whether the service or 
> component is secured or not
> * {{UNSECURED}} - Indicates service or component is not or should not be 
> secured
> * {{SECURED_KERBEROS}} - Indicates component is or should be secured using 
> Kerberos
> * {{ERROR}} - Indicates the component is not secured due to an error condition
> To properly set this state value, a call needs to be executed per component 
> querying for its specific state.  Due to the differences on how each 
> component is secured and how it may be determined if security is setup what 
> type is configured, and working is it properly, it is necessary for each 
> component to have its own logic for determining this state. Therefore the 
> ambari-agent process will need to call into the component’s configured 
> (lifecycle) script and wait for its response - not unlike how it determines 
> whether the component is up and running.
> After the infrastructure is in place, each service definition needs to be 
> updated to implement the new security status check function.  The function 
> should perform the following steps:
> * Determine if security is enabled or disabled
> ** If disabled, return "UNSECURED"
> ** If enabled, determine what type of security is enabled
> *** If Kerberos is configured
>  Perform tests (kinit?, ping KDC?) to determine if the configuration 
> appears to be working
> * If working, return “SECURED_KERBEROS”
> * If not working, return “ERROR”
> *** Else, return "UNKNOWN"
> If no function is available, the Ambari agent should return “UNKNOWN”.



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

[jira] [Commented] (AMBARI-8629) Nagios web: Error: Could not read object configuration data!

[Victor (JIRA)]

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

Victor commented on AMBARI-8629:


The real problem is in the NAGIOS config and CGI scripts, the parameter 
“retry_check_interval” must be an integer for CGI to work, but in many lines is 
0.5 or 0.25 by default.

Ambari in HDP2.1 use a template for this configuration located in:

/var/lib/ambari-server/resources/stacks/HDP/2.0.6/services/NAGIOS/package/templates

You need to edit hadoop-services.cfg.j2 and replace every occurrence of 
“retry_check_interval 0.25″ or “retry_check_interval 0.5″ with 
“retry_check_interval 1″. 

I attached a patch for this.

Restart NAGIOS through Ambari GUI.


> Nagios web: Error: Could not read object configuration data!
> 
>
> Key: AMBARI-8629
> URL: https://issues.apache.org/jira/browse/AMBARI-8629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 1.6.1
>Reporter: Victor
>Priority: Minor
> Attachments: 800px-Nagios-error.png, AMBARI-8629.patch
>
>
> Nagios web could not shown data in a clean install:
> Whoops!
> Error: Could not read object configuration data!
> This error appear in any menu section (Map, Hosts, Services.. ) except the 
> home page.



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

[jira] [Updated] (AMBARI-8629) Nagios web: Error: Could not read object configuration data!

[Victor (JIRA)]

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

Victor updated AMBARI-8629:
---
Attachment: AMBARI-8629.patch

> Nagios web: Error: Could not read object configuration data!
> 
>
> Key: AMBARI-8629
> URL: https://issues.apache.org/jira/browse/AMBARI-8629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 1.6.1
>Reporter: Victor
>Priority: Minor
> Attachments: 800px-Nagios-error.png, AMBARI-8629.patch
>
>
> Nagios web could not shown data in a clean install:
> Whoops!
> Error: Could not read object configuration data!
> This error appear in any menu section (Map, Hosts, Services.. ) except the 
> home page.



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

[jira] [Commented] (AMBARI-8343) Components should indicate Security State (via ambari-agent)

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8343:
---

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12686251/AMBARI-8343_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 2 new 
or modified test files.

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

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

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

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

This message is automatically generated.

> Components should indicate Security State (via ambari-agent)
> 
>
> Key: AMBARI-8343
> URL: https://issues.apache.org/jira/browse/AMBARI-8343
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: kerberos, states
> Fix For: 2.0.0
>
> Attachments: AMBARI-8343_01.patch, AMBARI-8343_02.patch, 
> AMBARI-8343_03.patch, AMBARI-8343_03.patch, AMBARI-8343_03.patch
>
>
> In order to properly handle the automated installation or removal of a 
> security infrastructure (like Kerberos) in the cluster, Ambari needs to know 
> whether each component on the hosts of the cluster is properly _secured_ or 
> not.  This information may be compared with data on the Ambari server to help 
> determine what steps should be taken to ensure the cluster is in the correct 
> _secured_ state.
> To do this, the current and desired component security state is maintained in 
> the Ambari database.  The Ambari server will update the desired state details 
> according to whether the cluster is to be secured or not and whether the 
> relevant service has enough metadata to be secured.  If the desired and 
> actual security state details do not match, the Ambari server will take the 
> necessary steps to work towards synchronization. 
> In order for a component to indicate its security status, a new property 
> needs to be returned in the {{STATUS_COMMAND}} response message (from the 
> Ambari agent).  This property should be named ‘securityState’ and should have 
> one of the following values:
> * {{UNKNOWN}} - Indicates that it is not known whether the service or 
> component is secured or not
> * {{UNSECURED}} - Indicates service or component is not or should not be 
> secured
> * {{SECURED_KERBEROS}} - Indicates component is or should be secured using 
> Kerberos
> * {{ERROR}} - Indicates the component is not secured due to an error condition
> To properly set this state value, a call needs to be executed per component 
> querying for its specific state.  Due to the differences on how each 
> component is secured and how it may be determined if security is setup what 
> type is configured, and working is it properly, it is necessary for each 
> component to have its own logic for determining this state. Therefore the 
> ambari-agent process will need to call into the component’s configured 
> (lifecycle) script and wait for its response - not unlike how it determines 
> whether the component is up and running.
> After the infrastructure is in place, each service definition needs to be 
> updated to implement the new security status check function.  The function 
> should perform the following steps:
> * Determine if security is enabled or disabled
> ** If disabled, return "UNSECURED"
> ** If enabled, determine what type of security is enabled
> *** If Kerberos is configured
>  Perform tests (kinit?, ping KDC?) to determine if the configuration 
> appears to be working
> * If working, return “SECURED_KERBEROS”
> * If not working, return “ERROR”
> *** Else, return "UNKNOWN"
> If no function is available, the Ambari agent should return “UNKNOWN”.



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

[jira] [Commented] (AMBARI-8629) Nagios web: Error: Could not read object configuration data!

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8629:
---

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

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

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

This message is automatically generated.

> Nagios web: Error: Could not read object configuration data!
> 
>
> Key: AMBARI-8629
> URL: https://issues.apache.org/jira/browse/AMBARI-8629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 1.6.1
>Reporter: Victor
>Priority: Minor
> Attachments: 800px-Nagios-error.png, AMBARI-8629.patch
>
>
> Nagios web could not shown data in a clean install:
> Whoops!
> Error: Could not read object configuration data!
> This error appear in any menu section (Map, Hosts, Services.. ) except the 
> home page.



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

Re: Review Request 28519: Components should indicate Security State (via ambari-agent)

[Robert Levas]

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

(Updated Dec. 10, 2014, 7:11 a.m.)


Review request for Ambari, Jaimin Jetly, Jonathan Hurley, Jayush Luniya, Nate 
Cole, Robert Nettleton, and Tom Beerbower.


Changes
---

Updates addressing comments.


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


Repository: ambari


Description
---

In order to properly handle the automated installation or removal of a security 
infrastructure (like Kerberos) in the cluster, Ambari needs to know whether 
each component on the hosts of the cluster is properly _secured_ or not.  This 
information may be compared with data on the Ambari server to help determine 
what steps should be taken to ensure the cluster is in the correct _secured_ 
state.

To do this, the current and desired component security state is maintained in 
the Ambari database.  The Ambari server will update the desired state details 
according to whether the cluster is to be secured or not and whether the 
relevant service has enough metadata to be secured.  If the desired and actual 
security state details do not match, the Ambari server will take the necessary 
steps to work towards synchronization. 

In order for a component to indicate its security status, a new property needs 
to be returned in the `STATUS_COMMAND` response message (from the Ambari 
agent).  This property should be named ‘securityState’ and should have one of 
the following values:

* `UNKNOWN` - Indicates that it is not known whether the service or component 
is secured or not
* `UNSECURED` - Indicates service or component is not or should not be secured
* `SECURED_KERBEROS` - Indicates component is or should be secured using 
Kerberos
* `ERROR` - Indicates the component is not secured due to an error condition

To properly set this state value, a call needs to be executed per component 
querying for its specific state.  Due to the differences on how each component 
is secured and how it may be determined if security is setup what type is 
configured, and working is it properly, it is necessary for each component to 
have its own logic for determining this state. Therefore the ambari-agent 
process will need to call into the component’s configured (lifecycle) script 
and wait for its response - not unlike how it determines whether the component 
is up and running.

After the infrastructure is in place, each service definition needs to be 
updated to implement the new security status check function.  The function 
should perform the following steps:

* Determine if security is enabled or disabled
** If disabled, return "UNSECURED"
** If enabled, determine what type of security is enabled
*** If Kerberos is configured
 Perform tests (kinit?, ping KDC?) to determine if the configuration 
appears to be working
* If working, return “SECURED_KERBEROS”
* If not working, return “ERROR”
*** Else, return "UNKNOWN"

If no function is available, the Ambari agent should return “UNKNOWN”.


Diffs (updated)
-

  ambari-agent/src/main/python/ambari_agent/ActionQueue.py fbde26f 
  ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py 
08dddae 
  ambari-agent/src/test/python/ambari_agent/TestActionQueue.py 52b586b 
  ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py 
24ee259 

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


Testing
---

Updated the following unit tests:
* ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py
* ambari-agent/src/test/python/ambari_agent/TestActionQueue.py


[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 03:06 min
[INFO] Finished at: 2014-11-27T15:35:18+00:00
[INFO] Final Memory: 80M/411M
[INFO] 


Thanks,

Robert Levas

[jira] [Created] (AMBARI-8630) Hosts / Host Details: Stack Version Management: Integrate with final API

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-8630:


 Summary: Hosts / Host Details: Stack Version Management: Integrate 
with final API
 Key: AMBARI-8630
 URL: https://issues.apache.org/jira/browse/AMBARI-8630
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
 Fix For: 2.0.0


Integrate Stack Version Management on Hosts/Host detail pages with latest API.



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

[jira] [Updated] (AMBARI-8630) Hosts / Host Details: Stack Version Management: Integrate with final API

[Andrii Tkach (JIRA)]

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

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

> Hosts / Host Details: Stack Version Management: Integrate with final API
> 
>
> Key: AMBARI-8630
> URL: https://issues.apache.org/jira/browse/AMBARI-8630
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.0.0
>
> Attachments: AMBARI-8630.patch
>
>
> Integrate Stack Version Management on Hosts/Host detail pages with latest API.



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

Review Request 28899: Hosts / Host Details: Stack Version Management: Integrate with final API

[Andrii Tkach]

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

Review request for Ambari and Aleksandr Kovalenko.


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


Repository: ambari


Description
---

Integrate Stack Version Management on Hosts/Host detail pages with latest API.


Diffs
-

  ambari-web/app/assets/data/hosts/HDP2/hosts.json b7d1893 
  ambari-web/app/assets/test/tests.js 495b7c8 
  ambari-web/app/controllers/global/update_controller.js 754421c 
  ambari-web/app/controllers/main/host/details.js b8df72c 
  ambari-web/app/mappers/hosts_mapper.js b593913 
  ambari-web/app/models/host.js 8bff1c5 
  ambari-web/app/models/host_stack_version.js 250a24a 
  ambari-web/app/templates/main/host/stack_versions.hbs 2c2988d 
  ambari-web/app/utils/ajax/ajax.js 2c3fc27 
  ambari-web/app/views/main/host.js 34b8e30 
  ambari-web/app/views/main/host/stack_versions_view.js f45ba17 
  ambari-web/test/controllers/main/host/details_test.js 0828cda 
  ambari-web/test/models/host_stack_version_test.js 957ac49 
  ambari-web/test/views/main/host/stack_versions_view_test.js PRE-CREATION 

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


Testing
---


  5119 tests complete (8 seconds)
  60 tests pending


Thanks,

Andrii Tkach

Re: Review Request 28899: Hosts / Host Details: Stack Version Management: Integrate with final API

[Aleksandr Kovalenko]

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

Ship it!


Ship It!

- Aleksandr Kovalenko


On Гру. 10, 2014, 12:20 після полудня, Andrii Tkach wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28899/
> ---
> 
> (Updated Гру. 10, 2014, 12:20 після полудня)
> 
> 
> Review request for Ambari and Aleksandr Kovalenko.
> 
> 
> Bugs: AMBARI-8630
> https://issues.apache.org/jira/browse/AMBARI-8630
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Integrate Stack Version Management on Hosts/Host detail pages with latest API.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/assets/data/hosts/HDP2/hosts.json b7d1893 
>   ambari-web/app/assets/test/tests.js 495b7c8 
>   ambari-web/app/controllers/global/update_controller.js 754421c 
>   ambari-web/app/controllers/main/host/details.js b8df72c 
>   ambari-web/app/mappers/hosts_mapper.js b593913 
>   ambari-web/app/models/host.js 8bff1c5 
>   ambari-web/app/models/host_stack_version.js 250a24a 
>   ambari-web/app/templates/main/host/stack_versions.hbs 2c2988d 
>   ambari-web/app/utils/ajax/ajax.js 2c3fc27 
>   ambari-web/app/views/main/host.js 34b8e30 
>   ambari-web/app/views/main/host/stack_versions_view.js f45ba17 
>   ambari-web/test/controllers/main/host/details_test.js 0828cda 
>   ambari-web/test/models/host_stack_version_test.js 957ac49 
>   ambari-web/test/views/main/host/stack_versions_view_test.js PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/28899/diff/
> 
> 
> Testing
> ---
> 
> 
>   5119 tests complete (8 seconds)
>   60 tests pending
> 
> 
> Thanks,
> 
> Andrii Tkach
> 
>

[jira] [Created] (AMBARI-8631) Provide assigning Alert Groups for Alert Notifications in Alert Notifications popup

[Oleg Nechiporenko (JIRA)]

Oleg Nechiporenko created AMBARI-8631:
-

 Summary: Provide assigning Alert Groups for Alert Notifications in 
Alert Notifications popup
 Key: AMBARI-8631
 URL: https://issues.apache.org/jira/browse/AMBARI-8631
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Priority: Critical
 Fix For: 2.0.0


AlertTarger resource doesn't support changing groups property by direct PUT 
request, so we have to make separate request to change AlertGroup resource.



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

[jira] [Updated] (AMBARI-8627) Allow for service-level Kerberos descriptor to contain multiple services

[Robert Levas (JIRA)]

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

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

Throwing exceptions where needed when failing to parse JSON data.

> Allow for service-level Kerberos descriptor to contain multiple services
> 
>
> Key: AMBARI-8627
> URL: https://issues.apache.org/jira/browse/AMBARI-8627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, kerberos_descriptor, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8627_01.patch, AMBARI-8627_01.patch, 
> AMBARI-8627_02.patch
>
>
> Current Kerberos descriptor handlers assume only a single service may be 
> identified in a service-level Kerberos descriptor file.  However services 
> like YARN include the MAPREDUCE2 service, thus multiple services need to be 
> acknowledged.



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

[jira] [Commented] (AMBARI-8631) Provide assigning Alert Groups for Alert Notifications in Alert Notifications popup

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-8631:
---

  5114 tests complete (8 seconds)
  60 tests pending

> Provide assigning Alert Groups for Alert Notifications in Alert Notifications 
> popup
> ---
>
> Key: AMBARI-8631
> URL: https://issues.apache.org/jira/browse/AMBARI-8631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.0.0
>
>
> AlertTarger resource doesn't support changing groups property by direct PUT 
> request, so we have to make separate request to change AlertGroup resource.



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

[jira] [Updated] (AMBARI-8631) Provide assigning Alert Groups for Alert Notifications in Alert Notifications popup

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-8631:
--
Attachment: AMBARI-8631.patch

> Provide assigning Alert Groups for Alert Notifications in Alert Notifications 
> popup
> ---
>
> Key: AMBARI-8631
> URL: https://issues.apache.org/jira/browse/AMBARI-8631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8631.patch
>
>
> AlertTarger resource doesn't support changing groups property by direct PUT 
> request, so we have to make separate request to change AlertGroup resource.



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

[jira] [Commented] (AMBARI-8631) Provide assigning Alert Groups for Alert Notifications in Alert Notifications popup

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-8631:
-

+1 for the patch

> Provide assigning Alert Groups for Alert Notifications in Alert Notifications 
> popup
> ---
>
> Key: AMBARI-8631
> URL: https://issues.apache.org/jira/browse/AMBARI-8631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8631.patch
>
>
> AlertTarger resource doesn't support changing groups property by direct PUT 
> request, so we have to make separate request to change AlertGroup resource.



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

[jira] [Commented] (AMBARI-8630) Hosts / Host Details: Stack Version Management: Integrate with final API

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8630:
---

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

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

This message is automatically generated.

> Hosts / Host Details: Stack Version Management: Integrate with final API
> 
>
> Key: AMBARI-8630
> URL: https://issues.apache.org/jira/browse/AMBARI-8630
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.0.0
>
> Attachments: AMBARI-8630.patch
>
>
> Integrate Stack Version Management on Hosts/Host detail pages with latest API.



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

[jira] [Commented] (AMBARI-8630) Hosts / Host Details: Stack Version Management: Integrate with final API

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-8630:
--

committed to trunk.

> Hosts / Host Details: Stack Version Management: Integrate with final API
> 
>
> Key: AMBARI-8630
> URL: https://issues.apache.org/jira/browse/AMBARI-8630
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.0.0
>
> Attachments: AMBARI-8630.patch
>
>
> Integrate Stack Version Management on Hosts/Host detail pages with latest API.



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

Re: Review Request 28861: Repository Version Management - Fix ignored tests

[Dmitro Lisnichenko]

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

Ship it!


Ship It!

- Dmitro Lisnichenko


On Dec. 9, 2014, 7:26 p.m., Yurii Shylov wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28861/
> ---
> 
> (Updated Dec. 9, 2014, 7:26 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmitro Lisnichenko, and Nate 
> Cole.
> 
> 
> Bugs: AMBARI-8613
> https://issues.apache.org/jira/browse/AMBARI-8613
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In classes QueryImplTest and RequestImplTest several tests are marked as 
> @Ignored, they should be fixed.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseStacksResourceDefinition.java
>  a3a8261 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/OperatingSystemResourceProvider.java
>  682d8bd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryResourceProvider.java
>  c2a81cd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
>  db7cb58 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
>  4b5486a 
>   
> ambari-server/src/test/java/org/apache/ambari/server/api/query/QueryImplTest.java
>  c2d82a5 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterControllerImplTest.java
>  8eadb37 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
>  5e89178 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestImplTest.java
>  202c69a 
> 
> Diff: https://reviews.apache.org/r/28861/diff/
> 
> 
> Testing
> ---
> 
> Results :
> 
> Tests run: 2401, Failures: 0, Errors: 0, Skipped: 13
> 
> 
> Thanks,
> 
> Yurii Shylov
> 
>

Re: Review Request 28861: Repository Version Management - Fix ignored tests

[Nate Cole]

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

Ship it!


Ship It!

- Nate Cole


On Dec. 9, 2014, 2:26 p.m., Yurii Shylov wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28861/
> ---
> 
> (Updated Dec. 9, 2014, 2:26 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmitro Lisnichenko, and Nate 
> Cole.
> 
> 
> Bugs: AMBARI-8613
> https://issues.apache.org/jira/browse/AMBARI-8613
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In classes QueryImplTest and RequestImplTest several tests are marked as 
> @Ignored, they should be fixed.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseStacksResourceDefinition.java
>  a3a8261 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/OperatingSystemResourceProvider.java
>  682d8bd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryResourceProvider.java
>  c2a81cd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
>  db7cb58 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
>  4b5486a 
>   
> ambari-server/src/test/java/org/apache/ambari/server/api/query/QueryImplTest.java
>  c2d82a5 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterControllerImplTest.java
>  8eadb37 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
>  5e89178 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestImplTest.java
>  202c69a 
> 
> Diff: https://reviews.apache.org/r/28861/diff/
> 
> 
> Testing
> ---
> 
> Results :
> 
> Tests run: 2401, Failures: 0, Errors: 0, Skipped: 13
> 
> 
> Thanks,
> 
> Yurii Shylov
> 
>

[jira] [Commented] (AMBARI-8630) Hosts / Host Details: Stack Version Management: Integrate with final API

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8630:


SUCCESS: Integrated in Ambari-trunk-Commit #1157 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1157/])
AMBARI-8630 Hosts / Host Details: Stack Version Management: Integrate with 
final API. (atkach) (atkach: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dacca7b5fa782a4d08b12017474bb91d747a706f)
* ambari-web/test/controllers/main/host/details_test.js
* ambari-web/app/assets/test/tests.js
* ambari-web/app/templates/main/host/stack_versions.hbs
* ambari-web/app/controllers/global/update_controller.js
* ambari-web/app/models/host.js
* ambari-web/app/mappers/hosts_mapper.js
* ambari-web/app/models/host_stack_version.js
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/test/views/main/host/stack_versions_view_test.js
* ambari-web/app/views/main/host.js
* ambari-web/app/controllers/main/host/details.js
* ambari-web/test/models/host_stack_version_test.js
* ambari-web/app/assets/data/hosts/HDP2/hosts.json
* ambari-web/app/views/main/host/stack_versions_view.js


> Hosts / Host Details: Stack Version Management: Integrate with final API
> 
>
> Key: AMBARI-8630
> URL: https://issues.apache.org/jira/browse/AMBARI-8630
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.0.0
>
> Attachments: AMBARI-8630.patch
>
>
> Integrate Stack Version Management on Hosts/Host detail pages with latest API.



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

[jira] [Commented] (AMBARI-8630) Hosts / Host Details: Stack Version Management: Integrate with final API

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8630:


FAILURE: Integrated in Ambari-trunk-Commit-docker #434 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/434/])
AMBARI-8630 Hosts / Host Details: Stack Version Management: Integrate with 
final API. (atkach) (atkach: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dacca7b5fa782a4d08b12017474bb91d747a706f)
* ambari-web/app/views/main/host.js
* ambari-web/test/views/main/host/stack_versions_view_test.js
* ambari-web/test/controllers/main/host/details_test.js
* ambari-web/app/assets/data/hosts/HDP2/hosts.json
* ambari-web/app/views/main/host/stack_versions_view.js
* ambari-web/app/models/host_stack_version.js
* ambari-web/app/models/host.js
* ambari-web/app/controllers/main/host/details.js
* ambari-web/app/mappers/hosts_mapper.js
* ambari-web/app/controllers/global/update_controller.js
* ambari-web/app/templates/main/host/stack_versions.hbs
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/test/models/host_stack_version_test.js
* ambari-web/app/assets/test/tests.js


> Hosts / Host Details: Stack Version Management: Integrate with final API
> 
>
> Key: AMBARI-8630
> URL: https://issues.apache.org/jira/browse/AMBARI-8630
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.0.0
>
> Attachments: AMBARI-8630.patch
>
>
> Integrate Stack Version Management on Hosts/Host detail pages with latest API.



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

[jira] [Created] (AMBARI-8632) add redirect to the cluster from admin view versions

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-8632:


 Summary: add redirect to the cluster from admin view versions
 Key: AMBARI-8632
 URL: https://issues.apache.org/jira/browse/AMBARI-8632
 Project: Ambari
  Issue Type: Task
  Components: ambari-views
Affects Versions: 2.0.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 2.0.0


after user register repoversion we can go to the cluster to install this 
repoverison on it. ui redirects user when he select some cluster in select box 
on repoversions list page.



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

[jira] [Updated] (AMBARI-8628) Create Kerberos Descriptors for HDFS and YARN services

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-8628:
-
Attachment: service_response.json

This is an example response using the following API call:

{{/api/v1/stacks/HDP/versions/2.2}}

[^service_response.json]

> Create Kerberos Descriptors for HDFS and YARN services
> --
>
> Key: AMBARI-8628
> URL: https://issues.apache.org/jira/browse/AMBARI-8628
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server, stacks
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: hdfs, kerberos, kerberos_descriptor, mapreduce, service, 
> yarn
> Fix For: 2.0.0
>
> Attachments: AMBARI-8628_01.patch, service_response.json
>
>
> Create Kerberos descriptor files for HDFS and YARN (which includes 
> MAPREDUCE2).
> These files are used to describe the identities and configurations needed to 
> properly enable Kerberos.



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

Re: Review Request 28874: Alert Host Count Summary Exposed Via Cluster Endpoint

[Tom Beerbower]

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

Ship it!


Looks good.

- Tom Beerbower


On Dec. 9, 2014, 10:24 p.m., Jonathan Hurley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28874/
> ---
> 
> (Updated Dec. 9, 2014, 10:24 p.m.)
> 
> 
> Review request for Ambari, Srimanth Gunturi and Tom Beerbower.
> 
> 
> Bugs: AMBARI-8623
> https://issues.apache.org/jira/browse/AMBARI-8623
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In Ambari-1.7.0 the cluster endpoint used to have a summary of host-counts by 
> severity. We need such a field in Ambari-2.0.0.
> {code}
> alerts: {
>  summary: {
>   CRITICAL: 1,
>   OK: 4,
>   PASSIVE: 0,
>   WARNING: 0
>  }
> }
> {code}
> 
> The alerts_summary structure currently returned by the 2.0.0 API are the 
> summary counts of alerts in the system, not those of the hosts. There are 
> alerts that don't have a host (such as aggregate alerts). 
> 
> Add a new field to the cluster endpoint; something like 
> {{alerts_summary_hosts }}
> {noformat}
> http://localhost:8080/api/v1/clusters/c1?fields=alerts_summary_hosts
> {
>   "href" : 
> "http://localhost:8080/api/v1/clusters/c1?fields=alerts_summary_hosts";,
>   "Clusters" : {
> "cluster_name" : "c1",
> "version" : "HDP-2.2"
>   },
>   "alerts_summary_hosts" : {
> "CRITICAL" : 1,
> "OK" : 41,
> "UNKNOWN" : 0,
> "WARNING" : 0
>   }
> }
> {noformat}
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertSummaryPropertyProvider.java
>  e9fef0e 
>   ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertsDAO.java 
> 4908eea 
>   
> ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertsDAOTest.java
>  6876877 
> 
> Diff: https://reviews.apache.org/r/28874/diff/
> 
> 
> Testing
> ---
> 
> New tests added to cover new summary. 
> 
> 
> Thanks,
> 
> Jonathan Hurley
> 
>

[jira] [Updated] (AMBARI-8632) add redirect to the cluster from admin view versions

[Andrii Babiichuk (JIRA)]

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

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

> add redirect to the cluster from admin view versions
> 
>
> Key: AMBARI-8632
> URL: https://issues.apache.org/jira/browse/AMBARI-8632
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-views
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8632.patch
>
>
> after user register repoversion we can go to the cluster to install this 
> repoverison on it. ui redirects user when he select some cluster in select 
> box on repoversions list page.



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

[jira] [Commented] (AMBARI-8632) add redirect to the cluster from admin view versions

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-8632:
--

+1 for the patch.

> add redirect to the cluster from admin view versions
> 
>
> Key: AMBARI-8632
> URL: https://issues.apache.org/jira/browse/AMBARI-8632
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-views
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8632.patch
>
>
> after user register repoversion we can go to the cluster to install this 
> repoverison on it. ui redirects user when he select some cluster in select 
> box on repoversions list page.



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

[jira] [Created] (AMBARI-8633) Dashboard > Config History tab does a "double load"

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-8633:


 Summary: Dashboard > Config History tab does a "double load"
 Key: AMBARI-8633
 URL: https://issues.apache.org/jira/browse/AMBARI-8633
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
 Fix For: 2.0.0


Go to Dashboard > Config History page. The table loads twice.



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

[jira] [Updated] (AMBARI-8633) Dashboard > Config History tab does a "double load"

[Andrii Tkach (JIRA)]

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

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

> Dashboard > Config History tab does a "double load"
> ---
>
> Key: AMBARI-8633
> URL: https://issues.apache.org/jira/browse/AMBARI-8633
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8633.patch
>
>
> Go to Dashboard > Config History page. The table loads twice.



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

[jira] [Commented] (AMBARI-8633) Dashboard > Config History tab does a "double load"

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-8633:
--

+1 for the patch

> Dashboard > Config History tab does a "double load"
> ---
>
> Key: AMBARI-8633
> URL: https://issues.apache.org/jira/browse/AMBARI-8633
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8633.patch
>
>
> Go to Dashboard > Config History page. The table loads twice.



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

[jira] [Commented] (AMBARI-8631) Provide assigning Alert Groups for Alert Notifications in Alert Notifications popup

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8631:
---

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

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

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

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

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

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

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

This message is automatically generated.

> Provide assigning Alert Groups for Alert Notifications in Alert Notifications 
> popup
> ---
>
> Key: AMBARI-8631
> URL: https://issues.apache.org/jira/browse/AMBARI-8631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8631.patch
>
>
> AlertTarger resource doesn't support changing groups property by direct PUT 
> request, so we have to make separate request to change AlertGroup resource.



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

[jira] [Created] (AMBARI-8634) Kerberos wizard->Configure Identities page: Invalidated properties should show error count and disable next button

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-8634:
---

 Summary: Kerberos wizard->Configure Identities page: Invalidated 
properties should show error count and disable next button
 Key: AMBARI-8634
 URL: https://issues.apache.org/jira/browse/AMBARI-8634
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.0.0






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

[jira] [Commented] (AMBARI-8628) Create Kerberos Descriptors for HDFS and YARN services

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8628:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12686274/service_response.json
  against trunk revision .

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

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

This message is automatically generated.

> Create Kerberos Descriptors for HDFS and YARN services
> --
>
> Key: AMBARI-8628
> URL: https://issues.apache.org/jira/browse/AMBARI-8628
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server, stacks
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: hdfs, kerberos, kerberos_descriptor, mapreduce, service, 
> yarn
> Fix For: 2.0.0
>
> Attachments: AMBARI-8628_01.patch, service_response.json
>
>
> Create Kerberos descriptor files for HDFS and YARN (which includes 
> MAPREDUCE2).
> These files are used to describe the identities and configurations needed to 
> properly enable Kerberos.



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

[jira] [Updated] (AMBARI-8634) Kerberos wizard->Configure Identities page: Invalidated properties should show error count and disable next button

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-8634:

Attachment: AMBARI-8634.patch

> Kerberos wizard->Configure Identities page: Invalidated properties should 
> show error count and disable next button
> --
>
> Key: AMBARI-8634
> URL: https://issues.apache.org/jira/browse/AMBARI-8634
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.0.0
>
> Attachments: AMBARI-8634.patch
>
>




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

Review Request 28901: Allow for service-level Kerberos descriptor to contain multiple services

[Robert Levas]

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

Review request for Ambari, Jaimin Jetly, John Speidel, Robert Nettleton, and 
Yusaku Sako.


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


Repository: ambari


Description
---

Current Kerberos descriptor handlers assume only a single service may be 
identified in a service-level Kerberos descriptor file.  However services like 
YARN include the MAPREDUCE2 service, thus multiple services need to be 
acknowledged.

The new format is
```
{
  "services" : [
... 0 or more service blocks ...
  ]
}
```

Also added some exception throwing for validation.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/AbstractKerberosDescriptor.java
 b18e412 
  
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosConfigurationDescriptor.java
 1e33e68 
  
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosDescriptor.java
 14ba19d 
  
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java
 12b588c 
  
ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorTest.java
 e882984 
  
ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptorTest.java
 d905522 
  ambari-server/src/test/resources/service_level_kerberos.json PRE-CREATION 
  ambari-server/src/test/resources/service_level_kerberos_invalid.json 
PRE-CREATION 

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


Testing
---

Updated unit tests:
* org.apache.ambari.server.state.kerberos.KerberosServiceDescriptorTest
* org.apache.ambari.server.state.kerberos.KerberosDescriptorTest

Running org.apache.ambari.server.state.kerberos.KerberosDescriptorTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.271 sec

Running org.apache.ambari.server.state.kerberos.KerberosServiceDescriptorTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.208 sec

Full Test Suite:
Tests run: 2408, Failures: 0, Errors: 0, Skipped: 22


Thanks,

Robert Levas

[jira] [Updated] (AMBARI-8624) Deploy on Ubuntu12, CentOS6, SUSE11 was hanged on install page

[Florian Barca (JIRA)]

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

Florian Barca updated AMBARI-8624:
--
Attachment: AMBARI-8624.0.patch

Fixed heartbeat handlers logic to keep running, and only stop when a stop 
signal has been sent.

> Deploy on Ubuntu12, CentOS6, SUSE11 was hanged on install page
> --
>
> Key: AMBARI-8624
> URL: https://issues.apache.org/jira/browse/AMBARI-8624
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.0.0
> Environment: Linux
>Reporter: Florian Barca
>Assignee: Florian Barca
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: AMBARI-8624.0.patch
>
>
> Try to deploy cluster with all services except AMS, Kafka, Falcon. Deploy was 
> hanged on Install, Start and Test page.
> The root cause is the Agent exiting prematurely when under stress with 
> heartbeats from the server.



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

[jira] [Updated] (AMBARI-8627) Allow for service-level Kerberos descriptor to contain multiple services

[Robert Levas (JIRA)]

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

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

Trying to rerun the automated test.. It's unclear why the test aborted at the 
end.

> Allow for service-level Kerberos descriptor to contain multiple services
> 
>
> Key: AMBARI-8627
> URL: https://issues.apache.org/jira/browse/AMBARI-8627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, kerberos_descriptor, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8627_01.patch, AMBARI-8627_01.patch, 
> AMBARI-8627_02.patch, AMBARI-8627_02.patch
>
>
> Current Kerberos descriptor handlers assume only a single service may be 
> identified in a service-level Kerberos descriptor file.  However services 
> like YARN include the MAPREDUCE2 service, thus multiple services need to be 
> acknowledged.



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

[jira] [Commented] (AMBARI-8611) UI for pre-upgrade checks

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8611:


SUCCESS: Integrated in Ambari-trunk-Commit #1158 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1158/])
AMBARI-8611 UI for pre-upgrade checks. (ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b1853c2f4436254e374c5af0a9d4e5ade662247d)
* ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* ambari-web/app/assets/data/stack_versions/pre_upgrade_check.json
* ambari-web/app/templates/main/admin/stack_versions/repo_versions.hbs
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/templates/main/admin/stack_versions/stack_versions.hbs
* ambari-web/app/views/main/admin/stack_and_upgrade_view.js
* ambari-web/app/messages.js
* ambari-web/app/templates/main/admin/stack_upgrade/pre_upgrade_check_dialog.hbs
* ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js


> UI for pre-upgrade checks
> -
>
> Key: AMBARI-8611
> URL: https://issues.apache.org/jira/browse/AMBARI-8611
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8611.patch
>
>
> add mocks to UI and popup to show check warnings



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

[jira] [Commented] (AMBARI-8632) add redirect to the cluster from admin view versions

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8632:
---

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

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

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

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

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

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

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

This message is automatically generated.

> add redirect to the cluster from admin view versions
> 
>
> Key: AMBARI-8632
> URL: https://issues.apache.org/jira/browse/AMBARI-8632
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-views
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8632.patch
>
>
> after user register repoversion we can go to the cluster to install this 
> repoverison on it. ui redirects user when he select some cluster in select 
> box on repoversions list page.



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

Re: Review Request 28644: Alerts: Nagios Target for Notifications

[Nate Cole]

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

Ship it!


Ship It!

- Nate Cole


On Dec. 8, 2014, 12:34 p.m., Yurii Shylov wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28644/
> ---
> 
> (Updated Dec. 8, 2014, 12:34 p.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley and Nate Cole.
> 
> 
> Bugs: AMBARI-8165
> https://issues.apache.org/jira/browse/AMBARI-8165
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The Ambari Server will be responsible for scheduling the dispatching of 
> alerts that have been received and not yet processed for outbound 
> notification. On a schedule, Ambari will determine the alert targets that 
> should be receiving some sort of notification and then it will gather all 
> alert data for all alerts that are destined for that alert target.
> Nagios is a required notification mechanism. The Nagios server will surface 
> the current state of each alert defined in the system. In order to accomplish 
> this there are two possible methods for implementation:
> 1) Write a python script that Nagios will execute on its own schedule which 
> can then retrieve the current alerts from Ambari's REST APIs. The script will 
> take a combination of parameters (host, security, certificate, etc) in order 
> to make the requests.
> 2) Write a dispatcher that can handle pushing data to a Nagios server. There 
> will no longer be an agent running on Nagios, so this method would need to 
> work with Nagios' built-in mechanism, if any, for publishing data into Nagios.
> 
> 
> Diffs
> -
> 
>   contrib/addons/package/deb/create_nagios_addon_deb.sh a64e045 
>   contrib/addons/package/rpm/create_nagios_addon_rpm.sh 42a2e28 
>   contrib/nagios-alerts/plugins/ambari_alerts.py PRE-CREATION 
>   contrib/nagios-alerts/plugins/generate_nagios_objects.py PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/28644/diff/
> 
> 
> Testing
> ---
> 
> Total run:674
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Yurii Shylov
> 
>

[jira] [Commented] (AMBARI-8611) UI for pre-upgrade checks

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8611:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #435 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/435/])
AMBARI-8611 UI for pre-upgrade checks. (ababiichuk) (ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b1853c2f4436254e374c5af0a9d4e5ade662247d)
* ambari-web/app/templates/main/admin/stack_upgrade/pre_upgrade_check_dialog.hbs
* ambari-web/app/templates/main/admin/stack_versions/stack_versions.hbs
* ambari-web/app/assets/data/stack_versions/pre_upgrade_check.json
* ambari-web/app/templates/main/admin/stack_versions/repo_versions.hbs
* ambari-web/app/views/main/admin/stack_and_upgrade_view.js
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/messages.js
* ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js


> UI for pre-upgrade checks
> -
>
> Key: AMBARI-8611
> URL: https://issues.apache.org/jira/browse/AMBARI-8611
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8611.patch
>
>
> add mocks to UI and popup to show check warnings



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

Review Request 28902: Config validations not displaying ERRORs

[Andrew Onischuk]

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

Review request for Ambari and Vitalyi Brodetskyi.


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


Repository: ambari


Description
---

Went and changed a tez property, POST /validations is called and the response
returns two things: WARN and ERROR.

Only the WARN is showing in the UI. Need to also inform the user about ERROR.

See attached.


Diffs
-

  
ambari-server/src/main/resources/stacks/HDP/2.2/services/TEZ/configuration/tez-site.xml
 50345fd 

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


Testing
---

mvn clean test


Thanks,

Andrew Onischuk

[jira] [Created] (AMBARI-8635) Config validations not displaying ERRORs

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-8635:
---

 Summary: Config validations not displaying ERRORs
 Key: AMBARI-8635
 URL: https://issues.apache.org/jira/browse/AMBARI-8635
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.0.0


Went and changed a tez property, POST /validations is called and the response
returns two things: WARN and ERROR.

Only the WARN is showing in the UI. Need to also inform the user about ERROR.

See attached.





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

[jira] [Created] (AMBARI-8636) Packages ambari-agent and ambari-server cannot be authenticated using ubuntu 12.04

[Julien Pellet (JIRA)]

Julien Pellet created AMBARI-8636:
-

 Summary: Packages ambari-agent and ambari-server cannot be 
authenticated using ubuntu 12.04
 Key: AMBARI-8636
 URL: https://issues.apache.org/jira/browse/AMBARI-8636
 Project: Ambari
  Issue Type: Bug
  Components: infra
Affects Versions: 1.7.0
 Environment: ubuntu 12.04
Reporter: Julien Pellet


After installing the apt source according to the doc:
wget -nv http://public-repo-
1.hortonworks.com/HDP/ubuntu12/2.x/GA/2.2.0.0/hdp.list -O 
/etc/apt/sources.list.d/HDP.list 

After adding the key :

apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD


I still have a warning, preventing to install it with a configuration manager :

root@chef:~# apt-get install ambari-agent 
Reading package lists... Done 
Building dependency tree  
Reading state information... Done 
The following NEW packages will be installed: 
  ambari-agent
0 upgraded, 1 newly installed, 0 to remove and 131 not upgraded.  
Need to get 0 B/2,288 kB of archives. 
After this operation, 7,576 kB of additional disk space will be used. 
WARNING: The following packages cannot be authenticated!  
  ambari-agent
Install these packages without verification [y/N]?




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

[GitHub] ambari pull request: Fix init hdfs fails.

[vitovitolo]

GitHub user vitovitolo opened a pull request:

https://github.com/apache/ambari/pull/13

Fix init hdfs fails.

Use 'hadoop dfsadmin' to execute hdfs command is deprecated.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vitovitolo/ambari init_hdfs

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ambari/pull/13.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #13


commit 6b96b61d1c9c61ef7e80e348761c2a79b195f708
Author: Victor Torre 
Date:   2014-12-10T15:19:03Z

Fix init hdfs fails: Use of this script to execute hdfs command is 
deprecated.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AMBARI-8636) Packages ambari-agent and ambari-server cannot be authenticated using ubuntu 12.04

[Jeff Sposetti (JIRA)]

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

Jeff Sposetti commented on AMBARI-8636:
---

Did you run apt-get update?

{code}
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD
apt-get update
apt-get install ambari-agent -y
{code}


> Packages ambari-agent and ambari-server cannot be authenticated using ubuntu 
> 12.04
> --
>
> Key: AMBARI-8636
> URL: https://issues.apache.org/jira/browse/AMBARI-8636
> Project: Ambari
>  Issue Type: Bug
>  Components: infra
>Affects Versions: 1.7.0
> Environment: ubuntu 12.04
>Reporter: Julien Pellet
>
> After installing the apt source according to the doc:
> wget -nv http://public-repo-
> 1.hortonworks.com/HDP/ubuntu12/2.x/GA/2.2.0.0/hdp.list -O 
> /etc/apt/sources.list.d/HDP.list 
> After adding the key :
> apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD
> I still have a warning, preventing to install it with a configuration manager 
> :
> root@chef:~# apt-get install ambari-agent 
> Reading package lists... Done 
> Building dependency tree  
> Reading state information... Done 
> The following NEW packages will be installed: 
>   ambari-agent
> 0 upgraded, 1 newly installed, 0 to remove and 131 not upgraded.  
> Need to get 0 B/2,288 kB of archives. 
> After this operation, 7,576 kB of additional disk space will be used. 
> WARNING: The following packages cannot be authenticated!  
>   ambari-agent
> Install these packages without verification [y/N]?



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

[jira] [Resolved] (AMBARI-8636) Packages ambari-agent and ambari-server cannot be authenticated using ubuntu 12.04

[Julien Pellet (JIRA)]

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

Julien Pellet resolved AMBARI-8636.
---
Resolution: Fixed

> Packages ambari-agent and ambari-server cannot be authenticated using ubuntu 
> 12.04
> --
>
> Key: AMBARI-8636
> URL: https://issues.apache.org/jira/browse/AMBARI-8636
> Project: Ambari
>  Issue Type: Bug
>  Components: infra
>Affects Versions: 1.7.0
> Environment: ubuntu 12.04
>Reporter: Julien Pellet
>
> After installing the apt source according to the doc:
> wget -nv http://public-repo-
> 1.hortonworks.com/HDP/ubuntu12/2.x/GA/2.2.0.0/hdp.list -O 
> /etc/apt/sources.list.d/HDP.list 
> After adding the key :
> apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD
> I still have a warning, preventing to install it with a configuration manager 
> :
> root@chef:~# apt-get install ambari-agent 
> Reading package lists... Done 
> Building dependency tree  
> Reading state information... Done 
> The following NEW packages will be installed: 
>   ambari-agent
> 0 upgraded, 1 newly installed, 0 to remove and 131 not upgraded.  
> Need to get 0 B/2,288 kB of archives. 
> After this operation, 7,576 kB of additional disk space will be used. 
> WARNING: The following packages cannot be authenticated!  
>   ambari-agent
> Install these packages without verification [y/N]?



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

[jira] [Commented] (AMBARI-8613) Repository Version Management - Fix ignored tests

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8613:


SUCCESS: Integrated in Ambari-trunk-Commit #1159 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1159/])
AMBARI-8613. Repository Version Management - Fix ignored tests (yshylov via 
dlysnichenko) (dlysnichenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e148fca5aadff1f8720de8285d700c1fde7f8a7b)
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/query/QueryImplTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestImplTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterControllerImplTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/OperatingSystemResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseStacksResourceDefinition.java


> Repository Version Management - Fix ignored tests
> -
>
> Key: AMBARI-8613
> URL: https://issues.apache.org/jira/browse/AMBARI-8613
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Yurii Shylov
>Assignee: Yurii Shylov
> Fix For: 2.0.0
>
> Attachments: AMBARI-8613.patch
>
>
> In classes QueryImplTest and RequestImplTest several tests are marked as 
> \@Ignored, they should be fixed.



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

[jira] [Commented] (AMBARI-8631) Provide assigning Alert Groups for Alert Notifications in Alert Notifications popup

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8631:


SUCCESS: Integrated in Ambari-trunk-Commit #1159 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1159/])
AMBARI-8631. Provide assigning Alert Groups for Alert Notifications in Alert 
Notifications popup. (onechiporenko) (onechiporenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=00f7a6a61cdffb9e6bc0b3055332aa40e84c3a57)
* ambari-web/test/mappers/alert_groups_mapper_test.js
* ambari-web/app/views/main/alerts/manage_alert_notifications_view.js
* ambari-web/app/messages.js
* ambari-web/app/templates/main/alerts/create_alert_notification.hbs
* ambari-web/app/mappers/alert_groups_mapper.js
* ambari-web/app/styles/alerts.less
* 
ambari-web/test/controllers/main/alerts/manage_alert_notifications_controller_test.js
* 
ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js


> Provide assigning Alert Groups for Alert Notifications in Alert Notifications 
> popup
> ---
>
> Key: AMBARI-8631
> URL: https://issues.apache.org/jira/browse/AMBARI-8631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8631.patch
>
>
> AlertTarger resource doesn't support changing groups property by direct PUT 
> request, so we have to make separate request to change AlertGroup resource.



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

[jira] [Commented] (AMBARI-8633) Dashboard > Config History tab does a "double load"

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8633:
---

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

This message is automatically generated.

> Dashboard > Config History tab does a "double load"
> ---
>
> Key: AMBARI-8633
> URL: https://issues.apache.org/jira/browse/AMBARI-8633
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8633.patch
>
>
> Go to Dashboard > Config History page. The table loads twice.



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

[jira] [Commented] (AMBARI-8636) Packages ambari-agent and ambari-server cannot be authenticated using ubuntu 12.04

[Julien Pellet (JIRA)]

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

Julien Pellet commented on AMBARI-8636:
---

Ok my bad, I did it in a bad order.

> Packages ambari-agent and ambari-server cannot be authenticated using ubuntu 
> 12.04
> --
>
> Key: AMBARI-8636
> URL: https://issues.apache.org/jira/browse/AMBARI-8636
> Project: Ambari
>  Issue Type: Bug
>  Components: infra
>Affects Versions: 1.7.0
> Environment: ubuntu 12.04
>Reporter: Julien Pellet
>
> After installing the apt source according to the doc:
> wget -nv http://public-repo-
> 1.hortonworks.com/HDP/ubuntu12/2.x/GA/2.2.0.0/hdp.list -O 
> /etc/apt/sources.list.d/HDP.list 
> After adding the key :
> apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD
> I still have a warning, preventing to install it with a configuration manager 
> :
> root@chef:~# apt-get install ambari-agent 
> Reading package lists... Done 
> Building dependency tree  
> Reading state information... Done 
> The following NEW packages will be installed: 
>   ambari-agent
> 0 upgraded, 1 newly installed, 0 to remove and 131 not upgraded.  
> Need to get 0 B/2,288 kB of archives. 
> After this operation, 7,576 kB of additional disk space will be used. 
> WARNING: The following packages cannot be authenticated!  
>   ambari-agent
> Install these packages without verification [y/N]?



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

Re: Review Request 28901: Allow for service-level Kerberos descriptor to contain multiple services

[John Speidel]

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

Ship it!


looks good


ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java


would be more flexible to use 'Collection' for instanceof check and cast 
instead of list since you aren't using any List specific functions



ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java


just wanted to be sure that it is ok for the map to be null and have an 
empty array returned


- John Speidel


On Dec. 10, 2014, 2:25 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28901/
> ---
> 
> (Updated Dec. 10, 2014, 2:25 p.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, John Speidel, Robert Nettleton, and 
> Yusaku Sako.
> 
> 
> Bugs: AMBARI-8627
> https://issues.apache.org/jira/browse/AMBARI-8627
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Current Kerberos descriptor handlers assume only a single service may be 
> identified in a service-level Kerberos descriptor file.  However services 
> like YARN include the MAPREDUCE2 service, thus multiple services need to be 
> acknowledged.
> 
> The new format is
> ```
> {
>   "services" : [
> ... 0 or more service blocks ...
>   ]
> }
> ```
> 
> Also added some exception throwing for validation.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/AbstractKerberosDescriptor.java
>  b18e412 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosConfigurationDescriptor.java
>  1e33e68 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosDescriptor.java
>  14ba19d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java
>  12b588c 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorTest.java
>  e882984 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptorTest.java
>  d905522 
>   ambari-server/src/test/resources/service_level_kerberos.json PRE-CREATION 
>   ambari-server/src/test/resources/service_level_kerberos_invalid.json 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/28901/diff/
> 
> 
> Testing
> ---
> 
> Updated unit tests:
> * org.apache.ambari.server.state.kerberos.KerberosServiceDescriptorTest
> * org.apache.ambari.server.state.kerberos.KerberosDescriptorTest
> 
> Running org.apache.ambari.server.state.kerberos.KerberosDescriptorTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.271 sec
> 
> Running org.apache.ambari.server.state.kerberos.KerberosServiceDescriptorTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.208 sec
> 
> Full Test Suite:
> Tests run: 2408, Failures: 0, Errors: 0, Skipped: 22
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

[jira] [Commented] (AMBARI-8632) add redirect to the cluster from admin view versions

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-8632:
--

was tested manual

> add redirect to the cluster from admin view versions
> 
>
> Key: AMBARI-8632
> URL: https://issues.apache.org/jira/browse/AMBARI-8632
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-views
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8632.patch
>
>
> after user register repoversion we can go to the cluster to install this 
> repoverison on it. ui redirects user when he select some cluster in select 
> box on repoversions list page.



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

Review Request 28903: Views: API - URLStreamProvider timeout control

[Andrew Onischuk]

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

Review request for Ambari and Tom Beerbower.


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


Repository: ambari


Description
---

Need to add possibility to change request timeout when making request through
ViewContext.getURLStreamProvider().readFrom

Now we're experiencing problems with it using WebHCat: responses pretty slow
and we need to make timeout bigger.


Diffs
-

  ambari-server/conf/unix/ambari.properties e5b9e7b 
  
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
 73a353e 
  ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java 
55f3a75 

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


Testing
---

mvn clean test


Thanks,

Andrew Onischuk

[jira] [Created] (AMBARI-8637) Views: API - URLStreamProvider timeout control

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-8637:
---

 Summary: Views: API - URLStreamProvider timeout control
 Key: AMBARI-8637
 URL: https://issues.apache.org/jira/browse/AMBARI-8637
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.0.0


Need to add possibility to change request timeout when making request through
ViewContext.getURLStreamProvider().readFrom

Now we're experiencing problems with it using WebHCat: responses pretty slow
and we need to make timeout bigger.





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

[jira] [Created] (AMBARI-8638) Alerts UI: include username + password

[Oleg Nechiporenko (JIRA)]

Oleg Nechiporenko created AMBARI-8638:
-

 Summary: Alerts UI: include username + password
 Key: AMBARI-8638
 URL: https://issues.apache.org/jira/browse/AMBARI-8638
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
 Fix For: 2.0.0


On alert notification, type = email, should also include the SMTP username and 
password fields in the UI by default for the user to set.



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

[jira] [Commented] (AMBARI-8613) Repository Version Management - Fix ignored tests

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8613:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #436 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/436/])
AMBARI-8613. Repository Version Management - Fix ignored tests (yshylov via 
dlysnichenko) (dlysnichenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e148fca5aadff1f8720de8285d700c1fde7f8a7b)
* 
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseStacksResourceDefinition.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterControllerImplTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestImplTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/query/QueryImplTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/OperatingSystemResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java


> Repository Version Management - Fix ignored tests
> -
>
> Key: AMBARI-8613
> URL: https://issues.apache.org/jira/browse/AMBARI-8613
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Yurii Shylov
>Assignee: Yurii Shylov
> Fix For: 2.0.0
>
> Attachments: AMBARI-8613.patch
>
>
> In classes QueryImplTest and RequestImplTest several tests are marked as 
> \@Ignored, they should be fixed.



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

[jira] [Commented] (AMBARI-8631) Provide assigning Alert Groups for Alert Notifications in Alert Notifications popup

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8631:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #436 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/436/])
AMBARI-8631. Provide assigning Alert Groups for Alert Notifications in Alert 
Notifications popup. (onechiporenko) (onechiporenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=00f7a6a61cdffb9e6bc0b3055332aa40e84c3a57)
* ambari-web/app/mappers/alert_groups_mapper.js
* ambari-web/app/messages.js
* ambari-web/test/mappers/alert_groups_mapper_test.js
* ambari-web/app/views/main/alerts/manage_alert_notifications_view.js
* ambari-web/app/templates/main/alerts/create_alert_notification.hbs
* ambari-web/app/styles/alerts.less
* 
ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js
* 
ambari-web/test/controllers/main/alerts/manage_alert_notifications_controller_test.js


> Provide assigning Alert Groups for Alert Notifications in Alert Notifications 
> popup
> ---
>
> Key: AMBARI-8631
> URL: https://issues.apache.org/jira/browse/AMBARI-8631
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8631.patch
>
>
> AlertTarger resource doesn't support changing groups property by direct PUT 
> request, so we have to make separate request to change AlertGroup resource.



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

[jira] [Commented] (AMBARI-8638) Alerts UI: include username + password

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-8638:
---

  5126 tests complete (8 seconds)
  60 tests pending

> Alerts UI: include username + password
> --
>
> Key: AMBARI-8638
> URL: https://issues.apache.org/jira/browse/AMBARI-8638
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8638.patch
>
>
> On alert notification, type = email, should also include the SMTP username 
> and password fields in the UI by default for the user to set.



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

[jira] [Updated] (AMBARI-8638) Alerts UI: include username + password

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-8638:
--
Attachment: AMBARI-8638.patch

> Alerts UI: include username + password
> --
>
> Key: AMBARI-8638
> URL: https://issues.apache.org/jira/browse/AMBARI-8638
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8638.patch
>
>
> On alert notification, type = email, should also include the SMTP username 
> and password fields in the UI by default for the user to set.



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

[jira] [Commented] (AMBARI-8633) Dashboard > Config History tab does a "double load"

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-8633:
--

committed to trunk.

> Dashboard > Config History tab does a "double load"
> ---
>
> Key: AMBARI-8633
> URL: https://issues.apache.org/jira/browse/AMBARI-8633
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8633.patch
>
>
> Go to Dashboard > Config History page. The table loads twice.



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

[jira] [Commented] (AMBARI-8638) Alerts UI: include username + password

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-8638:
--

+1 for the patch

> Alerts UI: include username + password
> --
>
> Key: AMBARI-8638
> URL: https://issues.apache.org/jira/browse/AMBARI-8638
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8638.patch
>
>
> On alert notification, type = email, should also include the SMTP username 
> and password fields in the UI by default for the user to set.



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

Re: Review Request 28902: Config validations not displaying ERRORs

[Vitalyi Brodetskyi]

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

Ship it!


Ship It!

- Vitalyi Brodetskyi


On Гру. 10, 2014, 3:17 після полудня, Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28902/
> ---
> 
> (Updated Гру. 10, 2014, 3:17 після полудня)
> 
> 
> Review request for Ambari and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-8635
> https://issues.apache.org/jira/browse/AMBARI-8635
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Went and changed a tez property, POST /validations is called and the response
> returns two things: WARN and ERROR.
> 
> Only the WARN is showing in the UI. Need to also inform the user about ERROR.
> 
> See attached.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/TEZ/configuration/tez-site.xml
>  50345fd 
> 
> Diff: https://reviews.apache.org/r/28902/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

[jira] [Created] (AMBARI-8639) Distribute Repository/Install: parallel install not working

[Dmitry Lysnichenko (JIRA)]

Dmitry Lysnichenko created AMBARI-8639:
--

 Summary: Distribute Repository/Install: parallel install not 
working
 Key: AMBARI-8639
 URL: https://issues.apache.org/jira/browse/AMBARI-8639
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.0.0
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
 Fix For: 2.0.0


As of Dec 9.

* Installed a brand new cluster from trunk.
* Installed initial repository with no issue of 2.2.0.0-2041.
* This created repo files HDP.repo and HDP-UTILS.repo on each host.
* All green.

Then, attempted creation of a new version.  Custom Action invoked successfully, 
but the result failed.

1. For HDP, ended up with two files:  HDP.repo and HDP-2.2.repo.  Each file 
contained a repo named "HDP-2.2".  The output of the yum invokation contains:

{noformat}
2014-12-09 19:19:54,929 - Package['zookeeper_2_2_*'] {}
2014-12-09 19:19:55,300 - Skipping installing existent package zookeeper_2_2_*
{noformat}
which should definitely NOT happen.

2.  The name of the repository file should be a little more specific.  There 
may be several "HDP-2.2" that a cluster is upgraded to.
3.  The installation should use ONLY the repo designated that it just created, 
such that we know that the version installed is from the correct repo.  The 
command should be something like: {{yum install --disablerepo=* 
--enablerepo="HDP-2.2.0.0-1234" zookeeper_2_2_*}}




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

Re: Review Request 28874: Alert Host Count Summary Exposed Via Cluster Endpoint

[Jonathan Hurley]

> On Dec. 9, 2014, 6:28 p.m., Srimanth Gunturi wrote:
> > Jonathan, I was testing out Ambari-1.7.0, and the output for hosts-summary 
> > is given in such a way that the sum of all counts is always equal to the 
> > number of hosts. If a host has CRITICAL and WARNING, it wont contribute to 
> > WARNING count. Similarly, OKs dont contribute to WARNING. CRITICAL > 
> > WARNING > UNKNOWN > OK. It is worth verifying how that logic was 
> > implemented.
> > 
> > For Ambari-2.0.0 we could do it like above. The other option is to 
> > introduce a new field called CRITICAL_OR_WARNING.

Since we only seem to care about the number of hosts with critical or warning, 
then I suggest we do:
```
  "alerts_summary_hosts" : {
"CRITICAL" : 2,
"WARNING" : 0,
"WARNING_OR_CRITICAL" : 3
  }
}
```

In fact, we might even just want to do 

```
  "alerts_summary_hosts" : {
"WARNING_OR_CRITICAL" : 3
  }
}
```

At this point in time since the other calculations could  be expensive and they 
are not used. So, if you're OK with a single value that represents the number 
of hosts that have either a warning or a critical, then I'd say we go with that.


- Jonathan


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


On Dec. 9, 2014, 5:24 p.m., Jonathan Hurley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28874/
> ---
> 
> (Updated Dec. 9, 2014, 5:24 p.m.)
> 
> 
> Review request for Ambari, Srimanth Gunturi and Tom Beerbower.
> 
> 
> Bugs: AMBARI-8623
> https://issues.apache.org/jira/browse/AMBARI-8623
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In Ambari-1.7.0 the cluster endpoint used to have a summary of host-counts by 
> severity. We need such a field in Ambari-2.0.0.
> {code}
> alerts: {
>  summary: {
>   CRITICAL: 1,
>   OK: 4,
>   PASSIVE: 0,
>   WARNING: 0
>  }
> }
> {code}
> 
> The alerts_summary structure currently returned by the 2.0.0 API are the 
> summary counts of alerts in the system, not those of the hosts. There are 
> alerts that don't have a host (such as aggregate alerts). 
> 
> Add a new field to the cluster endpoint; something like 
> {{alerts_summary_hosts }}
> {noformat}
> http://localhost:8080/api/v1/clusters/c1?fields=alerts_summary_hosts
> {
>   "href" : 
> "http://localhost:8080/api/v1/clusters/c1?fields=alerts_summary_hosts";,
>   "Clusters" : {
> "cluster_name" : "c1",
> "version" : "HDP-2.2"
>   },
>   "alerts_summary_hosts" : {
> "CRITICAL" : 1,
> "OK" : 41,
> "UNKNOWN" : 0,
> "WARNING" : 0
>   }
> }
> {noformat}
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertSummaryPropertyProvider.java
>  e9fef0e 
>   ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertsDAO.java 
> 4908eea 
>   
> ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertsDAOTest.java
>  6876877 
> 
> Diff: https://reviews.apache.org/r/28874/diff/
> 
> 
> Testing
> ---
> 
> New tests added to cover new summary. 
> 
> 
> Thanks,
> 
> Jonathan Hurley
> 
>

[jira] [Updated] (AMBARI-8639) Distribute Repository/Install: parallel install not working

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-8639:
---
Attachment: AMBARI-8639.patch

> Distribute Repository/Install: parallel install not working
> ---
>
> Key: AMBARI-8639
> URL: https://issues.apache.org/jira/browse/AMBARI-8639
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8639.patch
>
>
> As of Dec 9.
> * Installed a brand new cluster from trunk.
> * Installed initial repository with no issue of 2.2.0.0-2041.
> * This created repo files HDP.repo and HDP-UTILS.repo on each host.
> * All green.
> Then, attempted creation of a new version.  Custom Action invoked 
> successfully, but the result failed.
> 1. For HDP, ended up with two files:  HDP.repo and HDP-2.2.repo.  Each file 
> contained a repo named "HDP-2.2".  The output of the yum invokation contains:
> {noformat}
> 2014-12-09 19:19:54,929 - Package['zookeeper_2_2_*'] {}
> 2014-12-09 19:19:55,300 - Skipping installing existent package zookeeper_2_2_*
> {noformat}
> which should definitely NOT happen.
> 2.  The name of the repository file should be a little more specific.  There 
> may be several "HDP-2.2" that a cluster is upgraded to.
> 3.  The installation should use ONLY the repo designated that it just 
> created, such that we know that the version installed is from the correct 
> repo.  The command should be something like: {{yum install --disablerepo=* 
> --enablerepo="HDP-2.2.0.0-1234" zookeeper_2_2_*}}



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

Review Request 28905: Distribute Repository/Install: parallel install not working

[Dmitro Lisnichenko]

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

Review request for Ambari, Alejandro Fernandez, Nate Cole, and Yurii Shylov.


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


Repository: ambari


Description
---

As of Dec 9.
Installed a brand new cluster from trunk.
Installed initial repository with no issue of 2.2.0.0-2041.
This created repo files HDP.repo and HDP-UTILS.repo on each host.
All green.
Then, attempted creation of a new version. Custom Action invoked successfully, 
but the result failed.
1. For HDP, ended up with two files: HDP.repo and HDP-2.2.repo. Each file 
contained a repo named "HDP-2.2". The output of the yum invokation contains:
2014-12-09 19:19:54,929 - Package['zookeeper_2_2_*'] {}
2014-12-09 19:19:55,300 - Skipping installing existent package zookeeper_2_2_*
which should definitely NOT happen.
2. The name of the repository file should be a little more specific. There may 
be several "HDP-2.2" that a cluster is upgraded to.
3. The installation should use ONLY the repo designated that it just created, 
such that we know that the version installed is from the correct repo. The 
command should be something like: yum install --disablerepo=* 
--enablerepo="HDP-2.2.0.0-1234" zookeeper_2_2_*


Diffs
-

  ambari-agent/src/test/python/resource_management/TestPackageResource.py 
140dda9 
  
ambari-common/src/main/python/resource_management/core/providers/package/__init__.py
 5ab2b27 
  
ambari-common/src/main/python/resource_management/core/providers/package/apt.py 
c683be5 
  
ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
 7d868b0 
  
ambari-common/src/main/python/resource_management/core/providers/package/zypper.py
 764da73 
  ambari-common/src/main/python/resource_management/core/resources/packaging.py 
c2ff20e 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
 1c2297b 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
 b278177 
  ambari-server/src/main/resources/custom_actions/scripts/install_packages.py 
3e8113a 
  ambari-server/src/test/python/custom_actions/TestInstallPackages.py bbb96e7 
  
ambari-server/src/test/python/custom_actions/configs/install_packages_config.json
 9ea9f47 

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


Testing
---

[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Views .. SUCCESS [2.972s]
[INFO] Ambari Server . SUCCESS [28:44.868s]
[INFO] Ambari Agent .. SUCCESS [7.521s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 28:55.959s
[INFO] Finished at: Wed Dec 10 18:48:11 FET 2014
[INFO] Final Memory: 35M/196M
[INFO] 


Thanks,

Dmitro Lisnichenko

[jira] [Updated] (AMBARI-8639) Distribute Repository/Install: parallel install not working

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-8639:
---
Issue Type: Technical task  (was: Task)
Parent: AMBARI-8424

> Distribute Repository/Install: parallel install not working
> ---
>
> Key: AMBARI-8639
> URL: https://issues.apache.org/jira/browse/AMBARI-8639
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8639.patch
>
>
> As of Dec 9.
> * Installed a brand new cluster from trunk.
> * Installed initial repository with no issue of 2.2.0.0-2041.
> * This created repo files HDP.repo and HDP-UTILS.repo on each host.
> * All green.
> Then, attempted creation of a new version.  Custom Action invoked 
> successfully, but the result failed.
> 1. For HDP, ended up with two files:  HDP.repo and HDP-2.2.repo.  Each file 
> contained a repo named "HDP-2.2".  The output of the yum invokation contains:
> {noformat}
> 2014-12-09 19:19:54,929 - Package['zookeeper_2_2_*'] {}
> 2014-12-09 19:19:55,300 - Skipping installing existent package zookeeper_2_2_*
> {noformat}
> which should definitely NOT happen.
> 2.  The name of the repository file should be a little more specific.  There 
> may be several "HDP-2.2" that a cluster is upgraded to.
> 3.  The installation should use ONLY the repo designated that it just 
> created, such that we know that the version installed is from the correct 
> repo.  The command should be something like: {{yum install --disablerepo=* 
> --enablerepo="HDP-2.2.0.0-1234" zookeeper_2_2_*}}



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

Re: Review Request 28905: Distribute Repository/Install: parallel install not working

[Nate Cole]

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

Ship it!



ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py


Do you need an len(use_repos) as well?  If the argument is not passed, will 
this check be true with an empty array?


- Nate Cole


On Dec. 10, 2014, 10:51 a.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28905/
> ---
> 
> (Updated Dec. 10, 2014, 10:51 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Nate Cole, and Yurii Shylov.
> 
> 
> Bugs: AMBARI-8639
> https://issues.apache.org/jira/browse/AMBARI-8639
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> As of Dec 9.
> Installed a brand new cluster from trunk.
> Installed initial repository with no issue of 2.2.0.0-2041.
> This created repo files HDP.repo and HDP-UTILS.repo on each host.
> All green.
> Then, attempted creation of a new version. Custom Action invoked 
> successfully, but the result failed.
> 1. For HDP, ended up with two files: HDP.repo and HDP-2.2.repo. Each file 
> contained a repo named "HDP-2.2". The output of the yum invokation contains:
> 2014-12-09 19:19:54,929 - Package['zookeeper_2_2_*'] {}
> 2014-12-09 19:19:55,300 - Skipping installing existent package zookeeper_2_2_*
> which should definitely NOT happen.
> 2. The name of the repository file should be a little more specific. There 
> may be several "HDP-2.2" that a cluster is upgraded to.
> 3. The installation should use ONLY the repo designated that it just created, 
> such that we know that the version installed is from the correct repo. The 
> command should be something like: yum install --disablerepo=* 
> --enablerepo="HDP-2.2.0.0-1234" zookeeper_2_2_*
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/test/python/resource_management/TestPackageResource.py 
> 140dda9 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/__init__.py
>  5ab2b27 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/apt.py
>  c683be5 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
>  7d868b0 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/zypper.py
>  764da73 
>   
> ambari-common/src/main/python/resource_management/core/resources/packaging.py 
> c2ff20e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
>  1c2297b 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
>  b278177 
>   ambari-server/src/main/resources/custom_actions/scripts/install_packages.py 
> 3e8113a 
>   ambari-server/src/test/python/custom_actions/TestInstallPackages.py bbb96e7 
>   
> ambari-server/src/test/python/custom_actions/configs/install_packages_config.json
>  9ea9f47 
> 
> Diff: https://reviews.apache.org/r/28905/diff/
> 
> 
> Testing
> ---
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Views .. SUCCESS [2.972s]
> [INFO] Ambari Server . SUCCESS 
> [28:44.868s]
> [INFO] Ambari Agent .. SUCCESS [7.521s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 28:55.959s
> [INFO] Finished at: Wed Dec 10 18:48:11 FET 2014
> [INFO] Final Memory: 35M/196M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

[jira] [Updated] (AMBARI-8549) Rolling Upgrade: ClusterStackVersion should display only one repository version

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-8549:
---
Issue Type: Technical task  (was: Bug)
Parent: AMBARI-8424

> Rolling Upgrade: ClusterStackVersion should display only one repository 
> version
> ---
>
> Key: AMBARI-8549
> URL: https://issues.apache.org/jira/browse/AMBARI-8549
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8549.2.patch, AMBARI-8549.3.patch, 
> AMBARI-8549.patch
>
>
> for now cluster stack version resource contains all created repository 
> versions:
> {code}
> "href": 
> "http://h1:8080/api/v1/clusters/1/stack_versions?fields=repository_versions/*";,
> "items": [
> {
> "href": "http://h1:8080/api/v1/clusters/1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "1",
> "id": 1,
> "stack": "HDP",
> "version": "2.2"
> },
> "repository_versions": [
> {
> "href": 
> "http://h1:8080/api/v1/clusters/1/stack_versions/1/repository_versions/1";,
> "RepositoryVersions": {
> "display_name": "HDP 2.2.0",
> "id": 1,
> "repository_version": "2.2.0.1-885",
> "stack_name": "HDP",
> "stack_version": "2.2",
> "upgrade_pack": "upgrade-2.2"
> }
>  },
> {
> "href": 
> "http://h1:8080/api/v1/clusters/1/stack_versions/1/repository_versions/2";,
> "RepositoryVersions": {
> "display_name": "HDP 2.2.1",
> "id": 2,
> "repository_version": "2.2.1.1-885",
> "stack_name": "HDP",
> "stack_version": "2.2",
> "upgrade_pack": "upgrade-2.2"
> }
> }
> ]
> }
> ]
> }
> {code}
> but each cluster stack version sould contain only 1 repository version:
> {code}
> "href": 
> "http://h1:8080/api/v1/clusters/1/stack_versions?fields=repository_versions/*";
> "items": [
> {
> "href": "http://h1:8080/api/v1/clusters/1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "1",
> "id": 1,
> "stack": "HDP",
> "version": "2.2"
> },
> "repository_versions": [
> {
> "href": 
> "http://h1:8080/api/v1/clusters/1/stack_versions/1/repository_versions/1";,
> "RepositoryVersions": {
> "display_name": "HDP 2.2.0",
> "id": 1,
> "repository_version": "2.2.0.1-885",
> "stack_name": "HDP",
> "stack_version": "2.2",
> "upgrade_pack": "upgrade-2.2"
> }
>  }
> ]
> }
> {
> "href": "http://h1:8080/api/v1/clusters/1/stack_versions/2";,
> "ClusterStackVersions": {
> "cluster_name": "1",
> "id": 2,
> "stack": "HDP",
> "version": "2.2"
> },
> "repository_versions": [
> {
> "href": 
> "http://h1:8080/api/v1/clusters/1/stack_versions/1/repository_versions/2";,
> "RepositoryVersions": {
> "display_name": "HDP 2.2.1",
> "id": 2,
> "repository_version": "2.2.1.1-885",
> "stack_name": "HDP",
> "stack_version": "2.2",
> "upgrade_pack": "upgrade-2.2"
> }
> }
> ]
> }
> ]
> }
> {code}



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

Re: Review Request 28905: Distribute Repository/Install: parallel install not working

[Dmitro Lisnichenko]

> On Dec. 10, 2014, 4:01 p.m., Nate Cole wrote:
> > ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py,
> >  lines 36-38
> > 
> >
> > Do you need an len(use_repos) as well?  If the argument is not passed, 
> > will this check be true with an empty array?

Empty list (a default value) is false in python


- Dmitro


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


On Dec. 10, 2014, 3:51 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28905/
> ---
> 
> (Updated Dec. 10, 2014, 3:51 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Nate Cole, and Yurii Shylov.
> 
> 
> Bugs: AMBARI-8639
> https://issues.apache.org/jira/browse/AMBARI-8639
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> As of Dec 9.
> Installed a brand new cluster from trunk.
> Installed initial repository with no issue of 2.2.0.0-2041.
> This created repo files HDP.repo and HDP-UTILS.repo on each host.
> All green.
> Then, attempted creation of a new version. Custom Action invoked 
> successfully, but the result failed.
> 1. For HDP, ended up with two files: HDP.repo and HDP-2.2.repo. Each file 
> contained a repo named "HDP-2.2". The output of the yum invokation contains:
> 2014-12-09 19:19:54,929 - Package['zookeeper_2_2_*'] {}
> 2014-12-09 19:19:55,300 - Skipping installing existent package zookeeper_2_2_*
> which should definitely NOT happen.
> 2. The name of the repository file should be a little more specific. There 
> may be several "HDP-2.2" that a cluster is upgraded to.
> 3. The installation should use ONLY the repo designated that it just created, 
> such that we know that the version installed is from the correct repo. The 
> command should be something like: yum install --disablerepo=* 
> --enablerepo="HDP-2.2.0.0-1234" zookeeper_2_2_*
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/test/python/resource_management/TestPackageResource.py 
> 140dda9 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/__init__.py
>  5ab2b27 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/apt.py
>  c683be5 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
>  7d868b0 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/zypper.py
>  764da73 
>   
> ambari-common/src/main/python/resource_management/core/resources/packaging.py 
> c2ff20e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
>  1c2297b 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
>  b278177 
>   ambari-server/src/main/resources/custom_actions/scripts/install_packages.py 
> 3e8113a 
>   ambari-server/src/test/python/custom_actions/TestInstallPackages.py bbb96e7 
>   
> ambari-server/src/test/python/custom_actions/configs/install_packages_config.json
>  9ea9f47 
> 
> Diff: https://reviews.apache.org/r/28905/diff/
> 
> 
> Testing
> ---
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Views .. SUCCESS [2.972s]
> [INFO] Ambari Server . SUCCESS 
> [28:44.868s]
> [INFO] Ambari Agent .. SUCCESS [7.521s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 28:55.959s
> [INFO] Finished at: Wed Dec 10 18:48:11 FET 2014
> [INFO] Final Memory: 35M/196M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

[jira] [Created] (AMBARI-8640) Namenode install fails on multi-drive environment

[Eugene Chekanskiy (JIRA)]

Eugene Chekanskiy created AMBARI-8640:
-

 Summary: Namenode install fails on multi-drive environment
 Key: AMBARI-8640
 URL: https://issues.apache.org/jira/browse/AMBARI-8640
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.0.0
Reporter: Eugene Chekanskiy
Assignee: Eugene Chekanskiy
 Fix For: 2.0.0






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

Re: Review Request 28905: Distribute Repository/Install: parallel install not working

[Yurii Shylov]

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

Ship it!


Ship It!

- Yurii Shylov


On Дек. 10, 2014, 3:51 п.п., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28905/
> ---
> 
> (Updated Дек. 10, 2014, 3:51 п.п.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Nate Cole, and Yurii Shylov.
> 
> 
> Bugs: AMBARI-8639
> https://issues.apache.org/jira/browse/AMBARI-8639
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> As of Dec 9.
> Installed a brand new cluster from trunk.
> Installed initial repository with no issue of 2.2.0.0-2041.
> This created repo files HDP.repo and HDP-UTILS.repo on each host.
> All green.
> Then, attempted creation of a new version. Custom Action invoked 
> successfully, but the result failed.
> 1. For HDP, ended up with two files: HDP.repo and HDP-2.2.repo. Each file 
> contained a repo named "HDP-2.2". The output of the yum invokation contains:
> 2014-12-09 19:19:54,929 - Package['zookeeper_2_2_*'] {}
> 2014-12-09 19:19:55,300 - Skipping installing existent package zookeeper_2_2_*
> which should definitely NOT happen.
> 2. The name of the repository file should be a little more specific. There 
> may be several "HDP-2.2" that a cluster is upgraded to.
> 3. The installation should use ONLY the repo designated that it just created, 
> such that we know that the version installed is from the correct repo. The 
> command should be something like: yum install --disablerepo=* 
> --enablerepo="HDP-2.2.0.0-1234" zookeeper_2_2_*
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/test/python/resource_management/TestPackageResource.py 
> 140dda9 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/__init__.py
>  5ab2b27 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/apt.py
>  c683be5 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
>  7d868b0 
>   
> ambari-common/src/main/python/resource_management/core/providers/package/zypper.py
>  764da73 
>   
> ambari-common/src/main/python/resource_management/core/resources/packaging.py 
> c2ff20e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
>  1c2297b 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
>  b278177 
>   ambari-server/src/main/resources/custom_actions/scripts/install_packages.py 
> 3e8113a 
>   ambari-server/src/test/python/custom_actions/TestInstallPackages.py bbb96e7 
>   
> ambari-server/src/test/python/custom_actions/configs/install_packages_config.json
>  9ea9f47 
> 
> Diff: https://reviews.apache.org/r/28905/diff/
> 
> 
> Testing
> ---
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Views .. SUCCESS [2.972s]
> [INFO] Ambari Server . SUCCESS 
> [28:44.868s]
> [INFO] Ambari Agent .. SUCCESS [7.521s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 28:55.959s
> [INFO] Finished at: Wed Dec 10 18:48:11 FET 2014
> [INFO] Final Memory: 35M/196M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

[jira] [Updated] (AMBARI-8623) Alert Host Count Summary Exposed Via Cluster Endpoint

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-8623:

Attachment: AMBARI-8623.patch

> Alert Host Count Summary Exposed Via Cluster Endpoint
> -
>
> Key: AMBARI-8623
> URL: https://issues.apache.org/jira/browse/AMBARI-8623
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8623.patch
>
>
> In Ambari-1.7.0 the cluster endpoint used to have a summary of host-counts by 
> severity. We need such a field in Ambari-2.0.0.
> {code}
> alerts: {
>  summary: {
>   CRITICAL: 1,
>   OK: 4,
>   PASSIVE: 0,
>   WARNING: 0
>  }
> }
> {code}
> The alerts_summary structure currently returned by the 2.0.0 API are the 
> summary counts of alerts in the system, not those of the hosts. There are 
> alerts that don't have a host (such as aggregate alerts). 
> In order to expose the host alert count, there are two ways to do this:
> 1) Add a new field to the cluster endpoint; something like 
> {{alerts_host_summary}}
> {noformat}
> http://localhost:8080/api/v1/clusters/c1?fields=alerts_host_summary
> {
>   "href" : 
> "http://localhost:8080/api/v1/clusters/c1?fields=alerts_host_summary";,
>   "Clusters" : {
> "cluster_name" : "c1",
> "version" : "HDP-2.2"
>   },
>   "alerts_host_summary" : {
> "CRITICAL" : 1,
> "OK" : 41,
> "UNKNOWN" : 0,
> "WARNING" : 0
>   }
> }
> {noformat}
> 2) Provide a new formatter to display the alerts formatted by host:
> {noformat}
> http://localhost:8080/api/v1/clusters/c1/alerts?format=hostSummary
> {
>   "href" : 
> "http://localhost:8080/api/v1/clusters/c1/alerts?format=hostSummary";,
>   "alerts_summary" : {
> "CRITICAL" : {
>   "count" : 1,
>   "original_timestamp" : 1418150735812
> },
> "OK" : {
>   "count" : 41,
>   "original_timestamp" : 1418151145325
> },
> "UNKNOWN" : {
>   "count" : 0,
>   "original_timestamp" : 0
> },
> "WARNING" : {
>   "count" : 0,
>   "original_timestamp" : 0
> }
>   }
> }
> {noformat}



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

[jira] [Commented] (AMBARI-8632) add redirect to the cluster from admin view versions

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8632:


FAILURE: Integrated in Ambari-trunk-Commit #1160 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1160/])
AMBARI-8632 add redirect to the cluster from admin view versions. (ababiichuk) 
(ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cd38a54d6d48152e65623af6c4ddc4b4f00a5ad5)
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsListCtrl.js
* ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/list.html


> add redirect to the cluster from admin view versions
> 
>
> Key: AMBARI-8632
> URL: https://issues.apache.org/jira/browse/AMBARI-8632
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-views
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8632.patch
>
>
> after user register repoversion we can go to the cluster to install this 
> repoverison on it. ui redirects user when he select some cluster in select 
> box on repoversions list page.



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

[jira] [Commented] (AMBARI-8633) Dashboard > Config History tab does a "double load"

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8633:


FAILURE: Integrated in Ambari-trunk-Commit #1160 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1160/])
AMBARI-8633 Dashboard > Config History tab does a "double load". (atkach) 
(atkach: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c1482f8202d9c02879e566b7885174cc331d4c47)
* ambari-web/app/views/main/dashboard/config_history_view.js
* ambari-web/test/views/main/dashboard/config_history_view_test.js


> Dashboard > Config History tab does a "double load"
> ---
>
> Key: AMBARI-8633
> URL: https://issues.apache.org/jira/browse/AMBARI-8633
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8633.patch
>
>
> Go to Dashboard > Config History page. The table loads twice.



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

[jira] [Commented] (AMBARI-8632) add redirect to the cluster from admin view versions

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8632:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #437 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/437/])
AMBARI-8632 add redirect to the cluster from admin view versions. (ababiichuk) 
(ababiichuk: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cd38a54d6d48152e65623af6c4ddc4b4f00a5ad5)
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsListCtrl.js
* ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/list.html


> add redirect to the cluster from admin view versions
> 
>
> Key: AMBARI-8632
> URL: https://issues.apache.org/jira/browse/AMBARI-8632
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-views
>Affects Versions: 2.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.0.0
>
> Attachments: AMBARI-8632.patch
>
>
> after user register repoversion we can go to the cluster to install this 
> repoverison on it. ui redirects user when he select some cluster in select 
> box on repoversions list page.



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

[jira] [Created] (AMBARI-8641) Unuseful architecture constraints for packaging

[Tony Reix (JIRA)]

Tony Reix created AMBARI-8641:
-

 Summary: Unuseful architecture constraints for packaging
 Key: AMBARI-8641
 URL: https://issues.apache.org/jira/browse/AMBARI-8641
 Project: Ambari
  Issue Type: Bug
 Environment: Ubuntu / PPC64LE
Reporter: Tony Reix
Priority: Critical


Files:
  pom.xml
  ambari-shell/ambari-python-shell/pom.xml
  ambari-server/pom.xml
  ambari-client/python-client/pom.xml
  ambari-agent/pom.xml
contain lines like:
  amd64
  amd64

When creating a Ambari package with command:
 mvn -B package jdeb:jdeb -Pnode-local -DnewVersion=${AMBARI_VERSION} 
-DskipTests -Dpython.ver="python > 2.6" -Preplaceurl -l mvn.package.res
on my Ubuntu / PPC64LE machine, it creates Debian packaging data that require 
amd64 to be the Debian architecture of the machine where to install the package.
And, thus, the package cannot be installed on my Ubuntu/PPC64LE machine.
Example: file "control" of file control.tar.gz of package 
ambari-agent_1.6.1-1.deb contains the line:
  Architecture: amd64

Ambari seems to be the only one Hadoop package to have such constraints in 
pom.xml files for building the package.
However, Ambari looks to me to be "noarch", since it is pure Java code.
So, I think these "amd64" architecture values do not fit all cases (like my 
PPC64LE machine) and - moreover - they seem useless.
So, I suggest to remove them.



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

Re: Review Request 28901: Allow for service-level Kerberos descriptor to contain multiple services

[Robert Levas]

> On Dec. 10, 2014, 10:33 a.m., John Speidel wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java,
> >  line 200
> > 
> >
> > just wanted to be sure that it is ok for the map to be null and have an 
> > empty array returned

It should be ok. No services in the descriptor file is acceptable - but 
probably would never happen.


> On Dec. 10, 2014, 10:33 a.m., John Speidel wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java,
> >  line 188
> > 
> >
> > would be more flexible to use 'Collection' for instanceof check and 
> > cast instead of list since you aren't using any List specific functions

Agreed.. making this change.


- Robert


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


On Dec. 10, 2014, 9:25 a.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28901/
> ---
> 
> (Updated Dec. 10, 2014, 9:25 a.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, John Speidel, Robert Nettleton, and 
> Yusaku Sako.
> 
> 
> Bugs: AMBARI-8627
> https://issues.apache.org/jira/browse/AMBARI-8627
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Current Kerberos descriptor handlers assume only a single service may be 
> identified in a service-level Kerberos descriptor file.  However services 
> like YARN include the MAPREDUCE2 service, thus multiple services need to be 
> acknowledged.
> 
> The new format is
> ```
> {
>   "services" : [
> ... 0 or more service blocks ...
>   ]
> }
> ```
> 
> Also added some exception throwing for validation.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/AbstractKerberosDescriptor.java
>  b18e412 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosConfigurationDescriptor.java
>  1e33e68 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosDescriptor.java
>  14ba19d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java
>  12b588c 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorTest.java
>  e882984 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptorTest.java
>  d905522 
>   ambari-server/src/test/resources/service_level_kerberos.json PRE-CREATION 
>   ambari-server/src/test/resources/service_level_kerberos_invalid.json 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/28901/diff/
> 
> 
> Testing
> ---
> 
> Updated unit tests:
> * org.apache.ambari.server.state.kerberos.KerberosServiceDescriptorTest
> * org.apache.ambari.server.state.kerberos.KerberosDescriptorTest
> 
> Running org.apache.ambari.server.state.kerberos.KerberosDescriptorTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.271 sec
> 
> Running org.apache.ambari.server.state.kerberos.KerberosServiceDescriptorTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.208 sec
> 
> Full Test Suite:
> Tests run: 2408, Failures: 0, Errors: 0, Skipped: 22
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

[jira] [Commented] (AMBARI-8624) Deploy on Ubuntu12, CentOS6, SUSE11 was hanged on install page

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8624:
---

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

This message is automatically generated.

> Deploy on Ubuntu12, CentOS6, SUSE11 was hanged on install page
> --
>
> Key: AMBARI-8624
> URL: https://issues.apache.org/jira/browse/AMBARI-8624
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.0.0
> Environment: Linux
>Reporter: Florian Barca
>Assignee: Florian Barca
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: AMBARI-8624.0.patch
>
>
> Try to deploy cluster with all services except AMS, Kafka, Falcon. Deploy was 
> hanged on Install, Start and Test page.
> The root cause is the Agent exiting prematurely when under stress with 
> heartbeats from the server.



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

[jira] [Updated] (AMBARI-8627) Allow for service-level Kerberos descriptor to contain multiple services

[Robert Levas (JIRA)]

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

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

Updates due to reviewers comments.

Patch File [^AMBARI-8627_03.patch]

> Allow for service-level Kerberos descriptor to contain multiple services
> 
>
> Key: AMBARI-8627
> URL: https://issues.apache.org/jira/browse/AMBARI-8627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, kerberos_descriptor, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8627_01.patch, AMBARI-8627_01.patch, 
> AMBARI-8627_02.patch, AMBARI-8627_02.patch, AMBARI-8627_03.patch
>
>
> Current Kerberos descriptor handlers assume only a single service may be 
> identified in a service-level Kerberos descriptor file.  However services 
> like YARN include the MAPREDUCE2 service, thus multiple services need to be 
> acknowledged.



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

[jira] [Commented] (AMBARI-8638) Alerts UI: include username + password

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8638:


SUCCESS: Integrated in Ambari-trunk-Commit #1161 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1161/])
AMBARI-8638. Alerts UI: include username + password. (onechiporenko) 
(onechiporenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=96b7f56fec4fe89d0b1a1721a8d8badc8573d207)
* ambari-web/app/messages.js
* 
ambari-web/test/controllers/main/alerts/manage_alert_notifications_controller_test.js
* ambari-web/app/assets/data/alerts/alertGroups.json
* ambari-web/app/templates/main/alerts/create_alert_notification.hbs
* 
ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js


> Alerts UI: include username + password
> --
>
> Key: AMBARI-8638
> URL: https://issues.apache.org/jira/browse/AMBARI-8638
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8638.patch
>
>
> On alert notification, type = email, should also include the SMTP username 
> and password fields in the UI by default for the user to set.



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

[jira] [Commented] (AMBARI-8638) Alerts UI: include username + password

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8638:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #438 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/438/])
AMBARI-8638. Alerts UI: include username + password. (onechiporenko) 
(onechiporenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=96b7f56fec4fe89d0b1a1721a8d8badc8573d207)
* ambari-web/app/templates/main/alerts/create_alert_notification.hbs
* ambari-web/app/assets/data/alerts/alertGroups.json
* 
ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js
* 
ambari-web/test/controllers/main/alerts/manage_alert_notifications_controller_test.js
* ambari-web/app/messages.js


> Alerts UI: include username + password
> --
>
> Key: AMBARI-8638
> URL: https://issues.apache.org/jira/browse/AMBARI-8638
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8638.patch
>
>
> On alert notification, type = email, should also include the SMTP username 
> and password fields in the UI by default for the user to set.



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

[jira] [Commented] (AMBARI-8633) Dashboard > Config History tab does a "double load"

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8633:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #438 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/438/])
AMBARI-8633 Dashboard > Config History tab does a "double load". (atkach) 
(atkach: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c1482f8202d9c02879e566b7885174cc331d4c47)
* ambari-web/test/views/main/dashboard/config_history_view_test.js
* ambari-web/app/views/main/dashboard/config_history_view.js


> Dashboard > Config History tab does a "double load"
> ---
>
> Key: AMBARI-8633
> URL: https://issues.apache.org/jira/browse/AMBARI-8633
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8633.patch
>
>
> Go to Dashboard > Config History page. The table loads twice.



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

[jira] [Commented] (AMBARI-8639) Distribute Repository/Install: parallel install not working

[Hudson (JIRA)]

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

Hudson commented on AMBARI-8639:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #438 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/438/])
AMBARI-8639. Distribute Repository/Install: parallel install not working 
(dlysnichenko) (dlysnichenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b60f26ee9a3ae20a37e49f0158e581862643ef86)
* 
ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
* ambari-server/src/test/python/custom_actions/TestInstallPackages.py
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
* 
ambari-common/src/main/python/resource_management/core/providers/package/__init__.py
* ambari-agent/src/test/python/resource_management/TestPackageResource.py
* ambari-common/src/main/python/resource_management/core/resources/packaging.py
* 
ambari-common/src/main/python/resource_management/core/providers/package/zypper.py
* ambari-server/src/main/resources/custom_actions/scripts/install_packages.py
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* 
ambari-server/src/test/python/custom_actions/configs/install_packages_config.json
* 
ambari-common/src/main/python/resource_management/core/providers/package/apt.py


> Distribute Repository/Install: parallel install not working
> ---
>
> Key: AMBARI-8639
> URL: https://issues.apache.org/jira/browse/AMBARI-8639
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8639.patch
>
>
> As of Dec 9.
> * Installed a brand new cluster from trunk.
> * Installed initial repository with no issue of 2.2.0.0-2041.
> * This created repo files HDP.repo and HDP-UTILS.repo on each host.
> * All green.
> Then, attempted creation of a new version.  Custom Action invoked 
> successfully, but the result failed.
> 1. For HDP, ended up with two files:  HDP.repo and HDP-2.2.repo.  Each file 
> contained a repo named "HDP-2.2".  The output of the yum invokation contains:
> {noformat}
> 2014-12-09 19:19:54,929 - Package['zookeeper_2_2_*'] {}
> 2014-12-09 19:19:55,300 - Skipping installing existent package zookeeper_2_2_*
> {noformat}
> which should definitely NOT happen.
> 2.  The name of the repository file should be a little more specific.  There 
> may be several "HDP-2.2" that a cluster is upgraded to.
> 3.  The installation should use ONLY the repo designated that it just 
> created, such that we know that the version installed is from the correct 
> repo.  The command should be something like: {{yum install --disablerepo=* 
> --enablerepo="HDP-2.2.0.0-1234" zookeeper_2_2_*}}



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

[jira] [Created] (AMBARI-8642) Issues with "Test DB Connection" in HiveServer2 Move Master Wizard

[Szilard Nemethy (JIRA)]

Szilard Nemethy created AMBARI-8642:
---

 Summary: Issues with "Test DB Connection" in HiveServer2 Move 
Master Wizard
 Key: AMBARI-8642
 URL: https://issues.apache.org/jira/browse/AMBARI-8642
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server, ambari-web
Reporter: Szilard Nemethy
Assignee: Szilard Nemethy
Priority: Critical
 Fix For: 2.0.0


Scenario "HiveServer2":
● Fresh install of the ambari­server. 
● Create a new cluster with specific services. with internal hive DB
● Move the HiveServer2 to another host machine. :
Select Move HiveServer2 from the Service Actions drop down box
select the host to assign the new master to
go thru wizard to move HiveServer2
Expected
HiveServer2 successfully moved from host1 to host2
Actual
error on step "Test DB Connection"
1 try to test DB on host1(rather than host2)
if move next from host2 to host3 it test on host1(host that installed at first)
2 mysql not started on host1 or host2



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

[jira] [Commented] (AMBARI-8634) Kerberos wizard->Configure Identities page: Invalidated properties should show error count and disable next button

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-8634:
---

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

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

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

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

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

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

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

This message is automatically generated.

> Kerberos wizard->Configure Identities page: Invalidated properties should 
> show error count and disable next button
> --
>
> Key: AMBARI-8634
> URL: https://issues.apache.org/jira/browse/AMBARI-8634
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.0.0
>
> Attachments: AMBARI-8634.patch
>
>




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

[jira] [Updated] (AMBARI-8642) Issues with "Test DB Connection" in HiveServer2 Move Master Wizard

[Szilard Nemethy (JIRA)]

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

Szilard Nemethy updated AMBARI-8642:

Attachment: AMBARI-8642.patch

> Issues with "Test DB Connection" in HiveServer2 Move Master Wizard
> --
>
> Key: AMBARI-8642
> URL: https://issues.apache.org/jira/browse/AMBARI-8642
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Reporter: Szilard Nemethy
>Assignee: Szilard Nemethy
>Priority: Critical
>  Labels: ambari-server, ambari-web
> Fix For: 2.0.0
>
> Attachments: AMBARI-8642.patch
>
>
> Scenario "HiveServer2":
> ● Fresh install of the ambari­server. 
> ● Create a new cluster with specific services. with internal hive DB
> ● Move the HiveServer2 to another host machine. :
> Select Move HiveServer2 from the Service Actions drop down box
> select the host to assign the new master to
> go thru wizard to move HiveServer2
> Expected
> HiveServer2 successfully moved from host1 to host2
> Actual
> error on step "Test DB Connection"
> 1 try to test DB on host1(rather than host2)
> if move next from host2 to host3 it test on host1(host that installed at 
> first)
> 2 mysql not started on host1 or host2



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

Review Request 28907: Issues with "Test DB Connection" in HiveServer2 Move Master Wizard

[Szilard Nemethy]

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

Review request for Ambari, Nate Cole and Srimanth Gunturi.


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


Repository: ambari


Description
---

Scenario "HiveServer2":
? Fresh install of the ambari­server. 
? Create a new cluster with specific services. with internal hive DB
? Move the HiveServer2 to another host machine. :
Select Move HiveServer2 from the Service Actions drop down box
select the host to assign the new master to
go thru wizard to move HiveServer2
Expected
HiveServer2 successfully moved from host1 to host2
Actual
error on step "Test DB Connection"
1 try to test DB on host1(rather than host2)
if move next from host2 to host3 it test on host1(host that installed at first)
2 mysql not started on host1 or host2


Diffs
-

  
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/files/addMysqlUser.sh
 f366055 
  ambari-web/app/assets/test/tests.js 495b7c8 
  ambari-web/app/controllers/main/service/info/configs.js 4de6379 
  ambari-web/app/controllers/main/service/reassign/step1_controller.js 2f35650 
  ambari-web/app/controllers/main/service/reassign/step4_controller.js 3a1c487 
  ambari-web/app/controllers/main/service/reassign/step6_controller.js a189a27 
  ambari-web/app/controllers/main/service/reassign_controller.js 7c4f9ab 
  ambari-web/app/messages.js d0a58f6 
  ambari-web/app/routes/reassign_master_routes.js 738a018 
  ambari-web/app/templates/main/admin/highAvailability/progress.hbs 
PRE-CREATION 
  ambari-web/app/templates/main/service/reassign/step1.hbs 63a344d 
  ambari-web/app/templates/main/service/reassign/step3.hbs 2eb85a8 
  ambari-web/app/views/main/service/reassign/step1_view.js 1e6b13e 
  ambari-web/app/views/main/service/reassign/step3_view.js 20b8323 
  ambari-web/test/controllers/main/service/reassign/step1_controller_test.js 
PRE-CREATION 
  ambari-web/test/controllers/main/service/reassign/step4_controller_test.js 
889445f 

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


Testing
---

Unit testing.
E2E testing.


Thanks,

Szilard Nemethy

[jira] [Created] (AMBARI-8643) Expose Stage and Upgrade Item update status API.

[Tom Beerbower (JIRA)]

Tom Beerbower created AMBARI-8643:
-

 Summary: Expose Stage and Upgrade Item update status API.
 Key: AMBARI-8643
 URL: https://issues.apache.org/jira/browse/AMBARI-8643
 Project: Ambari
  Issue Type: Task
Reporter: Tom Beerbower
Assignee: Tom Beerbower
 Fix For: 2.0.0


Upgrade Item state diagram:

{code} 
- HOLDING 
|(release)  |
||
||
|   > *ABORTED   |
|   ||
|   |v
**PENDING ---> QUEUED -> IN_PROGRESS ---> *COMPLETED 
 ^  | |  |  |  
 |  | |  |  
---
 |  | |  |
  |
 |  | |  ---
  |
 |  | |   |
  |
 |  | vv
  |
 |  | FAILED* <-- HOLDING_FAILED 
---  |
 |  v   (skip) 
|  |
 |  TIMED_OUT* <- HOLDING_TIMED_OUT 
-->|  |
 |  ^  
|  |
 |  |  
|  |
 |  
---|---
 |  (retry)|
 ---
 
 ** starting state   
 *  terminal states 
{code}

Notes:
* The HOLDING, HOLDING_FAILED, HOLDING_TIMED_OUT states are new.
* An item in the HOLDING state can be completed by pushing its state to the 
COMPLETED state through the API (see below).  This will make the next stage 
become the current stage and advance from the PENDING state.
* An item in the HOLDING_FAILED state can be skipped by pushing its state to 
FAILED state through the API.  This will make the next stage become the current 
stage and advance it from the PENDING state.
* An item in the HOLDING_FAILED state can be retried by pushing its state to 
IN_PROGRESS state through the API.  This will keep the stage as the current 
stage and retry the associated tasks.
* An item in the HOLDING_TIMED_OUT state can be skipped by pushing its state to 
TIMED_OUT state through the API.  This will make the next stage become the 
current stage and advance it from the PENDING state.
* An item in the HOLDING_TIMED_OUT can be retried by pushing its state to 
IN_PROGRESS state through the API.  This will keep the stage as the current 
stage and retry the associated tasks.


Updated Proposed API changes:


# Determine if an upgrade is holding by checking the upgrade resource's status.
{code}
GET api/v1/upgrades/1
{
  "href" : "http://c6401.ambari.apache.org:8080/api/v1/upgrades/1";,
  "Upgrade" : {
...
"request_status" : "HOLDING",
...
}
{code}
# To find the upgrade item that is holding for a given upgrade look for the 
upgrade item that has a status of HOLDING.  Only the current stage should ever 
be in the HOLDING state.
{code}
GET api/v1/upgrades/1?upgrade_items/UpgradeItem/status=HOLDING

{
  "href" : 
"http://c6401.ambari.apache.org:8080/api/v1/upgrades/1?upgrade_items/UpgradeItem/status=HOLDING";,
  "Requests" : {
"id" : 1
  },
  "upgrade_items" : [
{
  "href" : 
"http://c6401.ambari.apache.org:8080/api/v1/upgrades/1/upgrade_items/10";,
  "UpgradeItem" : {
"request_id" : 1,
"stage_id" : 10,
"status" : "HOLDING"
  }
}
  ]
}
{code}
# To release the hold on a upgrade, complete the the stage that is holding by 
setting it's status to COMPLETED.
{code}
PUT api/v1/upgrades/1/upgrade_items/10

{
  "UpgradeItem" : {
"status" : "COMPLETED"
  }
}
{code}
# A stage may be marked as 'hold on error' which gives the opportunity to skip 
or retry a failure/timeout.  If an error occurs while executing the taks of a 
'hold on error' upgrade item its status will be set to HOLDING_FAILED or 
HOLDING_TIMED_OUT.  To retry the upgrade item, set its status back to to 
IN_PROGRESS.
{code}
PUT api/v1/upgrades/1/upgrade_items/10

{
  "UpgradeItem" : {
"status" : "IN_PROGRESS"
  }
}
{code}
# A stage item that is HOLDING_FAILED or HOLDING_TIMED_OUT may be skipped.  To 
skip an item that is in error and holding,  set its status back to to FAILED 
(for HOLDING_FAIL

Review Request 28908: Expose Stage and Upgrade Item update status API.

[Tom Beerbower]

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

Review request for Ambari and Nate Cole.


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


Repository: ambari


Description
---

Initial checkin of API changes for manually triggered/continuable upgrade item.

Note : this is incomplete but intended to unblock UI development by making the 
APIs available.  Additional backend work and testing is required.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/StageStatus.java
 PRE-CREATION 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
 c25152d 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeItemResourceProvider.java
 85d2c9a 
  
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/StageStatusTest.java
 PRE-CREATION 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StageResourceProviderTest.java
 e2d4d9f 

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


Testing
---

Added unit tests for state transition.  Additional unit tests are required.

All existing unit tests pass.

Results :

Tests run: 2402, Failures: 0, Errors: 0, Skipped: 22


Thanks,

Tom Beerbower

Re: Review Request 28903: Views: API - URLStreamProvider timeout control

[Tom Beerbower]

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

Ship it!


Looks good.

- Tom Beerbower


On Dec. 10, 2014, 3:38 p.m., Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28903/
> ---
> 
> (Updated Dec. 10, 2014, 3:38 p.m.)
> 
> 
> Review request for Ambari and Tom Beerbower.
> 
> 
> Bugs: AMBARI-8637
> https://issues.apache.org/jira/browse/AMBARI-8637
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Need to add possibility to change request timeout when making request through
> ViewContext.getURLStreamProvider().readFrom
> 
> Now we're experiencing problems with it using WebHCat: responses pretty slow
> and we need to make timeout bigger.
> 
> 
> Diffs
> -
> 
>   ambari-server/conf/unix/ambari.properties e5b9e7b 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  73a353e 
>   ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java 
> 55f3a75 
> 
> Diff: https://reviews.apache.org/r/28903/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

[jira] [Commented] (AMBARI-8634) Kerberos wizard->Configure Identities page: Invalidated properties should show error count and disable next button

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-8634:
-

+1 for the patch

> Kerberos wizard->Configure Identities page: Invalidated properties should 
> show error count and disable next button
> --
>
> Key: AMBARI-8634
> URL: https://issues.apache.org/jira/browse/AMBARI-8634
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.0.0
>
> Attachments: AMBARI-8634.patch
>
>




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

Review Request 28909: MR2 Service Check failed

[Andrew Onischuk]

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

Review request for Ambari and Vitalyi Brodetskyi.


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


Repository: ambari


Description
---

Installed a single-node cluster with ZK, HDFS, YARN, TEZ.



stderr: 
2014-12-05 20:42:58,117 - Error while executing command 'service_check':
Traceback (most recent call last):
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 152, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/YARN/package/scripts/mapred_service_check.py",
 line 67, in service_check
logoutput=True
  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/libraries/providers/execute_hadoop.py",
 line 50, in action_run
path= self.resource.bin_dir
  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 245, in action_run
raise ex
Fail: Execution of '/usr/bin/sudo su ambari-qa -l -s /bin/bash -c 'export  
PATH='"'"'/usr/lib/ambari-server/*:/usr/lib/ambari-server/*:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/usr/lib/ambari-server/*:/usr/lib/ambari-server/*:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/usr/hdp/current/hadoop-client/bin:/usr/hdp/current/hadoop-yarn-client/bin'"'"'
 > /dev/null ; hadoop --config /etc/hadoop/conf jar 
/usr/hdp/current/hadoop-mapreduce-client/hadoop-mapreduce-examples-2.*.jar 
wordcount /user/ambari-qa/mapredsmokeinput /user/ambari-qa/mapredsmokeoutput'' 
returned 255. 14/12/05 20:42:56 INFO impl.TimelineClientImpl: Timeline service 
address: http://ys1-1.c.pramod-thangali.internal:8188/ws/v1/timeline/
14/12/05 20:42:57 INFO client.RMProxy: Connecting to ResourceManager at 
ys1-1.c.pramod-thangali.internal/10.240.26.65:8050
java.io.FileNotFoundException: File does not exist: 
hdfs://ys1-1.c.pramod-thangali.internal:8020/hdp/apps/2.2.1.0-2048/mapreduce/mapreduce.tar.gz
at org.apache.hadoop.fs.Hdfs.getFileStatus(Hdfs.java:137)
at 
org.apache.hadoop.fs.AbstractFileSystem.resolvePath(AbstractFileSystem.java:460)
at org.apache.hadoop.fs.FileContext$24.next(FileContext.java:2137)
at org.apache.hadoop.fs.FileContext$24.next(FileContext.java:2133)
at org.apache.hadoop.fs.FSLinkResolver.resolve(FSLinkResolver.java:90)
at org.apache.hadoop.fs.FileContext.resolve(FileContext.java:2133)
at org.apache.hadoop.fs.FileContext.resolvePath(FileContext.java:595)
at 
org.apache.hadoop.mapreduce.JobSubmitter.addMRFrameworkToDistributedCache(JobSubmitter.java:753)
at 
org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:435)
at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1296)
at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1293)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1293)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1314)
at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
at sun.reflect.NativeMethodAcces