Bug 1105149

Summary:	[RFE] remove the option of automated LDAP Installation & Configuration to the Installer Script
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Steve Watt <swatt>
Component:	rhs-hadoop-install	Assignee:	Jeff Vance <jvance>
Status:	CLOSED CURRENTRELEASE	QA Contact:	BigData QE <bigdata-qe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	rhgs-3.0	CC:	bchilds, dahorak, eboyd, esammons, matt, mbukatov, nlevinki, swatt
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHGS 3.0.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	1.34-1	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-10 07:41:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Steve Watt 2014-06-05 13:38:43 UTC

At present, after setup_cluster.sh is run, the UIDs and GIDs across the cluster are always inconsistent. This means that the solution does not work after installation and the user has to manually remediate the cluster to create UID/GID consistency, which is a lot of work and prone to error.

We need to modify setup_cluster to incorporate the usage of LDAP, the script should support 3 options:

- If the customer has an existing LDAP server: Via documentation, instruct the user which users and groups to create in their LDAP repository prior to running the script. Provide an option for the user to pass in the existing LDAP Server as a parameter to the setup_cluster script and the script will configure the cluster to use that LDAP Server for Identity and Authorization. The script will provide a notice to the user that it is going to do this before executing these steps.

- (Default Option) If the customer has no existing LDAP server: The setup_cluster script will auto install an LDAP server on the Ambari server and auto configure the required users and groups within its LDAP repository. The script will also configure each server within the cluster to use the new LDAP server for Identity and Authorization. The script will provide a notice to the user that it is going to do this before executing these steps.

- If the customer has no existing LDAP Server and DOES NOT WANT ONE installed: The script does nothing additional. We provide a UID/GID consistency check at the end of the installation and the documentation describes how to manually remediate inconsistent UID/GIDs.

Comment 2 Jeff Vance 2014-06-11 15:39:29 UTC

new, optional "--ldap [user-list]" feature added. Default is that setup_cluster.sh does nothing related to creating the required hadoop users (mapred, yarn, hcat, hive). However, if --ldap is specified then setup_cluster will create a simple ldap/ipa server on the management node. All storage nodes and the yarn-master node will be setup as ldap/ipa clients. If <user-list> is included then those additional users will also be added.

Comment 3 Jeff Vance 2014-06-25 14:18:32 UTC

We've decided to not automate ldap/ipa installation with the installer tool for teh Denali release. Therefore the various user related options for setup_cluster have been removed and the usage text updated.

Comment 4 Daniel Horák 2014-06-25 15:00:46 UTC

(In reply to Jeff Vance from comment #3)
> We've decided to not automate ldap/ipa installation with the installer tool
> for teh Denali release. Therefore the various user related options for
> setup_cluster have been removed and the usage text updated.

I think, that there should not be any LDAP related file in rhs-hadoop-install package.
# rpm -ql rhs-hadoop-install | grep ldap
  /usr/share/rhs-hadoop-install/bin/ldap_clients.sh
  /usr/share/rhs-hadoop-install/bin/ldap_server.sh

>>  ASSIGNED

Comment 5 Steve Watt 2014-06-26 14:06:47 UTC

We can leave this open since this bug is now simply a request to remove the old LDAP logic out of the code. I've changed the priority and severity to low to reflect that. I don't think we will fix this for Denali as there are higher priority issues and I'm loathe to introduce the risk of code changes so close to release. As such, I've removed "Denali" from the Internal Whiteboard as well.

Comment 7 Steve Watt 2014-06-26 16:51:02 UTC

Jeff removed the LDAP options from the setup_cluster command line and thereby removed the ability to invoke the code that handles LDAP options

Comment 8 Jeff Vance 2014-07-10 19:59:27 UTC

all ldap/ipa related logic has been removed from the execution path of the GA installer in version 1.27 and several versions earlier.

Comment 12 Jeff Vance 2014-07-25 20:48:37 UTC

removed the 2 ldpa related scripts from bin/
fixed in version 1.32

Comment 13 Jeff Vance 2014-07-29 03:43:02 UTC

I have deleted all code related to creating the hadoop users. Fixed in version 1.34.

Comment 14 Ondřej Komárek 2014-07-30 14:07:49 UTC

Tested with:
rhs-hadoop-install-1_34-1.el6rhs.src.rpm (https://brewweb.devel.redhat.com/buildinfo?buildID=371877)

Flag SETUP_LDAP is not present in setup_cluster.sh anymore. Also, parameters --deploy-ldap-srv and --ext-ldap-srv which seted up this flag are not accepted now. Files ldap_clients.sh and ldap_server.sh are deleted. All code related with unsupported ldap option is gone. There is absolutely no reference about ldap in version 1.34-1:
grep -r "ldap" rhs-hadoop-install-1_34:
(no result)

This issue is fixed -> VERIFIED.