Chapter 11. Managing Containerized Red Hat Gluster Storage

With the Red Hat Gluster Storage 3.1 update 2 release, a Red Hat Gluster Storage service can be set up as a container on a Red Hat Enterprise Linux atomic host 7.2. Containers use the shared kernel concept and are much more efficient than hypervisors in system resource terms. Containers rest on top of a single Linux instance and allows applications to use the same Linux kernel as the system that they are running on. This improves the overall efficiency and reduces the space consumption considerably.
Containerized Red Hat Gluster Storage 3.1.2 is supported only on Red Hat Enterprise Linux Atomic Host 7.2. For more information about installing containerized Red Hat Gluster Storage, see the Red Hat Gluster Storage 3.1 Installation Guide.

Note

For Red Hat Gluster Storage 3.1.2, Erasure Coding, NFS-Ganesha, BitRot, and Data Tiering are not supported with containerized Red Hat Gluster Storage.

11.1. Prerequisites

Before creating a container, execute the following steps.
  1. Create the directories in the atomic host for persistent mount by executing the following command:
    # mkdir -p /etc/glusterfs /var/lib/glusterd /var/log/glusterfs
  2. Ensure the bricks that are required are mounted on the atomic hosts. For more information see, Brick Configuration.
  3. If Snapshot is required, then ensure that the dm-snapshot kernel module is loaded in Atomic Host system. If it is not loaded, then load it by executing the following command:
    # modprobe dm_snapshot