Page tree
Skip to end of metadata
Go to start of metadata

Prerequisites

This section provides information about the software and hardware prerequisites for installing Kyvos Manager. It also gives information about the standard checks that must be performed before starting the installation.

Hardware prerequisites for Kyvos Manager server

  • Operating System: Ubuntu 12.04 (64 bit), CentOS 6.2, 6.3 or 6.4 (64 bit)
  • Memory: 4 GB RAM or more
  • Storage Space: 10 GB or more

Software prerequisites for Kyvos Manager Client

Kyvos Manager Client is the computer used to access the Web application. You can access the Kyvos Manager Client through Google Chrome 35 or above.

Software prerequisites for cluster nodes

This section provides the software perquisites for cluster nodes for both sudo and non-sudo users. Sudo rights allow you to run programs with the security privileges of another user, by default the superuser.

Setting up cluster nodes when you are not a sudo user

The following prerequisites are required for all nodes.

  • Operating System: Ubuntu 12.04 (64 bit), CentOS 6.2, 6.3 or 6.4 (64 bit)
  • All nodes must have a user account with common login credentials
  • All the nodes used for cluster creation must have:
    • tar
    • ssh running (sshd service)
    • passwordless ssh (optional)
  • Ensure that Iptables/firewall is disabled on each host of a cluster to make them reachable through Kyvos Manager. For this, use the following commands on each host.


Host

Command

CentOS

service iptables save
service iptables stop
chkconfig iptables off

Ubuntu

ufw disable

  • If the firewall cannot be disabled, then ensure:
    • Access to ports used by Kyvos is allowed
    • Access to port 22 is allowed on each node for node retrieval to work properly
  • The MapR client must be installed on all the nodes where the BI Server and Query Engine binaries are being deployed.
    Add the following in BI Server under Dashboard > cluster name > Components > Kyvos > JAVA Options Configuration on the Kyvos Manager Portal.

-Djava.security.auth.login.config=/opt/mapr/conf/mapr.login.conf

You must restart the BI Server after this change.

Setting up cluster nodes when you are a sudo user       

Ensure that the following prerequisites are fulfilled for all the nodes.

  • Operating System: Ubuntu 12.04 (64 bit), CentOS 6.2, 6.3 or 6.4 (64 bit)
  • All nodes must have a user account with common login credentials and sudo access rights. To configure sudo access permission for a user, make an entry for that user, for example, user1, as shown below the root user entry under /etc/sudoers file

root    ALL=(ALL)      ALL
user1  ALL=(ALL)       ALL

  • Ensure the following software are installed and running on all the nodes used for cluster creation:
    • tar
    • ssh running (sshd service)
    • passwordless ssh
  • Ensure that Iptables/firewall is disabled on each host of a cluster to make them reachable through Kyvos Manager. For this, use the following commands on each host.

Host

Command

CentOS

service iptables save
service iptables stop
chkconfig iptables off

Ubuntu

ufw disable

  • If the firewall cannot be disabled, then ensure:
    • Access to ports used by Kyvos is allowed.
    • Access to port 22 is allowed on each node for node retrieval to work correctly.
  • Default Requirestty must be disabled to allow the Kyvos Manager to function. This option is required to execute sudo commands remotely. To disable tty, prefix with comment symbol (#) or delete the following line in /etc/sudoers file on each host in the cluster.
default requirestty

To add a comment to the example above, prefix it with a # symbol.

Example:

# default requirestty
  • If there is shared key authentication, configure NOPASSWD in the /etc/sudoers file.

A shared/private key file (for example, “id_rsa”) is one whose corresponding public key file (for example, “id_rsa.pub”) is copied to authorized_keys to all the nodes used in the cluster to allow passwordless ssh. This will allow you to execute sudo operations without using your password.

Username ALL=(ALL) NOPASSWD: ALL

 

 WARNING

Place the username ALL=(ALL) NOPASSWD:ALL configuration setting just under %sudo   ALL=(ALL:ALL) ALL. If this setting is not placed correctly, then the %sudo ALL=(ALL:ALL) ALL entry will override your configuration.

Configuring repositories (CentOS)

Kyvos Manager installs software from the Extra Packages for Enterprise Linux (EPEL) repositories that are not a part of the default CentOS installation. So, ensure that you have the latest EPEL version installed on your hosts.

To install the EPEL repository:

wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
sudo rpm -Uvh epel-release-6*.rpm

To confirm the repo list for EPEL:

sudo yum repolist


The output of this command must have EPEL mentioned in the repo list.

Sample:

repo id         repo name                                                status

base            CentOS-6 - Base                                           6,381

epel            Extra Packages for Enterprise Linux 6 - x86_64            8,626

extras          CentOS-6 - Extras                                            12

rpmforge        RHEL 6 - RPMforge.net - dag                               4,594

updates         CentOS-6 - Updates                                          562

virtualbox      Oracle Linux / RHEL / CentOS-6 / x86_64 - VirtualBox         19

repolist:                                                                20,194

 

  • The MapR client must be installed on all the nodes where the BI Server and Query Engine binaries are being deployed. Add the following in BI Server under Dashboard > cluster name > Components > Kyvos > JAVA Options Configuration on the Kyvos Manager Portal.
-Djava.security.auth.login.config=/opt/mapr/conf/mapr.login.conf.

  You must restart the BI Server after this change.

Pre-installation checklist

Before you start installing Kyvos Manager, verify the following:

  • SELinux must be disabled.
  • Cluster hosts must have a working network name resolution system. DHCP server configured for DNS name resolution or /etc/hosts file must be configured correctly.
  • Ensure apt-get is working (for Ubuntu).
  • Ensure yum is working (for CentOS) and can install the package on nodes either using the default or configured local repositories.
  • Ensure wget is working.
  • The user account from which the cluster is being deployed must have full access permissions on all the installation paths provided on Kyvos Manager.

Next: Install Kyvos Manager

  • No labels