date:20181205

[jira] [Resolved] (AMBARI-24992) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate

2018-12-05 Thread Sandor Molnar (JIRA)



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

Sandor Molnar resolved AMBARI-24992.

Resolution: Fixed

> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to 
> long certificate 
> -
>
> Key: AMBARI-24992
> URL: https://issues.apache.org/jira/browse/AMBARI-24992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Sandor Molnar
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> I am trying to upgrade to ambari-2.7.0 using  command : *ambari-server 
> upgrade*
> the upgrade operation is failing on Schema upgrade phase
> The exception is : 
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO 
> ambari_configuration (property_name, category_name, property_value) VALUES 
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)  
> Call getNextException to see other errors in the batch.
> {code}
> and i see as per 
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L125
> ambari is having : 
> {code:java}
> CREATE TABLE ambari_configuration (
>   category_name VARCHAR(100) NOT NULL,
>   property_name VARCHAR(100) NOT NULL,
>   property_value VARCHAR(2048),
>   CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, 
> property_name));
> {code}
> property_value as 2048 but i am having certificate length 2050 and ambari is 
> not accepting it.
> this should be fixed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24992) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate

2018-12-05 Thread Sandor Molnar (JIRA)



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

Sandor Molnar updated AMBARI-24992:
---
Fix Version/s: 2.8.0

> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to 
> long certificate 
> -
>
> Key: AMBARI-24992
> URL: https://issues.apache.org/jira/browse/AMBARI-24992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Sandor Molnar
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> I am trying to upgrade to ambari-2.7.0 using  command : *ambari-server 
> upgrade*
> the upgrade operation is failing on Schema upgrade phase
> The exception is : 
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO 
> ambari_configuration (property_name, category_name, property_value) VALUES 
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)  
> Call getNextException to see other errors in the batch.
> {code}
> and i see as per 
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L125
> ambari is having : 
> {code:java}
> CREATE TABLE ambari_configuration (
>   category_name VARCHAR(100) NOT NULL,
>   property_name VARCHAR(100) NOT NULL,
>   property_value VARCHAR(2048),
>   CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, 
> property_name));
> {code}
> property_value as 2048 but i am having certificate length 2050 and ambari is 
> not accepting it.
> this should be fixed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-25003) Starting JPA persistence service sometimes throws IllegalStateException

2018-12-05 Thread Robert Levas (JIRA)

Robert Levas created AMBARI-25003:
-

 Summary: Starting JPA persistence service sometimes throws 
IllegalStateException
 Key: AMBARI-25003
 URL: https://issues.apache.org/jira/browse/AMBARI-25003
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.8.0
Reporter: Robert Levas
Assignee: Robert Levas
 Fix For: 2.8.0


Starting JPA persistence service sometimes throws IllegalStateException.  

For example:
{noformat}
Exception in thread "main" java.lang.IllegalStateException: Persistence service 
was already initialized.
at 
com.google.common.base.Preconditions.checkState(Preconditions.java:173)
at 
com.google.inject.persist.jpa.JpaPersistService.start(JpaPersistService.java:104)
at 
com.google.inject.persist.jpa.AmbariJpaPersistService.start(AmbariJpaPersistService.java:27)
at 
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24992) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate

2018-12-05 Thread Hudson (JIRA)



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

Hudson commented on AMBARI-24992:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10361 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/10361/])
AMBARI-24992. Updated ambari_configuration.property_value to support (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=129632c94aa339571d0fa278a2259157b5244fcb])
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog280.java
* (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-MySQL-CREATE.sql
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog280Test.java


> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to 
> long certificate 
> -
>
> Key: AMBARI-24992
> URL: https://issues.apache.org/jira/browse/AMBARI-24992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Sandor Molnar
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> I am trying to upgrade to ambari-2.7.0 using  command : *ambari-server 
> upgrade*
> the upgrade operation is failing on Schema upgrade phase
> The exception is : 
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO 
> ambari_configuration (property_name, category_name, property_value) VALUES 
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)  
> Call getNextException to see other errors in the batch.
> {code}
> and i see as per 
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L125
> ambari is having : 
> {code:java}
> CREATE TABLE ambari_configuration (
>   category_name VARCHAR(100) NOT NULL,
>   property_name VARCHAR(100) NOT NULL,
>   property_value VARCHAR(2048),
>   CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, 
> property_name));
> {code}
> property_value as 2048 but i am having certificate length 2050 and ambari is 
> not accepting it.
> this should be fixed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25002) Allow Stack To Define Custom Rolling Orchestration Logic

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot updated AMBARI-25002:

Labels: pull-request-available  (was: )

> Allow Stack To Define Custom Rolling Orchestration Logic
> 
>
> Key: AMBARI-25002
> URL: https://issues.apache.org/jira/browse/AMBARI-25002
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server, ambari-server-spi
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>
> Use the SPI to allow stacks to provide their own code-based logic classes.  
> The first iteration will allow a stack to compute how many slave components 
> can run at the same time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-25002) Allow Stack To Define Custom Rolling Orchestration Logic

2018-12-05 Thread Nate Cole (JIRA)

Nate Cole created AMBARI-25002:
--

 Summary: Allow Stack To Define Custom Rolling Orchestration Logic
 Key: AMBARI-25002
 URL: https://issues.apache.org/jira/browse/AMBARI-25002
 Project: Ambari
  Issue Type: Task
  Components: ambari-server, ambari-server-spi
Reporter: Nate Cole
Assignee: Nate Cole
 Fix For: 2.8.0


Use the SPI to allow stacks to provide their own code-based logic classes.  The 
first iteration will allow a stack to compute how many slave components can run 
at the same time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24999) Disallow changing Kerberos-related configs in Add Service request

2018-12-05 Thread Doroszlai, Attila (JIRA)



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

Doroszlai, Attila resolved AMBARI-24999.

Resolution: Implemented

> Disallow changing Kerberos-related configs in Add Service request
> -
>
> Key: AMBARI-24999
> URL: https://issues.apache.org/jira/browse/AMBARI-24999
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Ambari should not allow a user to set configurations in the {{kerberos-env}} 
> and {{krb5-conf}} configuration types within the complex Add Service request. 
>  Generally, setting these configurations on an existing Kerberized cluster 
> could be problematic, since existing services already depend upon the 
> existing configuration to interact with the KDC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24988) Support provision_action in complex Add Service request

2018-12-05 Thread Doroszlai, Attila (JIRA)



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

Doroszlai, Attila resolved AMBARI-24988.

Resolution: Implemented

> Support provision_action in complex Add Service request
> ---
>
> Key: AMBARI-24988
> URL: https://issues.apache.org/jira/browse/AMBARI-24988
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Support {{provision_action}} in complex Add Service request, similarly to 
> blueprints.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24999) Disallow changing Kerberos-related configs in Add Service request

