Using mapr-setup.sh

This topic describes how you can use and run the Installer setup script.

Before you can run the Installer, you must run the mapr-setup.sh script to set up the installation environment on a node that may or may not be part of the cluster. Then, you can run the Installer to perform the installation.

To download and run the mapr-setup.sh script, see Installer.

mapr-setup.sh

The mapr-setup.sh script performs the following steps to prepare the node to run the Installer:

  1. Verifies and installs the operating system dependencies and Java requirements on the current node.
  2. Checks for Internet connectivity to the remote repository.
    • If access to https://package.ezmeral.hpe.com/ is not available, the script prompts for the archive tarballs. Provide the full paths of these tarballs in a space-delimited list.
  3. Asks for the hostname and port that cluster nodes can use to connect to the Installer node.
  4. Asks for the cluster admin user account and creates the account if it does not exist. This account must exist or be created on each node in the cluster. (The cluster admin is the cluster administrator.)
  5. Sets up a custom yum or apt repository.

    • If no archive file is provided, the script configures access to the https://package.ezmeral.hpe.com/ repository. For example, on RedHat / CentOS, the script creates the following remote repository: /etc/yum.repos.d/mapr_installer.repo

    • If archive files are provided, the script sets up a local repository.

  6. Starts the Installer.
Syntax
/opt/mapr/installer/bin/mapr-setup.sh 
[docker client]
[docker installer]
[-a <full_path_to_archive_file(s)>]
[install]
[reload]
[remove]
[update]
[-h]
[-i <full_path_to_installer_package>]
[-n]
[-p <hostname:port>]
[-r <repository_URL>]
[-y]

Options

In general, you should run the mapr-setup.sh script without using any additional options. Consider using the following options only if you have a known Internet connectivity issue, your Installer packages are not located in the default repository, or you need help with the installation process.

Option Description
docker client Use this option to create a PACC image.
docker installer Use this option to create a Installer container.
install Use this option to install the Installer and definition files. If you don't specify an option for mapr-setup.sh, the install option is invoked by default.
Example: 
./mapr-setup.sh install
reload Use this option to reinstall the Installer and definition files. This option is helpful in debugging. No prompt is returned when you use this option.
Example: 
./mapr-setup.sh reload
remove Use this option to remove the Installer and definition files. This option does not remove the mapr-setup.sh script.
Example: 
./mapr-setup.sh remove
update Use this option to update the installer packages. The setup script checks https://package.ezmeral.hpe.com/ for new packages and installs the packages if they are available.
Example: 
./mapr-setup.sh update
-a|--archives Use this option to bypass the Internet connectivity check and directly create a local repository. Specify a space-delimited list of the full paths to the following archive files (the order of the files is important) as an argument to the option:
  • Installer archive
  • Ecosystem Pack (EEP) archive
  • Data Fabric archive for the current release
For more information, see Using a Local, Shared Repository With the Installer.
NOTE
Use this option when the Installer node does not have access to the Internet or is behind a restricted VPN or firewall.
Example for Releases 5.2 and later: 
./mapr-setup.sh -a mapr-installer-v1.5.201705041557.deb.tgz 
mapr-mep-v3.0.0.201704051422.deb.tgz mapr-v5.2.1GA.deb.tgz
Example for Releases 5.0 and 5.1: 
./mapr-setup.sh -a mapr-5.0-5.1.201705082100.deb.tar.gz

For Releases 5.0 and 5.1, you only need to provide the core archive file.

-h|--help Use this option to display the command-line help for the Installer.
NOTE
If you use this option with other options, the Installer will ignore all options except for -h.
Example: 
./mapr-setup.sh -h
-i|--install Use this option to override the Installer packages stored in the remote or local repository. This option take a space-delimited list of the two local packages needed to install the Installer (the order of the files is not important):
  • Installer package
  • Installer definitions package
Example: 
./mapr-setup.sh -i mapr-installer-definitions_1.5.201705021610_all.deb 
mapr-installer_1.5.201705021610_all.deb
-n|--noinet Use this option when you don't want mapr-setup.sh to fetch packages from the Internet. Instead of taking the files as an argument like -a, this option prompts you for a complete set of archive files (the order of the files is important):
  • Installer archive
  • Ecosystem Pack (EEP) archive
  • Core archive for the current release
