[jira] [Commented] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support

2016-11-07 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18711:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #272 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/272/])
AMBARI-18711: Ambari-server: DB changes to enable/disable credential 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9b3db7e8338edc0d699c38532d00f12a550436c2])
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceDesiredStateEntity.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Service.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java


> Ambari-server: DB changes to enable/disable credential store support
> 
>
> Key: AMBARI-18711
> URL: https://issues.apache.org/jira/browse/AMBARI-18711
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53216.patch
>
>
> To enable or disable a component to use credential store, changes are 
> required in the DB to keep track of this information. The 
> _servicedesiredstate_ table can keep track of this information using a new 
> *credential_store_enabled* column.
> If a service supports reading passwords from the configuration's JCEKS file, 
> then it will specify this information in its stack definition. Services that 
> support using the credential store can be enabled or disabled to use it. 
> Services that do not, will always be disabled from using the credential store.
> The option to enable or disable the components of a service that has 
> credential store support is provided via the UI and blueprint. This 
> information will then be captured in the _servicedesiredstate_ table in the 
> *credential_store_enabled* column.



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


[jira] [Commented] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support

2016-11-01 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18711:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5901 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5901/])
AMBARI-18711: Ambari-server: DB changes to enable/disable credential 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c0c02d05ff184f89df8e152a63689318160efb18])
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceDesiredStateEntity.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Service.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql


> Ambari-server: DB changes to enable/disable credential store support
> 
>
> Key: AMBARI-18711
> URL: https://issues.apache.org/jira/browse/AMBARI-18711
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53216.patch
>
>
> To enable or disable a component to use credential store, changes are 
> required in the DB to keep track of this information. The 
> _servicedesiredstate_ table can keep track of this information using a new 
> *credential_store_enabled* column.
> If a service supports reading passwords from the configuration's JCEKS file, 
> then it will specify this information in its stack definition. Services that 
> support using the credential store can be enabled or disabled to use it. 
> Services that do not, will always be disabled from using the credential store.
> The option to enable or disable the components of a service that has 
> credential store support is provided via the UI and blueprint. This 
> information will then be captured in the _servicedesiredstate_ table in the 
> *credential_store_enabled* column.



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


[jira] [Commented] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support

2016-10-31 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-18711:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12836174/rb53216.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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest

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

This message is automatically generated.

> Ambari-server: DB changes to enable/disable credential store support
> 
>
> Key: AMBARI-18711
> URL: https://issues.apache.org/jira/browse/AMBARI-18711
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53216.patch
>
>
> To enable or disable a component to use credential store, changes are 
> required in the DB to keep track of this information. The 
> _servicedesiredstate_ table can keep track of this information using a new 
> *credential_store_enabled* column.
> If a service supports reading passwords from the configuration's JCEKS file, 
> then it will specify this information in its stack definition. Services that 
> support using the credential store can be enabled or disabled to use it. 
> Services that do not, will always be disabled from using the credential store.
> The option to enable or disable the components of a service that has 
> credential store support is provided via the UI and blueprint. This 
> information will then be captured in the _servicedesiredstate_ table in the 
> *credential_store_enabled* column.



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


[jira] [Commented] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support

2016-10-31 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18711:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5893 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5893/])
Revert "AMBARI-18711: Ambari-server: DB changes to enable/disable 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=59430dccc51490d0868b87f6cc63e970947e182a])
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Service.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceDesiredStateEntity.java


> Ambari-server: DB changes to enable/disable credential store support
> 
>
> Key: AMBARI-18711
> URL: https://issues.apache.org/jira/browse/AMBARI-18711
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53216.patch
>
>
> To enable or disable a component to use credential store, changes are 
> required in the DB to keep track of this information. The 
> _servicedesiredstate_ table can keep track of this information using a new 
> *credential_store_enabled* column.
> If a service supports reading passwords from the configuration's JCEKS file, 
> then it will specify this information in its stack definition. Services that 
> support using the credential store can be enabled or disabled to use it. 
> Services that do not, will always be disabled from using the credential store.
> The option to enable or disable the components of a service that has 
> credential store support is provided via the UI and blueprint. This 
> information will then be captured in the _servicedesiredstate_ table in the 
> *credential_store_enabled* column.



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


[jira] [Commented] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support

2016-10-27 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18711:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5881 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5881/])
AMBARI-18711: Ambari-server: DB changes to enable/disable credential 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=edc74e6f2a6375064c5a49bef709c24546f09932])
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceDesiredStateEntity.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Service.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql


> Ambari-server: DB changes to enable/disable credential store support
> 
>
> Key: AMBARI-18711
> URL: https://issues.apache.org/jira/browse/AMBARI-18711
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53216.patch
>
>
> To enable or disable a component to use credential store, changes are 
> required in the DB to keep track of this information. The 
> _servicedesiredstate_ table can keep track of this information using a new 
> *credential_store_enabled* column.
> If a service supports reading passwords from the configuration's JCEKS file, 
> then it will specify this information in its stack definition. Services that 
> support using the credential store can be enabled or disabled to use it. 
> Services that do not, will always be disabled from using the credential store.
> The option to enable or disable the components of a service that has 
> credential store support is provided via the UI and blueprint. This 
> information will then be captured in the _servicedesiredstate_ table in the 
> *credential_store_enabled* column.



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


[jira] [Commented] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support

2016-10-26 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-18711:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12835451/rb53216.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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.api.services.AmbariMetaInfoTest
  org.apache.ambari.server.agent.TestHeartbeatHandler
  
org.apache.ambari.server.api.services.KerberosServiceMetaInfoTest
  
org.apache.ambari.server.state.kerberos.KerberosDescriptorUpdateHelperTest
  org.apache.ambari.server.stack.StackManagerTest

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

This message is automatically generated.

> Ambari-server: DB changes to enable/disable credential store support
> 
>
> Key: AMBARI-18711
> URL: https://issues.apache.org/jira/browse/AMBARI-18711
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53216.patch
>
>
> To enable or disable a component to use credential store, changes are 
> required in the DB to keep track of this information. The 
> _servicedesiredstate_ table can keep track of this information using a new 
> *credential_store_enabled* column.
> If a service supports reading passwords from the configuration's JCEKS file, 
> then it will specify this information in its stack definition. Services that 
> support using the credential store can be enabled or disabled to use it. 
> Services that do not, will always be disabled from using the credential store.
> The option to enable or disable the components of a service that has 
> credential store support is provided via the UI and blueprint. This 
> information will then be captured in the _servicedesiredstate_ table in the 
> *credential_store_enabled* column.



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