8.1 Preparing Your Environment for CDF

1. Log in to the NFS server as root.

2. Create the following:

   • Group: arcsight with a GID 1999

   • User: arcsight with a UID 1999

   • NFS root directory: Root directory under which you can create all NFS shared directories.

     Example (NFS_Volume_Directory):/opt/NFS_Volume

3. (Conditional) If you have previously installed any version of CDF, you must remove all NFS directories using the following command for each directory:

   rm -rf <path to NFS directory>

   For example:

   rm -rf /opt/NFS_Volume/itom-vol

4. Create each NFS shared directory using the command:

   mkdir -p <path to NFS directory>

   For example:

   mkdir -p /opt/NFS_Volume/itom-vol

5. For each NFS directory, set the permission to 755 using the command:

   chmod -R 755 <path to NFS directory>

   For example:

   chmod -R 755 /opt/NFS_Volume/itom-vol

6. For each NFS directory, set the ownership to UID 1999 and GID 1999 using the command:

   chown -R 1999:1999 <path to NFS directory>

   For example:

   chown -R 1999:1999 /opt/NFS_Volume/itom-vol

   If you use a UID/GID other than 1999/1999, provide it during the CDF installation in the installation script arguments --system-group-id and --system-user-id.

1. For every node in the cluster, you must update the configuration to grant the node access to the NFS volume shares.

   For example:

   /opt/NFS_Volume/arcsight-vol 192.168.1.0/24(rw,sync,anonuid=1999,anongid=1999,all_squash)

   /opt/NFS_Volume/itom-vol 192.168.1.0/24(rw,sync,anonuid=1999,anongid=1999,all_squash)

   /opt/NFS_Volume/db-single-vol 192.168.1.0/24(rw,sync,anonuid=1999,anongid=1999,all_squash)

   /opt/NFS_Volume/itom-logging-vol 192.168.1.0/24(rw,sync,anonuid=1999,anongid=1999,all_squash)

   /opt/NFS_Volume/db-backup-vol 192.168.1.0/24(rw,sync,anonuid=1999,anongid=1999,all_squash)

2. Modify the /etc/exports file and run the following command:

   exportfs -ra

   If you add more NFS shared directories later, you must restart the NFS service.

1. Create the NFS directory under /mnt.

2. Mount the NFS directory on your local system by using the command:

   • NFS v3: mount -t nfs 192.168.1.25:/opt/NFS_Volume/arcsight-vol /mnt/nfs

   • NFS v4: mount -t nfs4 192.168.1.25:/opt/NFS_Volume/arcsight-vol /mnt/nfs

3. After creating all the directories, run the following commands on the NFS server:

   exportfs -ra

   systemctl restart rpcbind

   systemctl enable rpcbind

   systemctl restart nfs-server

   systemctl enable nfs-server

To set up NFS manually:

1. Copy setupNFS.sh to the NFS server.

   The setupNFS.sh file is located on the master node in the <download_directory>/esm-cmd-center-installer-for-fusion-x.x.x.x/installers/cdf-x.x.x.x/scripts folder.

2. (Conditional) If you are using the default UID/GID, use the command:

   sh setupNFS.sh <path_to_nfs_directory>/volumes/volume_name

3. (Conditional) If you are using a non-default UID/GID, use the command:

   sh setupNFS.sh <path_to_nfs_directory>/volumes/volume_name true <uid> <gid>

4. Restart the NFS service:

   systemctl restart nfs

1. Log in to the node.

2. Run the command:

   fdisk <name of the new disk device that was added>

   For example:

   # fdisk /dev/sdb1

3. Enter n to create a new partition.

4. When prompted, enter the partition number, sector, type (Linux LVM), and size for the first partition. To select the Linux LVM partition type:

   • Enter t to change the default partition type to Linux LVM

   • Type L to list the supported partition types

   • Type 8e to select the Linux LVM type

5. When prompted, enter the partition number, sector, type (Linux LVM), and size for the second partition.

6. Type p to view the partition table.

7. Type w to save the partition table to disk.

8. Type partprobe.

1. Create a physical volume with the following command:

   # pvcreate [physical device name]

   For example:

   # pvcreate /dev/sdb1

2. Create a volume group with the following command:

   # vgcreate [volume group name] [logical volume name]

   For example:

   # vgcreate docker /dev/sdb1