2018-12-05 Thread Hudson (JIRA)



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

Hudson commented on AMBARI-24999:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10360 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/10360/])
AMBARI-24999. Disallow changing Kerberos-related configs in Add Service 
(github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e70dd4e7434bc3828629d329684a12b574dfd9d3])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/addservice/RequestValidator.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/addservice/RequestValidatorTest.java


> Disallow changing Kerberos-related configs in Add Service request
> -
>
> Key: AMBARI-24999
> URL: https://issues.apache.org/jira/browse/AMBARI-24999
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Ambari should not allow a user to set configurations in the {{kerberos-env}} 
> and {{krb5-conf}} configuration types within the complex Add Service request. 
>  Generally, setting these configurations on an existing Kerberized cluster 
> could be problematic, since existing services already depend upon the 
> existing configuration to interact with the KDC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24988) Support provision_action in complex Add Service request

2018-12-05 Thread Hudson (JIRA)



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

Hudson commented on AMBARI-24988:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10359 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/10359/])
AMBARI-24988. Support provision_action in complex Add Service request (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=b268518b25ee9f78d00926b27516a773ea58967c])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/addservice/AddServiceOrchestrator.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/addservice/ResourceProviderAdapter.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ProvisionAction.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java


> Support provision_action in complex Add Service request
> ---
>
> Key: AMBARI-24988
> URL: https://issues.apache.org/jira/browse/AMBARI-24988
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Support {{provision_action}} in complex Add Service request, similarly to 
> blueprints.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread Hudson (JIRA)



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

Hudson commented on AMBARI-23456:
-

SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #68 (See 
[https://builds.apache.org/job/Ambari-LogSearch-master-Commit/68/])
AMBARI-23456. Add mkdocs support & markdown skeletons (#54) (github: 
[https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git&a=commit&h=6ff4dc21dd428bd57afd2bc95ba7c2ab4f6a7f8c])
* (edit) 
ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/InputConfigImpl.java
* (edit) ambari-logsearch-server/pom.xml
* (add) docs/docs.md
* (edit) pom.xml
* (add) ambari-logsearch-docs/src/main/resources/docs.md
* (add) docs/add_new_input.md
* (edit) 
ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/ConditionsImpl.java
* (edit) ambari-logsearch-docs/pom.xml
* (edit) 
ambari-logsearch-docs/src/main/java/org/apache/ambari/logsearch/doc/ShipperConfigDescriptionDataHolder.java
* (edit) 
ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
* (add) docs/getting_started.md
* (add) 
ambari-logsearch-docs/src/main/java/org/apache/ambari/logsearch/doc/LogSearchDocumentationGenerator.java
* (edit) 
ambari-logsearch-logfeeder-plugin-api/src/main/java/org/apache/ambari/logfeeder/plugin/output/Output.java
* (edit) 
ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/FieldsImpl.java
* (add) docs/index.md
* (add) docs/api-docs/logsearch-swagger.yaml
* (add) docs/schema_fields.md
* (edit) 
ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java
* (delete) docs/.keep
* (add) docs/about.md
* (delete) 
ambari-logsearch-docs/src/main/java/org/apache/ambari/logsearch/doc/LogSearchMarkdownGenerator.java
* (add) docs/logfeeder_properties.md
* (edit) 
ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/InputS3FileDescriptorImpl.java
* (edit) 
ambari-logsearch-docs/src/main/resources/templates/shipper_configurations.md.ftl
* (edit) .gitignore
* (edit) Makefile
* (add) mkdocs.yml
* (edit) 
ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/FilterGrokDescriptorImpl.java
* (add) docs/logsearch_properties.md
* (add) docs/shipper_configurations.md
* (add) docs/cloud_mode.md


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-23820) [Log Search UI] add different options of hostname display

2018-12-05 Thread Istvan Tobias (JIRA)



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

Istvan Tobias updated AMBARI-23820:
---
Status: Patch Available  (was: Open)

> [Log Search UI] add different options of hostname display
> -
>
> Key: AMBARI-23820
> URL: https://issues.apache.org/jira/browse/AMBARI-23820
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>   Original Estimate: 48h
>  Time Spent: 48h
>  Remaining Estimate: 0h
>
> Provide a setting to show FQDN or short hostname:
> FQDN: logsearch-demo-1.c.pramod-thangali.internal
> Short Hostname: logsearch-demo-1
> If shortname is preferred then show: FQDN.split(“.”)[0]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

asfgit commented on issue #54: AMBARI-23456. Add mkdocs support & markdown 
skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#issuecomment-444502771
 
 
   
   Refer to this link for build results (access rights to CI server needed): 
   https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/112/
   Test PASSed.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24992) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot updated AMBARI-24992:

Labels: pull-request-available  (was: )

> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to 
> long certificate 
> -
>
> Key: AMBARI-24992
> URL: https://issues.apache.org/jira/browse/AMBARI-24992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Sandor Molnar
>Priority: Major
>  Labels: pull-request-available
>
> I am trying to upgrade to ambari-2.7.0 using  command : *ambari-server 
> upgrade*
> the upgrade operation is failing on Schema upgrade phase
> The exception is : 
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO 
> ambari_configuration (property_name, category_name, property_value) VALUES 
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)  
> Call getNextException to see other errors in the batch.
> {code}
> and i see as per 
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L125
> ambari is having : 
> {code:java}
> CREATE TABLE ambari_configuration (
>   category_name VARCHAR(100) NOT NULL,
>   property_name VARCHAR(100) NOT NULL,
>   property_value VARCHAR(2048),
>   CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, 
> property_name));
> {code}
> property_value as 2048 but i am having certificate length 2050 and ambari is 
> not accepting it.
> this should be fixed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

asfgit commented on issue #54: AMBARI-23456. Add mkdocs support & markdown 
skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#issuecomment-95424
 
 
   
   Refer to this link for build results (access rights to CI server needed): 
   https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/111/
   Test PASSed.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

asfgit commented on issue #54: AMBARI-23456. Add mkdocs support & markdown 
skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#issuecomment-92508
 
 
   
   Refer to this link for build results (access rights to CI server needed): 
   https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/110/
   Test PASSed.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

asfgit commented on issue #54: AMBARI-23456. Add mkdocs support & markdown 
skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#issuecomment-91157
 
 
   
   Refer to this link for build results (access rights to CI server needed): 
   https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/109/
   Test PASSed.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

