Pulse Server Configuration Requirements

Software Requirements

Pulse Server (Supported Details):

User Requirements

Pulse Server Installation

• Root (preferred) or non-root user with required access to install, configure, and start/stop Docker services.
• The user must have required access to load/restart/terminate Docker containers and images.

Pulse Agent Installation

• SSH-Based Deployment
  • SSH user having a common password or password-less (RSA private key) based access from the core Pulse server to deploy agents on all nodes with a single deploy command. The SSH user should have password-less sudo access on all cluster nodes, required for agent package installation on the OS
  • Disable the TTY requirement for the respective user to run sudo on all cluster nodes.
• Custom Installation Steps
  • Acceldata team will provide commands to the system administrator for installing Hydra agent binaries on all nodes.
• Parcel-Based Deployment (only available for CDH 6.x / CDP 7.x)
  • Pulse provides a parcel-based approach as well for Pulse agent deployment to directly activate, distribute, and install via Cloudera Manager
• Mpack-Based Installation: Pulse provides an mpack-based approach as well for Pulse agent deployment to directly activate, distribute, and install via Ambari.

Security

For KERBEROS-enabled clusters:

• Headless keytab file for the HDFS user (principal example: hdfs-cluster@TEST.COM), required for connectors, file system analytics, and exploration.
• Special case requirements:
  • hdfs user not allowed - need a user with additional property changes and HDFS path privileges (Refer to the cluster configuration changes section)
  • hdfs user does not have access on Kafka topic metadata - need kafka service keytab present on one broker for accessing Kafka metadata details or a user having admin privileges at the ACL level (Refer to the cluster configuration changes section)
  • 403 forbidden access error on FS Analytics with hdfs user - Requires NameNode service keytab (example: nn/nn_host@TEST.COM)
• Place the /etc/krb5.conf file on the Pulse server from the respective cluster.
• Ensure network connectivity from the Pulse server to the respective KDCs of the realm to acquire required Kerberos tickets.
  • Run command to test connectivity: kinit -kt <keytab_path> <principal_name>
• In case of SSSD + Kerberos + AD enabled clusters, specified user such as hdfs or other user should exist on Pulse linux servers
• Service list enabled with Kerberos on UI endpoints such as HDFS Namenode UI, and Resource Manager UI.

For SSL/HTTPS Enabled Clusters:

• Truststore and cert files available on a node used to connect with SSL-enabled services like HDFS, HIVE, YARN, etc.
• Service list enabled with TLS/SSL

For LDAP Integration:

• Read-only user for LDAP interface able to query group and user information to validate user login.
• Network connectivity from Pulse server to respective LDAP servers.

For SMTP Integration:

• Network connectivity from Pulse server to SMTP hosts

Network

Pulse port list for Agent to Server and User accessibility:

• Hadoop Service - For alert and connectors module, requires connectivity from Acceldata Pulse Server to Hadoop host and configured ports (request for master list from Acceldata team)
• Internal – Refers to connectivity from Acceldata Pulse Agents to Acceldata Pulse Server(s). The services can be deployed in a multi-node pattern, for which they need to be exposed to all the Pulse hosted nodes.
• External – Refers to ports that end users within the enterprise network would need access to. This port should be accessible by your laptop once connected directly to the enterprise network or connected via VPN.

The following table provides details of the different ports used by Pulse services:

Reserved Pool Ports

If Pulse is configured against multiple Hadoop clusters, each with its own KDC servers, the count of connectors will be directly proportional to the number of distinct KDC servers configured.

To support this deployment model, we suggest allocating a block of ports from 19080 to 19099. Pulse services will then be set to select a port from this designated range.

Files and Additional Information

• Ambari/Cloudera Manager admin or read-only credentials, used by Pulse CLI to map service host discovery.
• Place /etc/hadoop/conf/hdfs-site.xml and /etc/hadoop/conf/core-site.xml on Pulse server
• Share the size of the FS Image
• Hadoop service-to-port mapping discovery (Optional)
• Various Log Paths for services, applications, and OS-level Syslogs.
• Host-to-service mapping discovery