HPE Ezmeral Data Fabric 6.2 is In Maintenance and transitions to "End of Maintenance" in June 2024. Please see the latest documentation.

About Release 6.2
This site contains documentation for HPE Ezmeral Data Fabric release 6.2 including installation, configuration, administration, and reference content, as well as content for the associated bundled ecosystem components and drivers.
6.2 Installation
This section contains information about installing and upgrading HPE Ezmeral Data Fabric software. It also contains information about how to migrate data and applications from an Apache Hadoop cluster to a HPE Ezmeral Data Fabric cluster.
6.2 Data Fabric
HPE Ezmeral Data Fabric is the industry-leading data platform for AI and analytics that solves enterprise business needs.
- HPE Ezmeral Data Fabric File Store
  HPE Ezmeral Data Fabric File Store is a distributed file system for data storage, data management, and data protection. File Store supports mounting and cluster access via NFS and FUSE-based POSIX clients (basic, platinum, or PACC) and also supports access and management via HDFS APIs.
- HPE Ezmeral Data Fabric Database
  HPE Ezmeral Data Fabric Database is an enterprise-grade, high-performance, NoSQL database management system that you can use for real-time, operational analytics.
- HPE Ezmeral Data Fabric Streams
  HPE Ezmeral Data Fabric Streams brings integrated publish and subscribe messaging to the Data Fabric Converged Data Platform.
- Kubernetes Interfaces for Data Fabric
  This section describes the Kubernetes Interfaces for Data Fabric, which include the Container Storage Interface (CSI) driver for multiple container-orchestration systems, and the FlexVolume driver for Kubernetes.
- Cluster Management
  Provides a synopsis of the various cluster components and their management.
- Performance
  Describes how to tune system performance, manage RDMA, and optimize CLDB tables.
- Security
  Provides an overview of the data-fabric security features.
  - Authentication in Data Fabric
    Describes types of authentication available with the HPE Ezmeral Data Fabric and how to manage user authentication with the maprlogin utility.
  - Authorization in Data Fabric
    Describes the basics of authorization including Access Control Lists and Access Control Expressions.
  - Encryption in Data Fabric
    Describes encryption types available on the HPE Ezmeral Data Fabric.
  - Prevent Storage of Specified Types of Files
    Provides an overview of how to prevent certain types of files from being stored on certain volumes.
  - Impersonation in Data Fabric
    Describes impersonation in data-fabric, which allows centralized control of access to resources in the file system, HPE Ezmeral Data Fabric Database, and HPE Ezmeral Data Fabric Streams.
  - Auditing in Data Fabric
    Data Fabric allows you to log audit records of cluster-administration operations, and operations on directories, files, streams and tables.
  - Policy-Based Security
    Starting in core version 6.2.0 (EEP 7.0.0), HPE Ezmeral Data Fabric supports Policy-Based Security, a feature that administrators can use to classify security controls into a manageable number of security policies.
    - Security Policy Domain and Policy Management
      Describes how to create the security-policy domain, propagate security policies to all the clusters within the domain, and some considerations for moving data.
      - Configuring the Global Policy Master
        This topic describes how to configure a cluster as the global policy master from the CLI, REST API, and Control System.
    - Volume-Level Security Policy Enforcement Mode
      Prior to Core 6.2.0, Data Fabric supported enforcement based on mode and ACEs set directly on data objects. Starting in 6.2.0, security policies provide an additional or alternative way to control access to data. The volume-level enforcement mode specifies which of these methods a volume uses to govern access to data.
    - Security Policy Enforcement Process
      Data Fabric Database and Data Fabric File System enforce security policies hierarchically, starting at the volume level.
    - Security Policy Inheritance and Replication
      Security policies are inherited during data-object creation and copied over during mirroring and replication.
    - Example Using Security Policies
      This example demonstrates how to secure data, set permissions, and create, view, and modify a security policy.
  - External KMIP Keystore Overview
    Describes the External KMIP Keystore functionality.
  - Security for Ecosystem Components
    Whether you install data-fabric software by using the Installer or by using manual steps, the platform and its ecosystem components are installed with security ON by default.
  - Security Settings for Ecosystem Components
    Lists the security settings for all HPE Ezmeral Data Fabric ecosystem components.
  - Security Exceptions
    "Secure by default" means network-safe authentication and encryption. This page describes areas in which secure-by-default capabilities are not yet implemented for the data-fabric platform or ecosystem components. Included where applicable, are links to more information to help you work around those issues.
- YARN
- Client Connections
  The following sections describe how a client connects to local and remote data-fabric clusters.
6.2 Administration
This section describes how to manage the nodes and services that make up a cluster.
6.2 Development
This section contains information related to application development for Ezmeral ecosystem components and HPE Ezmeral Data Fabric products, including the file system, Database (Key-Value and JSON), and Event Streams.
Other Docs
This section contains release-independent information, including: Installer documentation, Ecosystem release notes, interoperability matrices, security vulnerabilities, and links to other data-fabric version documentation.
Glossary
Definitions for commonly used terms in MapR Converged Data Platform environments.

Configuring the Global Policy Master

This topic describes how to configure a cluster as the global policy master from the CLI, REST API, and Control System.

Setting the Global Policy Master from the Control System

Complete the following steps in the Control System to set a cluster as the global policy master:

Click the Security Settings icon.
Click the PBS Mode setting.
Select the PBS Mode as Master from the drop-down.
Click Submit to save the setting.

Setting the Global Policy Master from the CLI or REST API

Complete the following steps from the CLI or REST API to set a cluster as the global policy master:

Run the following command to set a cluster as the global policy master:

maprcli config save -values '{"cldb.pbs.global.master":"1"}'

Send a request of type POST. For example, to designate a cluster as the global policy master, send a request similar to the following:

curl -k -X POST 'https://<hostname>:8443/rest/config/save?values={"cldb.pbs.global.master":"1"}' --user mapr:mapr

Changing the Global Policy Master Cluster

If the cluster designated as the global policy master goes offline or fails, there is no automatic fail-over or recovery for security policies. In such a scenario, promote one of the member security-policy clusters as the new master. When the original master cluster comes back up, set it as a member cluster.

You can identify the role of a cluster from the Control System or by running the following command:

maprcli dashboard info -json | grep globalPolicyMaster

To elect a new global policy master, perform the following steps:

Verify that the cluster you plan to promote to global policy master is set as a member. If the cluster is a member, the value of cldb.pbs.global.master on the cluster is 0. If the cluster is master, the value is 1.
Verify that no policies are being created or modified on the current master cluster.
Export all policies from the current global policy master and then import them to the cluster you will promote to global policy master.
Demote the original global policy master cluster to a member, by setting cldb.pbs.global.master to 0.
Promote the member cluster to global policy master by setting cldb.pbs.global.master to 1.