oleewere commented on a change in pull request #54: AMBARI-23456. Add mkdocs 
support & markdown skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#discussion_r239068143
 
 

 ##
 File path: 
ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/InputConfigImpl.java
 ##
 @@ -39,15 +39,17 @@
   @ShipperConfigElementDescription(
 path = "/input",
 type = "list of json objects",
-description = "A list of input descriptions"
+description = "A list of input descriptions",
+examples = {"{\"input\" : [ {\"type\": \"myinput_service_type\"}] }"}
 
 Review comment:
   @kasakrisz ok, could be


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

kasakrisz commented on a change in pull request #54: AMBARI-23456. Add mkdocs 
support & markdown skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#discussion_r239064714
 
 

 ##
 File path: 
ambari-logsearch-docs/src/main/java/org/apache/ambari/logsearch/doc/LogSearchDocumentationGenerator.java
 ##
 @@ -130,12 +140,32 @@ public static void main(String[] args) {
   File shipperConfigsOutputFile = Paths.get(outputDir, 
SHIPPER_CONFIGURATIONS_MARKDOWN_OUTPUT).toFile();
   writeMarkdown(freemarkerConfiguration, 
SHIPPER_CONFIGURATIONS_MARKDOWN_TEMPLATE_FILE, shipperConfigModels, 
shipperConfigsOutputFile);
 
+  String swaggerYaml = generateSwaggerYaml();
+  File swaggerYamlFile = Paths.get(outputDir, SWAGGER_API_DOC_FOLDER, 
SWAGGER_YAML_FILE_NAME).toFile();
+  FileUtils.writeStringToFile(swaggerYamlFile, swaggerYaml, 
Charset.defaultCharset());
 } catch (Exception e) {
   e.printStackTrace();
   System.exit(1);
 }
   }
 
+  private static String generateSwaggerYaml() throws Exception {
+ApiDocConfig apiDocConfig = new ApiDocConfig();
+BeanConfig beanConfig = apiDocConfig.swaggerConfig();
+Swagger swagger = beanConfig.getSwagger();
+swagger.addSecurityDefinition("basicAuth", new BasicAuthDefinition());
+beanConfig.configure(swagger);
+beanConfig.scanAndRead();
+String yaml = Yaml.mapper().writeValueAsString(swagger);
+StringBuilder b = new StringBuilder();
+String[] parts = yaml.split("\n");
+for (String part : parts) {
+  b.append(part);
+  b.append("\n");
+}
+return b.toString();
 
 Review comment:
   What is the difference between the result of `b.toString()` and `yaml` ?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

kasakrisz commented on a change in pull request #54: AMBARI-23456. Add mkdocs 
support & markdown skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#discussion_r239059077
 
 

 ##
 File path: 
ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/InputConfigImpl.java
 ##
 @@ -39,15 +39,17 @@
   @ShipperConfigElementDescription(
 path = "/input",
 type = "list of json objects",
-description = "A list of input descriptions"
+description = "A list of input descriptions",
+examples = {"{\"input\" : [ {\"type\": \"myinput_service_type\"}] }"}
 
 Review comment:
   What do you think? Would adding the following is helpful:
   ```
   where myinput_service_type is like ambari_server, hdfs_namenode etc...
   ```


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

kasakrisz commented on a change in pull request #54: AMBARI-23456. Add mkdocs 
support & markdown skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#discussion_r239062724
 
 

 ##
 File path: 
ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/InputS3FileDescriptorImpl.java
 ##
 @@ -34,7 +34,7 @@
   @ShipperConfigElementDescription(
 path = "/input/[]/s3_access_key",
 type = "string",
-description = "The access key used for AWS credentials."
+description = "The access key used for AWS credentials. (Not supported yet 
through shipper configurations)"
 
 Review comment:
   Is it possible to omit these not supported properties from the doc? I think 
these should only be included if the functionality is supported.
   lines: 37, 46, 55 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

kasakrisz commented on a change in pull request #54: AMBARI-23456. Add mkdocs 
support & markdown skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#discussion_r239066254
 
 

 ##
 File path: 
ambari-logsearch-docs/src/main/resources/templates/shipper_configurations.md.ftl
 ##
 @@ -17,19 +17,117 @@ limitations under the License.
 
 ## Log Feeder Shipper Descriptor
 
-### Top Level Descriptor Sections
+### Top Level Descriptors
 
+Input, Filter and Output configurations are defined in 3 (at least) different 
files. (note: there can be multiple input configuration files, but only 1 
output and global configuration)
+
+input.config-myservice.json example:
+```json
+{
+  "input" : [
+  ],
+  "filter" : [
+  ]
+}
+```
+output.config.json example:
+```json
+{
+  "output" : [
+  ]
+}
+```
+global.config.json example:
+```json
+{
+  "global" : {
+"source" : "file",
+"add_fields":{
+  "cluster":"cl1"
+},
+"tail" : "true"
+  }
+}
+```
 | `Path` | `Description` | `Default` | `Examples` |
 |---|---|---|---|
-<#if shipperConfigs.topLevelSections??>
-<#list shipperConfigs.topLevelSections as section>
+<#if shipperConfigs.topLevelConfigSections??>
+<#list shipperConfigs.topLevelConfigSections as section>
 
|`${section.path}`|${section.description}|${section.defaultValue}|${section.examples}|
 
 
-|`/output`|A list of output descriptors|`{}`||
+|`/output`|A list of output descriptors|`{}`|`{"output": 
[{"is_enabled" : "true", "destination": "solr", "myfield": 
"myvalue"}]`|
+|`/global`|A map that contains field/value pairs|`EMPTY`|`{"global": 
{"myfield": "myvalue"}}`|
 
-### Input Descriptor Sections
+### Input Descriptor
 
+Input configurations (for monitoring logs) can be defined in the input 
descriptor section.
+Example:
+```json
+{
+  "input" : [
+{
+  "type": "simple_service",
+  "rowtype": "service",
+  "path": "/var/logs/my/service/service_sample.txt",
 
 Review comment:
   Maybe `service_sample.log` would be more useful.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

kasakrisz commented on a change in pull request #54: AMBARI-23456. Add mkdocs 
support & markdown skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#discussion_r239066570
 
 

 ##
 File path: 
ambari-logsearch-docs/src/main/resources/templates/shipper_configurations.md.ftl
 ##
 @@ -38,8 +136,97 @@ limitations under the License.
 
 
 
-### Filter Descriptor Sections
+### Filter Descriptor
 
+Filter configurations can be defined in the filter descriptor section.
+Example:
+```json
+{
+  "input" : [
+  ],
+  "filter": [
+{
+  "filter": "json",
+  "conditions": {
+"fields": {
+  "type": [
+"simple_service_json"
+  ]
+}
+  }
+}
+{
+  "filter": "grok",
+  "deep_extract": "false",
+  "conditions":{
+"fields":{
+  "type":[
+"simple_service",
+"simple_audit_service",
+"docker_service"
+  ]
+}
+  },
+  "log4j_format":"%d{ISO8601} %5p [%t] %c{1}:%L - %m%n",
+  "multiline_pattern":"^(%{TIMESTAMP_ISO8601:logtime})",
+  
"message_pattern":"(?m)^%{TIMESTAMP_ISO8601:logtime}%{SPACE}%{LOGLEVEL:level}%{SPACE}\\[%{DATA:thread_name}\\]%{SPACE}%{JAVACLASS:logger_name}:%{INT:line_number}%{SPACE}-%{SPACE}%{GREEDYDATA:log_message}",
 
 Review comment:
   Including some lines of sample log can be useful to understand what log 
entries can be parsed with this pattern.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

kasakrisz commented on a change in pull request #54: AMBARI-23456. Add mkdocs 
support & markdown skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#discussion_r239061724
 
 

 ##
 File path: 
ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/InputConfigImpl.java
 ##
 @@ -39,15 +39,17 @@
   @ShipperConfigElementDescription(
 path = "/input",
 type = "list of json objects",
-description = "A list of input descriptions"
+description = "A list of input descriptions",
+examples = {"{\"input\" : [ {\"type\": \"myinput_service_type\"}] }"}
   )
   @Expose
   private List input;
 
   @ShipperConfigElementDescription(
 path = "/filter",
 type = "list of json objects",
-description = "A list of filter descriptions"
+description = "A list of filter descriptions",
+examples = {"{\"filter\" : [ {\"filter\": \"json\", \"conditions\": 
{\"fields\": { \"type\": [\"mytype1\", \"mytype2\"]} } } ]}"}
 
 Review comment:
   Same as above (line 43). Giving a concrete example could be useful.
   ```
 "filter":[
   {
 "filter":"json",
 "conditions":{
   "fields":{
 "type":[
   "logsearch_app",
   "logsearch_feeder",
   "logsearch_perf"
 ]
   }
 }
   }
 ]
   
   ```


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-22442) Log Search GA

2018-12-05 Thread JIRA



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

Olivér Szabó updated AMBARI-22442:
--
Affects Version/s: (was: 3.0.0)
   2.8.0

> Log Search GA
> -
>
> Key: AMBARI-22442
> URL: https://issues.apache.org/jira/browse/AMBARI-22442
> Project: Ambari
>  Issue Type: Epic
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24826) Log Search: add kerberos docker env for development

2018-12-05 Thread JIRA



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

Olivér Szabó resolved AMBARI-24826.
---
Resolution: Won't Do

> Log Search: add kerberos docker env for development
> ---
>
> Key: AMBARI-24826
> URL: https://issues.apache.org/jira/browse/AMBARI-24826
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24999) Disallow changing Kerberos-related configs in Add Service request

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot updated AMBARI-24999:

Labels: pull-request-available  (was: )

> Disallow changing Kerberos-related configs in Add Service request
> -
>
> Key: AMBARI-24999
> URL: https://issues.apache.org/jira/browse/AMBARI-24999
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>
> Ambari should not allow a user to set configurations in the {{kerberos-env}} 
> and {{krb5-conf}} configuration types within the complex Add Service request. 
>  Generally, setting these configurations on an existing Kerberized cluster 
> could be problematic, since existing services already depend upon the 
> existing configuration to interact with the KDC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-22442) Log Search GA

2018-12-05 Thread JIRA



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

Olivér Szabó updated AMBARI-22442:
--
Fix Version/s: (was: 3.0.0)
   2.8.0

> Log Search GA
> -
>
> Key: AMBARI-22442
> URL: https://issues.apache.org/jira/browse/AMBARI-22442
> Project: Ambari
>  Issue Type: Epic
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-25001) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate

2018-12-05 Thread Sandor Molnar (JIRA)



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

Sandor Molnar resolved AMBARI-25001.

Resolution: Duplicate

> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to 
> long certificate
> 
>
> Key: AMBARI-25001
> URL: https://issues.apache.org/jira/browse/AMBARI-25001
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Fix For: 2.8.0
>
>
> During the upgrade process to AMBARI 2.7.0 the upgrade operation is failing 
> on Schema upgrade phase due to the following error:
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO 
> ambari_configuration (property_name, category_name, property_value) VALUES 
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)
> {code}
> Ambari is having the following DDL for {{ambari_configuration}}:
> {code:java}
> CREATE TABLE ambari_configuration (
>   category_name VARCHAR(100) NOT NULL,
>   property_name VARCHAR(100) NOT NULL,
>   property_value VARCHAR(2048),
>   CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, 
> property_name));
> {code}
> {{property_value}} is set to maximum of 2048 bytes/chars which is obviously 
> not enough in some cases.
> Checking the currently supported DBs we may set this column to 4000 (except 
> for Postgres where the recommended type is {{text}})



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-25001) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate

