Using a Local, Shared Repository With the Installer

The Installer can use a local repository instead of an internet repository.

When you run the mapr-setup.sh script, it attempts to connect to https://package.ezmeral.hpe.com/ and configures an internet repository. If there is no internet connectivity, the script asks for archive files so that it can create a local repository.

IMPORTANT
To access the Data Fabric internet repository, you must specify the email and token of an HPE account. For more information, see Using the HPE Data FabricToken-Authenticated Internet Repository.
NOTE
Passing -a <full path each archive file> to the mapr-setup.sh script bypasses the internet connectivity check and automatically creates a local repository with the provided archive files.

To install with a local, shared repository, the node that runs mapr-setup.sh needs the following:

NOTE
Red Hat clusters must have access to a local EPEL repository, as described in Adding the Data Fabric Repository on RHEL, CentOS, or Oracle Linux. The EPEL repository enables installation of these packages:
  • clustershell
  • pdsh
  • pdsh-rcmd-ssh
  • sshpass*

*Before installing a cluster on a SLES image, you must install sshpass, as described in Adding the Data Fabric Repository on SUSE.

After downloading the mapr-setup.sh script and the archive files to the node that will run the Installer, run the following command from the directory that contains the mapr-setup.sh script:
bash ./mapr-setup.sh -a <full path to the archive files>