[jira] [Resolved] (AMBARI-22401) Display Host check report (warning popup) for JAVA_HOME depending on OS family and UI validations
[ https://issues.apache.org/jira/browse/AMBARI-22401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh resolved AMBARI-22401. Resolution: Fixed > Display Host check report (warning popup) for JAVA_HOME depending on OS > family and UI validations > - > > Key: AMBARI-22401 > URL: https://issues.apache.org/jira/browse/AMBARI-22401 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > > This will take care of necessary UI validation and show user warnings for the > prompt as well as the host check report. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22401) Display Host check report (warning popup) for JAVA_HOME depending on OS family and UI validations
[ https://issues.apache.org/jira/browse/AMBARI-22401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317840#comment-16317840 ] Yussuf Shaikh commented on AMBARI-22401: This has been merged to branch-feature-AMBARI-21674 with AMBARI-22406 > Display Host check report (warning popup) for JAVA_HOME depending on OS > family and UI validations > - > > Key: AMBARI-22401 > URL: https://issues.apache.org/jira/browse/AMBARI-22401 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > > This will take care of necessary UI validation and show user warnings for the > prompt as well as the host check report. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22749) Create Pull Request Template
[ https://issues.apache.org/jira/browse/AMBARI-22749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317710#comment-16317710 ] ASF GitHub Bot commented on AMBARI-22749: - vivekratnavel opened a new pull request #70: AMBARI-22749. Create Pull Request Template URL: https://github.com/apache/ambari/pull/70 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 > Create Pull Request Template > > > Key: AMBARI-22749 > URL: https://issues.apache.org/jira/browse/AMBARI-22749 > Project: Ambari > Issue Type: Task >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > > Create a pull request template for github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-20840) Upgrade phantomjs to 2.1.1
[ https://issues.apache.org/jira/browse/AMBARI-20840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317608#comment-16317608 ] Jun He commented on AMBARI-20840: - Hi, Any throughts on this? > Upgrade phantomjs to 2.1.1 > -- > > Key: AMBARI-20840 > URL: https://issues.apache.org/jira/browse/AMBARI-20840 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin >Reporter: Jun He > > PhantomJS is used in ambari-admin ambari-web. The current version is 1.9.8 > which runs only on x86. Support for other archs (ppc/arm) are introduced in > 2.1.1. > Upgrade phantomjs in upstream will enable Ambari on those non-x86 platforms. > And that will help to improve Ambari on compatibility, acceptance, gain more > focus and effort/contributions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20840) Upgrade phantomjs to 2.1.1
[ https://issues.apache.org/jira/browse/AMBARI-20840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun He updated AMBARI-20840: Flags: Important Component/s: ambari-admin Issue Type: Improvement (was: Wish) > Upgrade phantomjs to 2.1.1 > -- > > Key: AMBARI-20840 > URL: https://issues.apache.org/jira/browse/AMBARI-20840 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin >Reporter: Jun He > > PhantomJS is used in ambari-admin ambari-web. The current version is 1.9.8 > which runs only on x86. Support for other archs (ppc/arm) are introduced in > 2.1.1. > Upgrade phantomjs in upstream will enable Ambari on those non-x86 platforms. > And that will help to improve Ambari on compatibility, acceptance, gain more > focus and effort/contributions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22621) Ensure value for hbase.coprocessor.abortonerror is true
[ https://issues.apache.org/jira/browse/AMBARI-22621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-22621: Description: In the coprocessor refactor for hbase-2, Server#abort has been taken out of reach. We should ensure that value for hbase.coprocessor.abortonerror is true so that coprocessor can abort the server by throwing exception. See HBASE-19341 for related details. was: In the coprocessor refactor for hbase-2, Server#abort has been taken out of reach. We should ensure that value for hbase.coprocessor.abortonerror is true so that coprocessor can abort the server by throwing exception. See HBASE-19341 for related detail. > Ensure value for hbase.coprocessor.abortonerror is true > --- > > Key: AMBARI-22621 > URL: https://issues.apache.org/jira/browse/AMBARI-22621 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > In the coprocessor refactor for hbase-2, Server#abort has been taken out of > reach. > We should ensure that value for hbase.coprocessor.abortonerror is true so > that coprocessor can abort the server by throwing exception. > See HBASE-19341 for related details. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-18952) Register BackupObserver and BackupHFileCleaner
[ https://issues.apache.org/jira/browse/AMBARI-18952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884466#comment-15884466 ] Ted Yu edited comment on AMBARI-18952 at 1/9/18 2:55 AM: - Note: There is cost when BackupObserver is registered - it would poll backup table (at the end of bulk load per region) for whether the underlying table has gone thru full backup. was (Author: yuzhih...@gmail.com): Note: There is cost when BackupObserver is registered - it would poll backup table (at the end of bulk load per region) for whether the underlying table has gone thru full backup. > Register BackupObserver and BackupHFileCleaner > -- > > Key: AMBARI-18952 > URL: https://issues.apache.org/jira/browse/AMBARI-18952 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > Over in HBASE-14417, two new classes are added. > org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered > through hbase.master.hfilecleaner.plugins . It is responsible for keeping > bulk loaded hfiles so that incremental backup can pick them up. > org.apache.hadoop.hbase.backup.BackupObserver should be registered through > hbase.coprocessor.region.classes > It is notified when bulk load completes and writes records into hbase:backup > table. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22749) Create Pull Request Template
Vivek Ratnavel Subramanian created AMBARI-22749: --- Summary: Create Pull Request Template Key: AMBARI-22749 URL: https://issues.apache.org/jira/browse/AMBARI-22749 Project: Ambari Issue Type: Task Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Create a pull request template for github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22252) Implement Blueprint v2 API changes
[ https://issues.apache.org/jira/browse/AMBARI-22252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317261#comment-16317261 ] ASF GitHub Bot commented on AMBARI-22252: - adoroszlai opened a new pull request #69: AMBARI-22252. Revert incomplete Blueprint v2 work URL: https://github.com/apache/ambari/pull/69 A few changes for Blueprint V2 work were initially commited on `branch-feature-AMBARI-14714` before the "private" feature `branch branch-feature-AMBARI-14714-blueprintv2` was forked. This change mostly reverts those commits. https://reviews.apache.org/r/64971/ 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 > Implement Blueprint v2 API changes > -- > > Key: AMBARI-22252 > URL: https://issues.apache.org/jira/browse/AMBARI-22252 > Project: Ambari > Issue Type: Epic > Components: ambari-server >Reporter: Magyari Sandor Szilard >Assignee: Robert Nettleton > Fix For: 3.0.0 > > > Epic to cover task required to implement v2 Blueprints API changes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317238#comment-16317238
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905072/AMBARI-22656.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 3 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-agent ambari-server ambari-web:
org.apache.ambari.server.topology.BlueprintImplTest
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12938//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22744) Fix issues with webapp deployment with new Hadoop common changes
[
https://issues.apache.org/jira/browse/AMBARI-22744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317199#comment-16317199
]
ASF GitHub Bot commented on AMBARI-22744:
-
swagle closed pull request #68: [AMBARI-22744][ambari-metrics] Fix issues with
webapp deployment with new Hadoop common changes. Addendum. (swagle)
URL: https://github.com/apache/ambari/pull/68
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-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/AMSApplicationServer.java
b/ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/AMSApplicationServer.java
index 38d46ef5da5..db889bf5804 100644
---
a/ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/AMSApplicationServer.java
+++
b/ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/AMSApplicationServer.java
@@ -18,6 +18,8 @@
package org.apache.hadoop.yarn.server.applicationhistoryservice;
+import static org.apache.hadoop.http.HttpServer2.HTTP_MAX_THREADS_KEY;
+
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.apache.hadoop.conf.Configuration;
@@ -120,7 +122,7 @@ protected void startWebApp() {
LOG.info("Instantiating metrics collector at " + bindAddress);
try {
Configuration conf = metricConfiguration.getMetricsConf();
- conf.set("hadoop.http.max.threads", String.valueOf(metricConfiguration
+ conf.set(HTTP_MAX_THREADS_KEY, String.valueOf(metricConfiguration
.getTimelineMetricsServiceHandlerThreadCount()));
HttpConfig.Policy policy = HttpConfig.Policy.valueOf(
conf.get(TimelineMetricConfiguration.TIMELINE_SERVICE_HTTP_POLICY,
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
> Fix issues with webapp deployment with new Hadoop common changes
>
>
> Key: AMBARI-22744
> URL: https://issues.apache.org/jira/browse/AMBARI-22744
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22744.patch
>
>
> - Fix deploy time issues after migration.
> - Fix imports.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22744) Fix issues with webapp deployment with new Hadoop common changes
[ https://issues.apache.org/jira/browse/AMBARI-22744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317190#comment-16317190 ] ASF GitHub Bot commented on AMBARI-22744: - swagle opened a new pull request #68: [AMBARI-22744][ambari-metrics] Fix issues with webapp deployment with new Hadoop common changes. Addendum. (swagle) URL: https://github.com/apache/ambari/pull/68 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 > Fix issues with webapp deployment with new Hadoop common changes > > > Key: AMBARI-22744 > URL: https://issues.apache.org/jira/browse/AMBARI-22744 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22744.patch > > > - Fix deploy time issues after migration. > - Fix imports. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22748) Create user service abstraction to provide user lookup and authentication services for local and remote users
Robert Levas created AMBARI-22748: - Summary: Create user service abstraction to provide user lookup and authentication services for local and remote users Key: AMBARI-22748 URL: https://issues.apache.org/jira/browse/AMBARI-22748 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Robert Levas Assignee: Robert Levas Fix For: 3.0.0 Create user service abstraction to provide user lookup and authentication services for local and remote users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22253) Cluster creation using v2 blueprints
[ https://issues.apache.org/jira/browse/AMBARI-22253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila resolved AMBARI-22253. Resolution: Won't Fix > Cluster creation using v2 blueprints > > > Key: AMBARI-22253 > URL: https://issues.apache.org/jira/browse/AMBARI-22253 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Magyari Sandor Szilard >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[ https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22740: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-3.0-ams. > Fix integration test for HBase in branch-3.0-ams due to UUID changes > > > Key: AMBARI-22740 > URL: https://issues.apache.org/jira/browse/AMBARI-22740 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22740-3.patch > > > Fixing all integration tests in AMS timeline-service module. > Renamed 'org.apache.hadoop.yarn.server.applicationhistoryservice' package to > 'org.apache.ambari.metrics'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[ https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22740: --- Attachment: AMBARI-22740-3.patch > Fix integration test for HBase in branch-3.0-ams due to UUID changes > > > Key: AMBARI-22740 > URL: https://issues.apache.org/jira/browse/AMBARI-22740 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22740-3.patch > > > Fixing all integration tests in AMS timeline-service module. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[ https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22740: --- Description: Fixing all integration tests in AMS timeline-service module. Renamed 'org.apache.hadoop.yarn.server.applicationhistoryservice' package to 'org.apache.ambari.metrics'. was:Fixing all integration tests in AMS timeline-service module. > Fix integration test for HBase in branch-3.0-ams due to UUID changes > > > Key: AMBARI-22740 > URL: https://issues.apache.org/jira/browse/AMBARI-22740 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22740-3.patch > > > Fixing all integration tests in AMS timeline-service module. > Renamed 'org.apache.hadoop.yarn.server.applicationhistoryservice' package to > 'org.apache.ambari.metrics'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[ https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22740: --- Attachment: (was: AMBARI-22740.patch) > Fix integration test for HBase in branch-3.0-ams due to UUID changes > > > Key: AMBARI-22740 > URL: https://issues.apache.org/jira/browse/AMBARI-22740 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > > Fixing all integration tests in AMS timeline-service module. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22747) Loosely store users authenticating from remote sources (LDAP, PAM, etc)
[
https://issues.apache.org/jira/browse/AMBARI-22747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22747:
--
Description:
Loosely store users authenticating from remote sources (LDAP, PAM, etc) such
that minimal information is store in the Ambari database, relying on
information from the remote sources to provide details like group membership
and username.
Group membership, consecutive authentication failure count, and etc... should
not be stored in the Ambari database for user accounts that are not
authenticated locally.
To do this, convert the {{users}} table into the following tables:
*user*
* user_id (primary key)
* principal_id (foreign key to adminprincipal table)
* user_name
* authentication_source (LOCAL, LDAP, PAM)
* active_widget_layouts
* create_time
*local_user_authentication*
* user_id (foreign key to user table)
* password
* active
* consecutive_failures
* create_time
* update_time
was:
Loosely handle users authenticating from remote sources (LDAP, PAM, etc) such
that minimal information is store in the Ambari database, relying on
information from the remote sources to provide details like group membership
and username.
Group membership, consecutive authentication failure count, and etc... should
not be stored in the Ambari database for user accounts that are not
authenticated locally.
To do this, convert the {{users}} table into the following tables:
*user*
* user_id (primary key)
* principal_id (foreign key to adminprincipal table)
* user_name
* authentication_source (LOCAL, LDAP, PAM)
* active_widget_layouts
* create_time
*local_user_authentication*
* user_id (foreign key to user table)
* password
* active
* consecutive_failures
* create_time
* update_time
> Loosely store users authenticating from remote sources (LDAP, PAM, etc)
> ---
>
> Key: AMBARI-22747
> URL: https://issues.apache.org/jira/browse/AMBARI-22747
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication
> Fix For: 3.0.0
>
>
> Loosely store users authenticating from remote sources (LDAP, PAM, etc) such
> that minimal information is store in the Ambari database, relying on
> information from the remote sources to provide details like group membership
> and username.
> Group membership, consecutive authentication failure count, and etc... should
> not be stored in the Ambari database for user accounts that are not
> authenticated locally.
> To do this, convert the {{users}} table into the following tables:
> *user*
> * user_id (primary key)
> * principal_id (foreign key to adminprincipal table)
> * user_name
> * authentication_source (LOCAL, LDAP, PAM)
> * active_widget_layouts
> * create_time
> *local_user_authentication*
> * user_id (foreign key to user table)
> * password
> * active
> * consecutive_failures
> * create_time
> * update_time
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22747) Loosely store users authenticating from remote sources (LDAP, PAM, etc)
[
https://issues.apache.org/jira/browse/AMBARI-22747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22747:
--
Summary: Loosely store users authenticating from remote sources (LDAP, PAM,
etc) (was: Loosely handle users authenticating from remote sources (LDAP, PAM,
etc))
> Loosely store users authenticating from remote sources (LDAP, PAM, etc)
> ---
>
> Key: AMBARI-22747
> URL: https://issues.apache.org/jira/browse/AMBARI-22747
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication
> Fix For: 3.0.0
>
>
> Loosely handle users authenticating from remote sources (LDAP, PAM, etc) such
> that minimal information is store in the Ambari database, relying on
> information from the remote sources to provide details like group membership
> and username.
> Group membership, consecutive authentication failure count, and etc... should
> not be stored in the Ambari database for user accounts that are not
> authenticated locally.
> To do this, convert the {{users}} table into the following tables:
> *user*
> * user_id (primary key)
> * principal_id (foreign key to adminprincipal table)
> * user_name
> * authentication_source (LOCAL, LDAP, PAM)
> * active_widget_layouts
> * create_time
> *local_user_authentication*
> * user_id (foreign key to user table)
> * password
> * active
> * consecutive_failures
> * create_time
> * update_time
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22747) Loosely handle users authenticating from remote sources (LDAP, PAM, etc)
Robert Levas created AMBARI-22747:
-
Summary: Loosely handle users authenticating from remote sources
(LDAP, PAM, etc)
Key: AMBARI-22747
URL: https://issues.apache.org/jira/browse/AMBARI-22747
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 3.0.0
Loosely handle users authenticating from remote sources (LDAP, PAM, etc) such
that minimal information is store in the Ambari database, relying on
information from the remote sources to provide details like group membership
and username.
Group membership, consecutive authentication failure count, and etc... should
not be stored in the Ambari database for user accounts that are not
authenticated locally.
To do this, convert the {{users}} table into the following tables:
*user*
* user_id (primary key)
* principal_id (foreign key to adminprincipal table)
* user_name
* authentication_source (LOCAL, LDAP, PAM)
* active_widget_layouts
* create_time
*local_user_authentication*
* user_id (foreign key to user table)
* password
* active
* consecutive_failures
* create_time
* update_time
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (AMBARI-22576) LDAP sync should be based off of DN rather than username
[ https://issues.apache.org/jira/browse/AMBARI-22576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas closed AMBARI-22576. - > LDAP sync should be based off of DN rather than username > > > Key: AMBARI-22576 > URL: https://issues.apache.org/jira/browse/AMBARI-22576 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Levas >Assignee: Robert Levas > Labels: ldap > Fix For: 3.0.0 > > > LDAP sync should be based off of DN rather than username. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22576) LDAP sync should be based off of DN rather than username
[ https://issues.apache.org/jira/browse/AMBARI-22576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas resolved AMBARI-22576. --- Resolution: Won't Do > LDAP sync should be based off of DN rather than username > > > Key: AMBARI-22576 > URL: https://issues.apache.org/jira/browse/AMBARI-22576 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Levas >Assignee: Robert Levas > Labels: ldap > Fix For: 3.0.0 > > > LDAP sync should be based off of DN rather than username. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: AMBARI-22656.patch > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: (was: AMBARI-22656.patch) > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