2018-12-05 Thread Sandor Molnar (JIRA)



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

Sandor Molnar commented on AMBARI-25001:


Additional information about the storage requirements for all kind of DBs that 
are currently supported :
Oracle
 - 12c : 4000 
([https://docs.oracle.com/database/121/SQLRF/sql_elements001.htm#SQLRF0021])
 - 11gr2 : 4000 
([https://docs.oracle.com/cd/E11882_01/server.112/e41084/sql_elements001.htm#SQLRF30020])

Postgres
 - 10.2 : 1 GB 
([https://www.postgresql.org/docs/10/datatype-character.html#DATATYPE-CHARACTER-TABLE]);
 depends on encoding; recommended is to use 'text' as type (see 
{{clusterconfig.config_data}})
 - 9.6 : 1 GB 
([https://www.postgresql.org/docs/9.6/datatype-character.html#DATATYPE-CHARACTER-TABLE]);
 depends on encoding; recommended is to use 'text' as type (see 
{{clusterconfig.config_data}})

MySQL (InnoDB only)
 - 5.7 : 65,535 
([https://dev.mysql.com/doc/refman/5.7/en/storage-requirements.html#data-types-storage-reqs-innodb])

MariaDB
 - 10.2 : 65,535 ([https://mariadb.com/kb/en/library/varchar/])

> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to 
> long certificate
> 
>
> Key: AMBARI-25001
> URL: https://issues.apache.org/jira/browse/AMBARI-25001
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Fix For: 2.8.0
>
>
> During the upgrade process to AMBARI 2.7.0 the upgrade operation is failing 
> on Schema upgrade phase due to the following error:
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO 
> ambari_configuration (property_name, category_name, property_value) VALUES 
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)
> {code}
> Ambari is having the following DDL for {{ambari_configuration}}:
> {code:java}
> CREATE TABLE ambari_configuration (
>   category_name VARCHAR(100) NOT NULL,
>   property_name VARCHAR(100) NOT NULL,
>   property_value VARCHAR(2048),
>   CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, 
> property_name));
> {code}
> {{property_value}} is set to maximum of 2048 bytes/chars which is obviously 
> not enough in some cases.
> Checking the currently supported DBs we may set this column to 4000 (except 
> for Postgres where the recommended type is {{text}})



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (AMBARI-24992) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate

2018-12-05 Thread Sandor Molnar (JIRA)



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

Sandor Molnar reassigned AMBARI-24992:
--

Assignee: Sandor Molnar  (was: Robert Levas)

> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to 
> long certificate 
> -
>
> Key: AMBARI-24992
> URL: https://issues.apache.org/jira/browse/AMBARI-24992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Sandor Molnar
>Priority: Major
>
> I am trying to upgrade to ambari-2.7.0 using  command : *ambari-server 
> upgrade*
> the upgrade operation is failing on Schema upgrade phase
> The exception is : 
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO 
> ambari_configuration (property_name, category_name, property_value) VALUES 
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)  
> Call getNextException to see other errors in the batch.
> {code}
> and i see as per 
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L125
> ambari is having : 
> {code:java}
> CREATE TABLE ambari_configuration (
>   category_name VARCHAR(100) NOT NULL,
>   property_name VARCHAR(100) NOT NULL,
>   property_value VARCHAR(2048),
>   CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, 
> property_name));
> {code}
> property_value as 2048 but i am having certificate length 2050 and ambari is 
> not accepting it.
> this should be fixed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-25001) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate

2018-12-05 Thread Sandor Molnar (JIRA)

Sandor Molnar created AMBARI-25001:
--

 Summary: Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema 
upgrade phase due to long certificate
 Key: AMBARI-25001
 URL: https://issues.apache.org/jira/browse/AMBARI-25001
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
 Fix For: 2.8.0


During the upgrade process to AMBARI 2.7.0 the upgrade operation is failing on 
Schema upgrade phase due to the following error:
{code:java}
Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO 
ambari_configuration (property_name, category_name, property_value) VALUES 
('ambari.sso.provider.certificate','sso-configuration',') was aborted: ERROR: value too long for type character varying(2048)
{code}
Ambari is having the following DDL for {{ambari_configuration}}:
{code:java}
CREATE TABLE ambari_configuration (
  category_name VARCHAR(100) NOT NULL,
  property_name VARCHAR(100) NOT NULL,
  property_value VARCHAR(2048),
  CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, 
property_name));
{code}
{{property_value}} is set to maximum of 2048 bytes/chars which is obviously not 
enough in some cases.

Checking the currently supported DBs we may set this column to 4000 (except for 
Postgres where the recommended type is {{text}})



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24998) Not supported actions(like Start/Stop) should not be shown for HDFS/YARN clients in WL cluster with externalized HDFS/YARN

2018-12-05 Thread Hudson (JIRA)



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

Hudson commented on AMBARI-24998:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10358 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/10358/])
AMBARI-24998 Not supported actions(like Start/Stop) should not be shown 
(atkach: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f4be4bb1e573c2a8376fa2aa9a17d340d906b99d])
* (edit) ambari-web/app/views/main/service/item.js
* (edit) ambari-web/test/views/main/service/item_test.js
* (edit) ambari-web/app/views/main/service/services/yarn.js


> Not supported actions(like Start/Stop) should not be shown for HDFS/YARN 
> clients in WL cluster with externalized HDFS/YARN
> --
>
> Key: AMBARI-24998
> URL: https://issues.apache.org/jira/browse/AMBARI-24998
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Start/Stop operations should not be shown/should be disabled for HDFS/YARN 
> clients.
> But as of Ambari 2.7, they are visible in Service actions. 
> Also there are multiple other actions which are currently enabled and are not 
> applicable for the clients(listed below). These should be masked in the UI 
> and not be shown to the user. Please clarify , if there is any discrepancy in 
> understanding.
> *HDFS Client :*
> Manage Journal Nodes
> Add new HDFS Namespace
> Rebalance HDFS
> restart all
> *YARN Client:*
> Refresh YARN Capacity Scheduler.
> Enable resourceManager HA
> restart All



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

asfgit commented on issue #54: AMBARI-23456. Add mkdocs support & markdown 
skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#issuecomment-61394
 
 
   
   Refer to this link for build results (access rights to CI server needed): 
   https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/107/
   Test FAILed.
   Test FAILured.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24998) Not supported actions(like Start/Stop) should not be shown for HDFS/YARN clients in WL cluster with externalized HDFS/YARN

2018-12-05 Thread Andrii Tkach (JIRA)



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

Andrii Tkach resolved AMBARI-24998.
---
Resolution: Fixed

> Not supported actions(like Start/Stop) should not be shown for HDFS/YARN 
> clients in WL cluster with externalized HDFS/YARN
> --
>
> Key: AMBARI-24998
> URL: https://issues.apache.org/jira/browse/AMBARI-24998
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Start/Stop operations should not be shown/should be disabled for HDFS/YARN 
> clients.
> But as of Ambari 2.7, they are visible in Service actions. 
> Also there are multiple other actions which are currently enabled and are not 
> applicable for the clients(listed below). These should be masked in the UI 
> and not be shown to the user. Please clarify , if there is any discrepancy in 
> understanding.
> *HDFS Client :*
> Manage Journal Nodes
> Add new HDFS Namespace
> Rebalance HDFS
> restart all
> *YARN Client:*
> Refresh YARN Capacity Scheduler.
> Enable resourceManager HA
> restart All



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

asfgit commented on issue #54: AMBARI-23456. Add mkdocs support & markdown 
skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#issuecomment-63348
 
 
   
   Refer to this link for build results (access rights to CI server needed): 
   https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/108/
   Test PASSed.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24998) Not supported actions(like Start/Stop) should not be shown for HDFS/YARN clients in WL cluster with externalized HDFS/YARN

2018-12-05 Thread Andrii Tkach (JIRA)



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

Andrii Tkach commented on AMBARI-24998:
---

committed to trunk

> Not supported actions(like Start/Stop) should not be shown for HDFS/YARN 
> clients in WL cluster with externalized HDFS/YARN
> --
>
> Key: AMBARI-24998
> URL: https://issues.apache.org/jira/browse/AMBARI-24998
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Start/Stop operations should not be shown/should be disabled for HDFS/YARN 
> clients.
> But as of Ambari 2.7, they are visible in Service actions. 
> Also there are multiple other actions which are currently enabled and are not 
> applicable for the clients(listed below). These should be masked in the UI 
> and not be shown to the user. Please clarify , if there is any discrepancy in 
> understanding.
> *HDFS Client :*
> Manage Journal Nodes
> Add new HDFS Namespace
> Rebalance HDFS
> restart all
> *YARN Client:*
> Refresh YARN Capacity Scheduler.
> Enable resourceManager HA
> restart All



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

asfgit commented on issue #54: AMBARI-23456. Add mkdocs support & markdown 
skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54#issuecomment-60373
 
 
   
   Refer to this link for build results (access rights to CI server needed): 
   https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/106/
   Test PASSed.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-23456:
-

oleewere opened a new pull request #54: AMBARI-23456. Add mkdocs support & 
markdown skeletons
URL: https://github.com/apache/ambari-logsearch/pull/54
 
 
   # What changes were proposed in this pull request?
   - fix some docs
   - generate output shipper configs as well
   - add mkdocs support
   - put javadoc + rest api doc as well to generated site
   - add markdown skeletons (i will need to fill those + add nice pictures)
   
   note: probably we will use docker for mkdocs build, right now it is expected 
to be installed
   
   ## How was this patch tested?
   full test: `make serve-site`, it can take long because of 2 web build, if 
modules are already installed then its enough to run: `make javadoc`, `make 
prop-docs-only` then `make serve-site-only`
   
   Please review @g-boros 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Log Search: generate mardown docs for properties and logfeeder configs based 
> on annotations
> ---
>
> Key: AMBARI-23456
> URL: https://issues.apache.org/jira/browse/AMBARI-23456
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24999) Disallow changing Kerberos-related configs in Add Service request

