Installing the Data Fabric Client on Red Hat and Oracle Linux (Non-FIPS)
This section describes how to install the Data Fabric client on Red Hat and Oracle Linux.
The following steps describe how to install a non-FIPS client for use with a secure non-FIPS cluster. If you need to install a FIPS or non-FIPS-enabled client for use with a cluster consisting of all FIPS nodes or a mix of FIPS and non-FIPS nodes, see the procedures in Installing the Data Fabric Client (FIPS).
These steps assume that you have already set up a Data Fabric repository as described in Adding the Data Fabric Repository on RHEL, CentOS, or Oracle Linux.
-
Remove any previous Data Fabric software. You can use
rpm -qa | grep mapr
to get a list of installed Data Fabric packages, then type the packages separated by spaces after therpm -e
command:rpm -qa | grep mapr rpm -e mapr-fileserver mapr-core
- Import the package
keys to enable signature
verification:
Optionally, you may use commands to verify the signatures before installing the software. For more information, see HPE GPG Public Keys for GPG or RPM Signature Verification.wget --user=<email> --password=<token> -O /tmp/maprgpg.key -q https://package.ezmeral.hpe.com/releases/pub/maprgpg.key && rpm --import /tmp/maprgpg.key wget --user=<email> --password=<token> -O /tmp/hpeezdf.pub -q https://package.ezmeral.hpe.com/releases/pub/hpeezdf.pub && rpm --import /tmp/hpeezdf.pub && gpg --import /tmp/hpeezdf.pub
-
Install the client for your target architecture:
yum install mapr-client.x86_64
-
To use this client with a secure cluster or clusters, copy the following files from theIf this client will connect to multiple clusters, merge the
/opt/mapr/conf
directory on the cluster to the/opt/mapr/conf
directory on the client.ssl_truststore
ssl_truststore.p12
ssl_truststore.pem
maprtrustcreds.conf
maprtrustcreds.jceks
ssl_keystore-signed.pem
ssl_truststore
files with the/opt/mapr/server/manageSSLKeys.sh
tool. You must perform the merging on the cluster. See Managing Secure Clusters for details on how to connect to a secure cluster. -
Run
configure.sh
to configure the client. In the following examples, the-N
parameter specifies the cluster name, the-c
(lowercase) parameter specifies a client configuration, the-secure
parameter is added if the cluster is secure, the-C
(uppercase) parameter specifies the CLDB nodes, and the-HS
parameter specifies the HistoryServer node. To ensure that the client can connect in the event of a CLDB node failure, all CLDB nodes are specified. For more information about the syntax, parameters, and behavior ofconfigure.sh
, see configure.sh.Secure cluster example/opt/mapr/server/configure.sh -N my.cluster.com -c -secure -C mynode01:7222,mynode02:7222,mynode03:7222 -HS mynode02
Non-secure cluster example/opt/mapr/server/configure.sh -N my.cluster.com -c -C mynode01:7222,mynode02:7222,mynode03:7222 -HS mynode02
NOTEIf the cluster was configured with a cluster admin
user:group
that is different from the defaultmapr:mapr
value, you must include options to specify the cluster admin user and group information when you runconfigure.sh
to configure the client.If the cluster-admin user ID is present on the client node, include these options:-u
-g
If the cluster-admin user ID is not present on the client node, include these options:-u
-g
--create-user | -a
-U
-G
The following table describes each option:Option Description -u
The user name under which cluster services run. -g
The group name under which cluster services run. --create-user | -a
Creates a local user to run cluster services, using the specified user either from the -u
parameter, or from the environment variable$MAPR_USER
.-U
The user ID to use when creating $MAPR_USER
with the--create-user
or-a
option; corresponds to the-u
or--uid
option of theuseradd
command in Linux.-G
The group ID to use when creating $MAPR_USER
with the-create-user
or-a
option; corresponds to the-g
or-gid
option of theuseradd
command in Linux. -
At the end of the client installation, run the maprlogin password command to create a valid ticket to connect to the cluster.