NOTE
Configure this option when the Installer node does not have access to the Internet or is behind a restricted VPN or firewall. If you use this option together with -a, mapr-setup.sh will ignore -n.
Example: 
./mapr-setup.sh -n
-p|--port This option specifies the hostname:port to use for installation-related communication between the Installer node and other nodes in the cluster. The Installer also adds the hostname provided as a default entry for the list of cluster nodes on the Configure Nodes page. Both the hostname and the port are not required when configuring this option; you can choose to configure one or both values.
NOTE
Configure this option when the Installer node has multiple interfaces or hostnames and the result of hostname is not a value that other nodes in the cluster are able to communicate with.
Example: 
./mapr-setup.sh -p perfnode131.perf.lab:9441
-r|--repo Use the -r option to specify the repo (typically for a new installation). There is no longer a default repo:
Example: 
./mapr-setup.sh -r http://<email>:<token>@myrepo.download.pkgs/mapr/releases/
-R|--new_repo_url Specify a new repository URL for both ecosystem and core components. Use this option only with the reload command, including the required email and token, as indicated in Using the HPE Data Fabric Token-Authenticated Internet Repository.
Example:
./mapr-setup.sh -R http://<email>:<token>@<new_url> reload
-v|--verbose Use this option when you want additional information about the setup process.
Example: 
./mapr-setup.sh -v
-x Use this option to run the setup script but change the cluster admin password to a value other than the default value. By default, the Installer creates the mapr user and sets the password to mapr. If the mapr user is present, you can use the following command to change the password. If the mapr user is not present, using the command creates the mapr user with the password that you specify:
Example:
./mapr-setup.sh -x <mapr-password>
The following command runs the setup script, bypassing all prompts and using default values, but sets the mapr user password to Adminpass:
./mapr-setup.sh -x Adminpass -y
-y|--yes Use this option to bypass the Installer's usual prompts and immediately proceed with the default options. This option produces the same installation result as going through the mapr-setup.sh script prompts and choosing all of the default options, but with increased speed.
Example: 
./mapr-setup.sh -y

Stopping mapr-setup.sh

If you need to stop mapr-setup.sh while it is running, press Ctrl + C. Depending on when you issue the Ctrl + C command, the script either stops or continues to execute until it is able to stop gracefully. You can run the script again or use the remove option, described earlier on this page, to remove the Installer and definition files and then rerun the script.

Another way to exit the script is to answer NO when the script prompts for a YES or NO reply. For example, when the script asks if you want to upgrade dependent packages, if you reply NO, the script exits.

After Running mapr-setup.sh

To validate that the Installer started correctly, do one of the following:
  • Log in to the Installer web interface using the cluster admin user name and password.
  • Run the Installer Stanza exportcommand using the cluster admin user name and password.
If the Installer does not start up correctly, check the logs. See Logs for the Installer.

If you want to change any parameter that you provided to mapr-setup.sh on a previous run (for example, the repository URL, the cluster admin user name, or another parameter), you can safely rerun mapr-setup.sh with the new parameters. Doing so updates the Installer configuration to use the new parameters. However, do not rerun mapr-setup.sh while an installation or a probe command is in progress.

Installer Web Interface

When you run the Installer web interface, it performs the following tasks:

  1. Displays the services and ecosystem components that you can install based on the software version that you select.
  2. Provides the option to install Monitoring.
  3. Guides you through node and cluster configuration.
  4. Verifies that each node meets the node requirements.
  5. Sets a default, configurable service layout across the nodes in the cluster based on the requirements of each service.
  6. Installs or upgrades the software and associated operating-system dependencies.
  7. If you chose to install a trial or community license, it will attempt to apply the license to your cluster.

Installer Stanzas

Running mapr-setup.sh also installs Installer Stanzas. Stanzas give you a script-based tool to perform all the installation tasks you can perform using the Installer web interface. See Installer Stanzas. In addition, Stanza commands make it possible to probe a cluster that was installed without using the Installer and use the import command to set up the installer database. See Using probe and import to Generate the Installer Database.

Installer Components

The Installer uses the following components to set up the installation environment:

Name Filename Description
Configuration Script mapr-setup.sh Script that configures a node to run the Installer. This includes setting up an Internet or local repository.
Installer Package mapr-installer-<version> Package that contains the Installer.
Installer Definitions Package mapr-installer-definitions-<version> Package that contains the list of software versions, services, and ecosystem components that you can install with the Installer.
Service Packages various

If you use a remote repository, the Installer accesses the installation packages from https://package.ezmeral.hpe.com/.

If you use a local repository, the Installer accesses the installation packages from the local repository. The mapr-setup.sh script creates the local repository with the packages available in the archive files that you provide to the mapr-setup.sh script. For more information, see Using a Local, Shared Repository With the Installer.