2018-12-05 Thread Doroszlai, Attila (JIRA)

Doroszlai, Attila created AMBARI-24999:
--

 Summary: Disallow changing Kerberos-related configs in Add Service 
request
 Key: AMBARI-24999
 URL: https://issues.apache.org/jira/browse/AMBARI-24999
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.8.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
 Fix For: 2.8.0


Ambari should not allow a user to set configurations in the {{kerberos-env}} 
and {{krb5-conf}} configuration types within the complex Add Service request.  
Generally, setting these configurations on an existing Kerberized cluster could 
be problematic, since existing services already depend upon the existing 
configuration to interact with the KDC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-25000) START_ONLY provision action may be applied to the wrong component

2018-12-05 Thread Doroszlai, Attila (JIRA)

Doroszlai, Attila created AMBARI-25000:
--

 Summary: START_ONLY provision action may be applied to the wrong 
component
 Key: AMBARI-25000
 URL: https://issues.apache.org/jira/browse/AMBARI-25000
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
 Fix For: 2.8.0


If component XY is provisioned with {{START_ONLY}}, and component X is a prefix 
of XY, then the provision action is applied to both X and XY.

{noformat:title=blueprint}
{
  "host_groups": [
{
  "components": [
{ "name": "HIVE_SERVER" },
{ "name": "HIVE_SERVER_INTERACTIVE", "provision_action": "START_ONLY" },
...
{noformat}

{noformat:title=ambari-server.log}
AmbariManagementControllerImpl:3149 - Skipping create of INSTALL task for 
HIVE_SERVER on c7401.ambari.apache.org.
AmbariManagementControllerImpl:3149 - Skipping create of INSTALL task for 
HIVE_SERVER_INTERACTIVE on c7401.ambari.apache.org.
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24998) Not supported actions(like Start/Stop) should not be shown for HDFS/YARN clients in WL cluster with externalized HDFS/YARN

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot updated AMBARI-24998:

Labels: pull-request-available  (was: )

> Not supported actions(like Start/Stop) should not be shown for HDFS/YARN 
> clients in WL cluster with externalized HDFS/YARN
> --
>
> Key: AMBARI-24998
> URL: https://issues.apache.org/jira/browse/AMBARI-24998
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>
> Start/Stop operations should not be shown/should be disabled for HDFS/YARN 
> clients.
> But as of Ambari 2.7, they are visible in Service actions. 
> Also there are multiple other actions which are currently enabled and are not 
> applicable for the clients(listed below). These should be masked in the UI 
> and not be shown to the user. Please clarify , if there is any discrepancy in 
> understanding.
> *HDFS Client :*
> Manage Journal Nodes
> Add new HDFS Namespace
> Rebalance HDFS
> restart all
> *YARN Client:*
> Refresh YARN Capacity Scheduler.
> Enable resourceManager HA
> restart All



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-24998) Not supported actions(like Start/Stop) should not be shown for HDFS/YARN clients in WL cluster with externalized HDFS/YARN

2018-12-05 Thread Andrii Tkach (JIRA)

Andrii Tkach created AMBARI-24998:
-

 Summary: Not supported actions(like Start/Stop) should not be 
shown for HDFS/YARN clients in WL cluster with externalized HDFS/YARN
 Key: AMBARI-24998
 URL: https://issues.apache.org/jira/browse/AMBARI-24998
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.7.3
Reporter: Andrii Tkach
Assignee: Andrii Tkach
 Fix For: 2.8.0


Start/Stop operations should not be shown/should be disabled for HDFS/YARN 
clients.
But as of Ambari 2.7, they are visible in Service actions. 

Also there are multiple other actions which are currently enabled and are not 
applicable for the clients(listed below). These should be masked in the UI and 
not be shown to the user. Please clarify , if there is any discrepancy in 
understanding.

*HDFS Client :*
Manage Journal Nodes
Add new HDFS Namespace
Rebalance HDFS
restart all

*YARN Client:*
Refresh YARN Capacity Scheduler.
Enable resourceManager HA
restart All



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24988) Support provision_action in complex Add Service request

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot updated AMBARI-24988:

Labels: pull-request-available  (was: )

> Support provision_action in complex Add Service request
> ---
>
> Key: AMBARI-24988
> URL: https://issues.apache.org/jira/browse/AMBARI-24988
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>
> Support {{provision_action}} in complex Add Service request, similarly to 
> blueprints.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24997) When the custom service does not have the configure directory, add service in step 4 failed

