Configuring the Feature

Scenario 1: Ceph/HDFS Access Configuration (Mandatory)

When the OmniData service is started, the HDFS/Ceph configuration file needs to be read. You need to upload the hdfs-site.xml and core-site.xml configuration files to the etc directory of OmniData. You can search for the files on the ceph1/hdfs1, ceph2/hdfs2, and ceph3/hdfs3 nodes in the etc/hadoop/ directory in the Hadoop installation directory.

You can add file transfer operations, as shown in Table 1. Using Ceph as an example, transfer hdfs-site.xml in the local path to /home/omm/omnidata-install/omnidata/etc/ of the selected servers (ceph1, ceph2, and ceph3). The method of uploading the core-site.xml file is the same.

To access Ceph, you need to prepare multiple dependencies on offload nodes (ceph1 to ceph3).

1. Upload hdfs-ceph-3.2.0.jar and librgw_jni.so to the server using SmartKit and ensure that they can be loaded by HAF.
2. Copy the keyring file on any of the nodes (agent1 to agent3) to the same path (default path: /var/lib/ceph/radosgw/ceph-admin/keyring) on ceph1 to ceph3.
3. On ceph1 to ceph3, check the keyring permission: chmod -R 755 /var/lib/ceph;chmod 644 keyring

Scenario 2: OmniData Native Configuration (Mandatory for OmniData Native)

Add the following configuration to /home/omm/omnidata-install/omnidata/etc/config.properties on offload nodes.

1. Go to the directory where the config.properties file is stored and edit the configuration file.

   1 2	cd /home/omm/omnidata-install/omnidata/etc vi config.properties

2. Press i to enter the insert mode and add the following content to the file:

   1 2 3

   operator.combine.enabled=true operator.lib.path=/opt/omni-operator/lib dynamic.lib.path=/usr/local/lib/HMPP

   In the preceding file, operator.lib.path indicates the absolute path of the lib directory of OmniOperator. dynamic.lib.path is the default installation path of the OmniOperator dynamic libraries.

   

   Native logs can be viewed only when the log level is DEBUG. To view native logs, change the log level of /home/omm/omnidata-install/omnidata/etc/logback.xml to DEBUG. Example:

   1 2 3 4

   <!-- L0G LEVEL --> <root level="DEBUG"> <appender-ref ref="FILE" /> </root>

3. Press Esc, type :wq!, and press Enter to save the file and exit.

Scenario 3: Kerberos Configuration (When HDFS and ZooKeeper in the Cluster Are in Secure Mode)

Add the following configuration to /home/omm/omnidata-install/omnidata/etc/config.properties on offload nodes. Copy related configuration files (krb5.conf, hdfs.keytab, and client_jass.conf) to the etc directory.

1. Configure Kerberos and copy related configuration files to the specified directory.
   1. Go to the directory where the config.properties file is stored and edit the configuration file.

      1 2	cd /home/omm/omnidata-install/omnidata/etc vi config.properties

   2. Press i to enter the insert mode and add the following content to the file:

      hdfs.authentication.type=KERBEROS
      hdfs.krb5.conf.path=/home/omm/omnidata-install/omnidata/etc/krb5.conf
      hdfs.krb5.keytab.path=/home/omm/omnidata-install/omnidata/etc/hdfs.keytab
      hdfs.krb5.principal=hdfs/server1@EXAMPLE.COM

   3. Press Esc, type :wq!, and press Enter to save the file and exit.
   4. Copy related configuration files to the specified directory.

      cp xxx/krb5.conf /home/omm/omnidata-install/omnidata/etc/
      cp xxx/hdfs.keytab /home/omm/omnidata-install/omnidata/etc/

2. Configure a secure ZooKeeper connection.

   zookeeper.krb5.enabled=true
   zookeeper.java.security.auth.login.config=/home/omm/omnidata-install/omnidata/etc/client_jaas.conf
   zookeeper.krb5.conf=/home/omm/omnidata-install/omnidata/etc/krb5.conf
   cp xxx/client_jaas.conf /home/omm/omnidata-install/omnidata/etc/
   cp xxx/krb5.conf /home/omm/omnidata-install/omnidata/etc/

3. Grant permission on the configuration file directory. In the following command, omm is the current HAF installation user. Replace it with the actual user.

   chown omm /home/omm/omnidata-install/omnidata/etc/*

• The italic part in the preceding commands needs to be modified based on the actual paths in the cluster environment.
• Replace the zookeeper-xxx.jar package in the /home/omm/omnidata-install/omnidata/lib directory with the ZooKeeper package to be used in your environment.