3. Create a logical volume (LV) for the thinpool and bootstrap with the following command:

   # lvcreate [logical volume name] [volume group name]

   For example, the data LV is 95% of the 'Docker' volume group size. (Leaving free space allows for automatic expanding of either the data or metadata if space is running low, as a temporary measure.)

   # lvcreate --wipesignatures y -n thinpool docker -l 95%VG

   # lvcreate --wipesignatures y -n thinpoolmeta docker -l 1%VG

4. Convert the pool to a thinpool with the following command:

   # lvconvert -y --zero n -c 512K --thinpool docker/thinpool --poolmetadata docker/thinpoolmeta

   Optionally, you can configure the auto-extension of thinpools using an lvm profile.

   1. Open the lvm profile.

   2. Specify a value for the parameters thin_pool_autoextend_threshold and thin_pool_autoextend_percent, each of which represents a percentage of the space used.

      For example:

      activation { thin_pool_autoextend_threshold=80 thin_pool_autoextend_percent=20 }

   3. Apply the lvm profile with the following command:

      # lvchange --metadataprofile docker-thinpool docker/thinpool

   4. Verify that the lvm profile is monitored with the following command:

      # lvs -o+seg_monitor

   5. Clear the graph driver directory with the following command, if Docker was previously started:

      # rm -rf /var/lib/docker/*

   6. Monitor the thinpool and volume group free space with the following commands:

      # lvs

      # lvs -a

      # vgs

   7. Check the logs to see the auto-extension of the thinpool when it hits the threshold:

      # journalctl -fu dm-event.service

1. Log in to the initial master node as the root user.

2. Open the /etc/sudoers file using Visudo.

3. Add the following Cmnd_Alias line to the command aliases group in the sudoers file:

   Cmnd_Alias CDFINSTALL = <CDF_installation_package_directory>/scripts/precheck.sh, <CDF_installation_package_directory>/install, <K8S_HOME>/uninstall.sh, /usr/bin/kubectl, /usr/bin/docker, /usr/bin/mkdir,/bin/rm, /bin/su, /bin/chmod, /bin/tar, <K8S_HOME>/scripts/uploadimages.sh,/bin/chown

   where

   • CDF_installation_package_directory represents the directory where you unzipped the installation package. For example:

     /tmp/cdf-2019.05.0xxx.

   • K8S_HOME represents the Kubernetes directory, by default /opt/arcsight/kubernetes.

4. Add the following lines to the wheel users group, replacing <username> with your sudo user password:

   %wheel ALL=(ALL) ALL

   cdfuser ALL=NOPASSWD: CDFINSTALL

   For example:

   Defaults: root !requiretty

5. Locate the secure_path line in the sudoers file and ensure that the following paths are present:

   Defaults secure_path = /sbin:/bin:/usr/sbin:/usr/bin

   By doing this, the sudo user can execute the showmount, curl, ifconfig, and unzip commands when installing CDF.

6. Save the file.

1. Log in to each master and worker node.

2. Open the /etc/sudoers file.

3. Add the following Cmnd_Alias line to the command aliases group in the sudoers file.

   Cmnd_Alias CDFINSTALL = /tmp/scripts/pre-check.sh, <ITOM_Suite_Foundation_Node>/install, <K8S_HOME>/uninstall.sh, /usr/bin/kubectl, /usr/bin/docker,/usr/bin/mkdir, /bin/rm, /bin/su, /bin/chmod, /bin/tar, <K8S_HOME>/scripts/uploadimages.sh, /bin/chown

   where

   • ITOM_Suite_Foundation_Node represents the directory where you unzipped the installation package. For example:

     /tmp/ITOM_Suite_Foundation_2019.05.0xxx

   • K8S_HOME represents the Kubernetes directory, by default /opt/arcsight/kubernetes.

4. Add the following lines to the wheel users group, replacing <username> with your sudo user password:

   %wheel ALL=(ALL) ALL

   cdfuser ALL=NOPASSWD: CDFINSTALL

   For example:

   Defaults: root !requiretty

5. Locate the secure_path line in the sudoers file and ensure that the following paths are present:

   Defaults secure_path = /sbin:/bin:/usr/sbin:/usr/bin

   By doing this, the sudo user can execute the showmount, curl, ifconfig, and unzip commands when installing CDF.

6. Save the file.