2018-12-05 Thread xiaosonglin (JIRA)



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

xiaosonglin commented on AMBARI-24997:
--

PR URL:[https://github.com/apache/ambari/pull/2690]

 

> When the custom service does not have the configure directory, add service in 
>  step 4 failed
> 
>
> Key: AMBARI-24997
> URL: https://issues.apache.org/jira/browse/AMBARI-24997
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: !image-2018-12-05-15-49-18-977.png!
>Reporter: xiaosonglin
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: image-2018-12-05-15-45-39-307.png, 
> image-2018-12-05-15-49-18-977.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> review ambari code ,custom service must have configuration directory,  I 
> don't need a configuration directory
> !image-2018-12-05-15-45-39-307.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24987) Infra Manager: parse logs by Logsearch

2018-12-05 Thread Hudson (JIRA)



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

Hudson commented on AMBARI-24987:
-

SUCCESS: Integrated in Jenkins build Ambari-Infra-master-Commit #28 (See 
[https://builds.apache.org/job/Ambari-Infra-master-Commit/28/])
AMBARI-24987 - Infra Manager: parse logs by Logsearch (#23) (oleewere: 
[https://gitbox.apache.org/repos/asf?p=ambari-infra.git&a=commit&h=65a45ca2471f4261f333642399c8a3d64c2adbf7])
* (edit) ambari-infra-manager/src/main/resources/log4j2.xml
* (edit) ambari-infra-manager/pom.xml
* (edit) pom.xml


> Infra Manager: parse logs by Logsearch
> --
>
> Key: AMBARI-24987
> URL: https://issues.apache.org/jira/browse/AMBARI-24987
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-infra, ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24987) Infra Manager: parse logs by Logsearch

2018-12-05 Thread ASF GitHub Bot (JIRA)



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

ASF GitHub Bot commented on AMBARI-24987:
-

oleewere closed pull request #23: AMBARI-24987 - Infra Manager: parse logs by 
Logsearch
URL: https://github.com/apache/ambari-infra/pull/23
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/ambari-infra-manager/pom.xml b/ambari-infra-manager/pom.xml
index 419ccd57..80dddb1f 100644
--- a/ambari-infra-manager/pom.xml
+++ b/ambari-infra-manager/pom.xml
@@ -363,6 +363,10 @@
   org.slf4j
   slf4j-log4j12
 
+
+  log4j
+  log4j
+
 
   org.eclipse.jetty
   jetty-server
@@ -571,6 +575,17 @@
   2.3.1
 
 
+
+  org.apache.logging.log4j
+  log4j-web
+  ${log4j2.version}
+
+
+  org.apache.logging.log4j
+  log4j-1.2-api
+  ${log4j2.version}
+
+
   
 
 
diff --git a/ambari-infra-manager/src/main/resources/log4j2.xml 
b/ambari-infra-manager/src/main/resources/log4j2.xml
index d3db3d7e..80819c89 100644
--- a/ambari-infra-manager/src/main/resources/log4j2.xml
+++ b/ambari-infra-manager/src/main/resources/log4j2.xml
@@ -24,7 +24,7 @@
   
 
 
-  
+  
   
 
 
diff --git a/pom.xml b/pom.xml
index af47dc8f..80c4877b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -36,6 +36,7 @@
 3.4.6.2.3.0.0-2557
 2.7.0.0.0
 false
+2.10.0
   
 
   


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Infra Manager: parse logs by Logsearch
> --
>
> Key: AMBARI-24987
> URL: https://issues.apache.org/jira/browse/AMBARI-24987
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-infra, ambari-logsearch
>Affects Versions: 2.8.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24997) When the custom service does not have the configure directory, add service in step 4 failed

2018-12-05 Thread xiaosonglin (JIRA)



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

xiaosonglin updated AMBARI-24997:
-
Fix Version/s: 2.7.0

> When the custom service does not have the configure directory, add service in 
>  step 4 failed
> 
>
> Key: AMBARI-24997
> URL: https://issues.apache.org/jira/browse/AMBARI-24997
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: !image-2018-12-05-15-49-18-977.png!
>Reporter: xiaosonglin
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: image-2018-12-05-15-45-39-307.png, 
> image-2018-12-05-15-49-18-977.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> review ambari code ,custom service must have configuration directory,  I 
> don't need a configuration directory
> !image-2018-12-05-15-45-39-307.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24997) When the custom service does not have the configure directory, add service in step 4 failed

2018-12-05 Thread xiaosonglin (JIRA)



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

xiaosonglin updated AMBARI-24997:
-
 Flags:   (was: Patch)
External issue URL:   (was: https://github.com/apache/ambari/pull/2690)
Labels:   (was: patch)

> When the custom service does not have the configure directory, add service in 
>  step 4 failed
> 
>
> Key: AMBARI-24997
> URL: https://issues.apache.org/jira/browse/AMBARI-24997
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: !image-2018-12-05-15-49-18-977.png!
>Reporter: xiaosonglin
>Priority: Major
> Attachments: image-2018-12-05-15-45-39-307.png, 
> image-2018-12-05-15-49-18-977.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> review ambari code ,custom service must have configuration directory,  I 
> don't need a configuration directory
> !image-2018-12-05-15-45-39-307.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24997) When the custom service does not have the configure directory, add service in step 4 failed

2018-12-05 Thread xiaosonglin (JIRA)



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

xiaosonglin updated AMBARI-24997:
-
Status: Patch Available  (was: Reopened)

> When the custom service does not have the configure directory, add service in 
>  step 4 failed
> 
>
> Key: AMBARI-24997
> URL: https://issues.apache.org/jira/browse/AMBARI-24997
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: !image-2018-12-05-15-49-18-977.png!
>Reporter: xiaosonglin
>Priority: Major
>  Labels: patch
> Attachments: image-2018-12-05-15-45-39-307.png, 
> image-2018-12-05-15-49-18-977.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> review ambari code ,custom service must have configuration directory,  I 
> don't need a configuration directory
> !image-2018-12-05-15-45-39-307.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24997) When the custom service does not have the configure directory, add service in step 4 failed

2018-12-05 Thread xiaosonglin (JIRA)



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

xiaosonglin updated AMBARI-24997:
-
Status: Open  (was: Patch Available)

> When the custom service does not have the configure directory, add service in 
>  step 4 failed
> 
>
> Key: AMBARI-24997
> URL: https://issues.apache.org/jira/browse/AMBARI-24997
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: !image-2018-12-05-15-49-18-977.png!
>Reporter: xiaosonglin
>Priority: Major
>  Labels: patch
> Attachments: image-2018-12-05-15-45-39-307.png, 
> image-2018-12-05-15-49-18-977.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> review ambari code ,custom service must have configuration directory,  I 
> don't need a configuration directory
> !image-2018-12-05-15-45-39-307.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24997) When the custom service does not have the configure directory, add service in step 4 failed

2018-12-05 Thread xiaosonglin (JIRA)



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

xiaosonglin updated AMBARI-24997:
-
External issue URL: https://github.com/apache/ambari/pull/2690

> When the custom service does not have the configure directory, add service in 
>  step 4 failed
> 
>
> Key: AMBARI-24997
> URL: https://issues.apache.org/jira/browse/AMBARI-24997
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: !image-2018-12-05-15-49-18-977.png!
>Reporter: xiaosonglin
>Priority: Major
>  Labels: patch
> Attachments: image-2018-12-05-15-45-39-307.png, 
> image-2018-12-05-15-49-18-977.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> review ambari code ,custom service must have configuration directory,  I 
> don't need a configuration directory
> !image-2018-12-05-15-45-39-307.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (AMBARI-24997) When the custom service does not have the configure directory, add service in step 4 failed

2018-12-05 Thread xiaosonglin (JIRA)



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

xiaosonglin reopened AMBARI-24997:
--

> When the custom service does not have the configure directory, add service in 
>  step 4 failed
> 
>
> Key: AMBARI-24997
> URL: https://issues.apache.org/jira/browse/AMBARI-24997
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: !image-2018-12-05-15-49-18-977.png!
>Reporter: xiaosonglin
>Priority: Major
>  Labels: patch
> Attachments: image-2018-12-05-15-45-39-307.png, 
> image-2018-12-05-15-49-18-977.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> review ambari code ,custom service must have configuration directory,  I 
> don't need a configuration directory
> !image-2018-12-05-15-45-39-307.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24997) When the custom service does not have the configure directory, add service in step 4 failed

2018-12-05 Thread xiaosonglin (JIRA)



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

xiaosonglin resolved AMBARI-24997.
--
Resolution: Works for Me

> When the custom service does not have the configure directory, add service in 
>  step 4 failed
> 
>
> Key: AMBARI-24997
> URL: https://issues.apache.org/jira/browse/AMBARI-24997
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: !image-2018-12-05-15-49-18-977.png!
>Reporter: xiaosonglin
>Priority: Major
>  Labels: patch
> Attachments: image-2018-12-05-15-45-39-307.png, 
> image-2018-12-05-15-49-18-977.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> review ambari code ,custom service must have configuration directory,  I 
> don't need a configuration directory
> !image-2018-12-05-15-45-39-307.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24997) When the custom service does not have the configure directory, add service in step 4 failed

2018-12-05 Thread xiaosonglin (JIRA)



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

xiaosonglin updated AMBARI-24997:
-
Remaining Estimate: 24h
 Original Estimate: 24h

> When the custom service does not have the configure directory, add service in 
>  step 4 failed
> 
>
> Key: AMBARI-24997
> URL: https://issues.apache.org/jira/browse/AMBARI-24997
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: !image-2018-12-05-15-49-18-977.png!
>Reporter: xiaosonglin
>Priority: Major
>  Labels: patch
> Attachments: image-2018-12-05-15-45-39-307.png, 
> image-2018-12-05-15-49-18-977.png
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> review ambari code ,custom service must have configuration directory,  I 
> don't need a configuration directory
> !image-2018-12-05-15-45-39-307.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AMBARI-24986) Use Ambari CLI to enable and disable trusted proxy support in Ambari

2018-12-05 Thread Sandor Molnar (JIRA)



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

Sandor Molnar resolved AMBARI-24986.

Resolution: Fixed

> Use Ambari CLI to enable and disable trusted proxy support in Ambari
> 
>
> Key: AMBARI-24986
> URL: https://issues.apache.org/jira/browse/AMBARI-24986
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>  Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> Use Ambari CLI to enable and disable trusted proxy support in Ambari.
> Information needed to be collected:
>  * Enable/Disable trusted proxy support
>  ** {{ambari.tproxy.authentication.enabled}} : "true"|"false"
>  * Trusted proxy user (the authenticated user allowed to declare a proxied 
> user) details - One or more may be specified
>  ** hosts from which the proxy user can connect
>  *** {{ambari.tproxy.proxyuser.PROXY_USER.hosts}} : * or a comma-delimited 
> list of hostname, ip address, CIDR Notation (intermixed is ok)
>  ** users allowed to be specified as proxied users by the proxy user
>  *** {{ambari.tproxy.proxyuser.PROXY_USER.users}} : *, or a comma-delimited 
> list of usernames
>  ** group for which users to be proxied are members
>  *** {{ambari.tproxy.proxyuser.PROXY_USER.groups}} : *, or a comma-delimited 
> list of group names
> {noformat}
> [root@c7402 ~]# ambari-server  setup-trusted-proxy
> Using python  /usr/bin/python
> Enter Ambari Admin login: admin
> Enter Ambari Admin password:
> Fetching Trusted Proxy configuration from DB.
> Trusted Proxy support is currently disabled
> Do you want to configure Trusted Proxy support [y/n] (y)?  y
> The proxy user's (local) username? knox  
> Allowed hosts for knox (*)? knox.ambari.apache.org
> Allowed users for knox (*)? *
> Allowed groups for knox (*)? users
> Add another proxy user [y/n]?  y
> The proxy user's (local) username? admin  
> Allowed hosts for admin (*)? 192.168.74.0/24 
> Allowed users for admin (*)? tom, sam, admin
> Allowed groups for admin (*)? admin_users
> Add another proxy user [y/n]?  n
> Save settings [y/n] (y)? y
> Saving Trusted Proxy configuration...
> Saving Trusted Proxy configuration finished
> Ambari Server ' setup-trusted-proxy' completed successfully.
> {noformat}
> The REST API calls to get and set the trusted proxy configurations are
> {noformat:title=GET request}
> GET 
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/tproxy-configuration
> {noformat}
> {noformat:title=GET example response}
> {
>   "href" : 
> "http://c7401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/tproxy-configuration";,
>   "Configuration" : {
> "category" : "tproxy-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI",
> "properties" : {
>   "ambari.tproxy.authentication.enabled" : "true",
>   "ambari.tproxy.proxyuser.admin.groups" : "admin_users",
>   "ambari.tproxy.proxyuser.admin.hosts" : "192.168.74.0/24",
>   "ambari.tproxy.proxyuser.admin.users" : "sam, tom, admin",
>   "ambari.tproxy.proxyuser.knox.groups" : "users",
>   "ambari.tproxy.proxyuser.knox.hosts" : "c7401.ambari.apache.org",
>   "ambari.tproxy.proxyuser.knox.users" : "*"
> },
> "property_types" : {
>   "ambari.tproxy.authentication.enabled" : "PLAINTEXT",
>   "ambari.tproxy.proxyuser.admin.groups" : "PLAINTEXT",
>   "ambari.tproxy.proxyuser.admin.hosts" : "PLAINTEXT",
>   "ambari.tproxy.proxyuser.admin.users" : "PLAINTEXT",
>   "ambari.tproxy.proxyuser.knox.groups" : "PLAINTEXT",
>   "ambari.tproxy.proxyuser.knox.hosts" : "PLAINTEXT",
>   "ambari.tproxy.proxyuser.knox.users" : "PLAINTEXT"
> }
>   }
> }
> {noformat}
> {noformat:title=POST request}
> POST /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {
>   "Configuration": {
> "category" : "tproxy-configuration",
> "properties": {
>   "ambari.tproxy.authentication.enabled" : "true",
>   "ambari.tproxy.proxyuser.knox.hosts": "c7401.ambari.apache.org",
>   "ambari.tproxy.proxyuser.knox.users": "*",
>   "ambari.tproxy.proxyuser.knox.groups": "users",
>   "ambari.tproxy.proxyuser.admin.hosts": "192.168.74.0/24",
>   "ambari.tproxy.proxyuser.admin.users": "sam, tom, admin",
>   "ambari.tproxy.proxyuser.admin.groups": "admin_users"
> }
>   }
> }{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

56 matches

Mail list logo