1. Ensure that the network cable is attached. The link indicator light on the network socket should be lit, even if the computer is not switched on.
2. Switch on the computer.
3. A menu screen appears. Press the number key that corresponds to the preferred option.

1. You must install Red Hat Gluster Storage Server 3.0.4 on the target server.

   Warning

   • For layered installation of Red Hat Gluster Storage, ensure to have only the default Red Hat Enterprise Linux server installation, without the Samba or CTDB packages installed from Red Hat Enterprise Linux.
   • The Samba version 3 is being deprecated from Red Hat Gluster Storage 3.0 Update 4. Further updates will not be provided for samba-3.x. It is recommended that you upgrade to Samba-4.x, which is provided in a separate channel or repository, for all updates including the security updates.
   • CTDB version 2.5 is not supported from Red Hat Gluster Storage 3.1 Update 2. To use CTDB in Red Hat Gluster Storage 3.1.2 and later, you must upgrade the system to CTDB 4.x, which is provided in the Samba channel of Red Hat Gluster Storage.
   • Downgrade of Samba from Samba 4.x to Samba 3.x is not supported.
   • Ensure that Samba is upgraded on all the nodes simultaneously, as running different versions of Samba in the same cluster will lead to data corruption.
2. Enable the channel where the Samba packages are available:
   For Red Hat Gluster Storage 3.2 on Red Hat Enterprise Linux 6.x

   1. If you have registered your machine using Red Hat Subscription Manager, enable the repository by running the following command:

      # subscription-manager repos --enable=rh-gluster-3-samba-for-rhel-6-server-rpms

   2. If you have registered your machine using Satellite server, enable the channel by running the following command:

      # rhn-channel --add --channel rhel-x86_64-server-6-rh-gluster-3-samba

   For Red Hat Gluster Storage 3.2 on Red Hat Enterprise Linux 7.x

   1. If you have registered your machine using Red Hat Subscription Manager, enable the repository by running the following command:

      # subscription-manager repos --enable=rh-gluster-3-samba-for-rhel-7-server-rpms

   2. If you have registered your machine using Satellite server, enable the channel by running the following command:

      # rhn-channel --add --channel rhel-x86_64-server-7-rh-gluster-3-samba

1. To install the basic Samba packages, execute the following command:

   # yum install samba

2. If you require the smbclient on the server, then execute the following command:

   # yum install samba-client

3. If you require an Active directory setup, then execute the following commands:

   # yum install samba-winbind
   # yum install samba-winbind-clients
   # yum install samba-winbind-krb5-locator

4. Verify if the following packages are installed.

   samba-libs
   samba-winbind-krb5-locator
   samba-winbind-modules
   samba-vfs-glusterfs
   samba-winbind
   samba-client
   samba-common
   samba-winbind-clients
   samba

1. If you have registered your machine using Red Hat Subscription Manager, enable the repository by running the following command:

   # subscription-manager repos 
   --enable=rh-gluster-3-nfs-for-rhel-6-server-rpms

2. If you have registered your machine using Satellite server, enable the channel by running the following command:

   # rhn-channel --add --channel 
   rhel-x86_64-server-6-rh-gluster-3-nfs

3. To subscribe to the HA channel, execute the following command:

   # rhn-channel --add --channel rhel-x86_64-server-ha-6

4. To add the HA repository, execute the following command:

   # subscription-manager repos --enable=rhel-6-server-rpms --enable=rhel-ha-for-rhel-6-server-rpms

1. If you have registered your machine using Red Hat Subscription Manager, enable the repository by running the following command:

   # subscription-manager repos 
   --enable=rh-gluster-3-nfs-for-rhel-7-server-rpms

2. If you have registered your machine using Satellite server, enable the channel by running the following command:

   # rhn-channel --add --channel 
   rhel-x86_64-server-7-rh-gluster-3-nfs

3. To subscribe to the HA channel, execute the following command:

   # rhn-channel --add --channel rhel-x86_64-server-ha-7

4. To add the HA repository, execute the following command:

   # subscription-manager repos --enable=rhel-7-server-rpms --enable=rhel-ha-for-rhel-7-server-rpms

1. While installing Red Hat Storage using an ISO, in the Customizing the Software Selection screen, select RH-Gluster-NFS-Ganesha and click Next.
2. Proceed with the remaining installation steps for installing Red Hat Gluster Storage. For more information on how to install Red Hat Storage using an ISO, see Installing from an ISO Image.

1. The glusterfs-ganesha package can be installed using the following command:

   # yum install glusterfs-ganesha

   NFS-Ganesha is installed along with the above package. nfs-ganesha-gluster and HA packages are also installed.

1. While installing Red Hat Storage using an ISO, in the Customizing the Software Selection screen, select Red Hat Storage Tools Group and click Optional Packages.
2. From the list of packages, select gstatus and click Close.
3. Proceed with the remaining installation steps for installing Red Hat Storage. For more information on how to install Red Hat Storage using an ISO, see Installing from an ISO Image.

1. You can verify the docker service is running with the following command:

   # systemctl status docker
   docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled)
   Active: active (running) since Fri 2017-01-22 12:03:34 CEST; 3h 19min ago
   Docs: http://docs.docker.com
   Main PID: 843 (docker)
   CGroup: /system.slice/docker.service
              └─843 /usr/bin/docker -d --selinux-enabled
   
   

2. Download the Red Hat Gluster Storage Container images from the Red Hat Docker Registry using the following command:

   # docker pull registry.access.redhat.com/rhgs3/rhgs-server-rhel7

3. Verify that you have a Red Hat Gluster Storage image on a Red Hat Enterprise Linux Atomic Host 7.2 by checking the contents of the /etc/redhat-release file. First, on the host system:

   # cat /etc/redhat-release
   Red Hat Enterprise Linux Atomic Host 7.3

4. And next, you can check the Red Hat Gluster Storage Container Image, again from the host system (no need to log into the container image):

   # docker run rhgs3/rhgs-server-rhel7 cat /etc/redhat-storage-release
   Red Hat Gluster Storage Server 3.1 Update 2 (Container)

Updating Red Hat Gluster Storage 3.2 in the offline mode

1. Make a complete backup using a reliable backup solution. This Knowledge Base solution covers one possible approach: https://access.redhat.com/solutions/1484053.
   If you use an alternative backup solution:
   • Ensure that you have sufficient space available for a complete backup.
   • Copy the .glusterfs directory before copying any data files.
   • Ensure that no new files are created on Red Hat Gluster Storage file systems during the backup.
   • Ensure that all extended attributes, ACLs, owners, groups, and symbolic and hard links are backed up.
   • Check that the backup restores correctly before you continue with the migration.
2. Delete the existing Logical Volume (LV) and recreate a new thinly provisioned LV. For more information, see https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/thinprovisioned_volumes.html
3. Restore backed up content to the newly created thinly provisioned LV.
4. When you are certain that your backup works, stop all volumes.

   # gluster volume stop volname

5. Run the following commands to stop gluster services and update Red Hat Gluster Storage in the offline mode:
   On Red Hat Enterprise Linux 6:

   # service glusterd stop
   # pkill glusterfs
   # pkill glusterfsd
   # yum update

   On Red Hat Enterprise Linux 7:

   # systemctl stop glusterd
   # pkill glusterfs
   # pkill glusterfsd
   # yum update

   Wait for the update to complete.
6. Start glusterd.
   On Red Hat Enterprise Linux 6:

   # service glusterd start

   On Red Hat Enterprise Linux 7:

   # systemctl start glusterd

7. When all nodes have been updated, run the following command to update the op-version of the cluster. This helps to prevent any compatibility issues within the cluster.

   # gluster volume set all cluster.op-version 31001

   Note

   31001 is the cluster.op-version value for Red Hat Gluster Storage 3.2.0. Refer to Section 1.5, “Supported Versions of Red Hat Gluster Storage” for the correct cluster.op-version value for other versions.
8. Start your volumes with the following command:

   # gluster volume start volname

9. If you had a meta volume configured prior to this upgrade, and you did not reboot as part of the upgrade process, mount the meta volume:

   # mount /var/run/gluster/shared_storage/

   If this command does not work, review the content of /etc/fstab and ensure that the entry for the shared storage is configured correctly and re-run the mount command. The line for the meta volume in the /etc/fstab file should look like the following:

   hostname:/gluster_shared_storage   /var/run/gluster/shared_storage/   glusterfs   defaults   0 0

10. If using NFS to access volumes, enable gluster-NFS using the following command:

    # gluster volume set volname nfs.disable off

    For example:

    # gluster volume set testvol nfs.disable off
    volume set: success

11. If you use geo-replication, restart geo-replication sessions when upgrade is complete.

    Important

    In Red Hat Gluster Storage 3.1 and higher, a meta volume is recommended when geo-replication is configured. However, when upgrading geo-replicated Red Hat Gluster Storage from version 3.0.x to 3.1.y, the older geo-replicated configuration that did not use shared volumes was persisted to the upgraded installation. Red Hat recommends reconfiguring geo-replication following upgrade to Red Hat Gluster Storage 3.2 to ensure that shared volumes are used and a meta volume is configured.

    To enable shared volumes, set the cluster.enable-shared-storage parameter to enable from the master node:

    # gluster volume set all cluster.enable-shared-storage enable

    Then configure geo-replication to use shared volumes as a meta volume by setting use_meta_volume to true.

    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL config use_meta_volume true

    For further information see the following sections in the Red Hat Gluster Storage 3.2 Administration Guide:

    • https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.2/html-single/Administration_Guide/index.html#chap-Managing_Red_Hat_Storage_Volumes-Shared_Volume
    • https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.2/html-single/Administration_Guide/index.html#chap-Managing_Geo-replication-Meta_Volume

    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start

    Note

    As a result of BZ#1347625, you may need to use the force parameter to successfully restart in some circumstances.

    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start force

Updating Red Hat Gluster Storage 3.2 in in-service mode

1. If you have a replicated configuration, perform these steps on all nodes of a replica set.
   If you have a distributed-replicated setup, perform these steps on one replica set at a time, for all replica sets.
2. Stop any geo-replication sessions.

   # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL stop

3. Verify that there are no pending self-heals:

   # gluster volume heal volname info

   Wait for any self-heal operations to complete before continuing.
4. Stop the gluster services on the storage server using the following commands:

   # service glusterd stop
   # pkill glusterfs
   # pkill glusterfsd

5. If you use Samba:
   1. Enable the required repository.
      On Red Hat Enterprise Linux 6.7 or later:

      # subscription-manager repos --enable=rh-gluster-3-samba-for-rhel-6-server-rpms

      On Red Hat Enterprise Linux 7:

      # subscription-manager repos --enable=rh-gluster-3-samba-for-rhel-7-server-rpms

   2. Stop the CTDB and SMB services across all nodes in the Samba cluster using the following command. Stopping the CTDB service also stops the SMB service.

      # service ctdb stop

      This ensures different versions of Samba do not run in the same Samba cluster.
   3. Verify that the CTDB and SMB services are stopped by running the following command:

      ps axf | grep -E '(ctdb|smb|winbind|nmb)[d]'

6. Update the server using the following command:

   # yum update

   Wait for the update to complete.
7. If a kernel update was included as part of the update process in the previous step, reboot the server.
8. If a reboot of the server was not required, then start the gluster services on the storage server using the following command:

   # service glusterd start

   Additionally, if you use Samba:
   1. Mount /gluster/lock before starting CTDB by executing the following command:

      # mount -a

   2. If the CTDB and SMB services were stopped earlier, then start the services by executing the following command.

      # service ctdb start

   3. To verify if the CTDB and SMB services have started, execute the following command:

      ps axf | grep -E '(ctdb|smb|winbind|nmb)[d]'

9. To verify that you have updated to the latest version of the Red Hat Gluster Storage server execute the following command and compare output with the desired version in Section 1.5, “Supported Versions of Red Hat Gluster Storage”.

   # gluster --version

10. Ensure that all bricks are online. To check the status, execute the following command:

    # gluster volume status

11. Start self-heal on the volume.

    # gluster volume heal volname

12. Ensure self-heal is complete on the replica using the following command:

    # gluster volume heal volname info

13. When all nodes in the volume have been upgraded, run the following command to update the op-version of the cluster. This helps to prevent any compatibility issues within the cluster.

    # gluster volume set all cluster.op-version 31001

    Note

    31001 is the cluster.op-version value for Red Hat Gluster Storage 3.2.0. Refer to Section 1.5, “Supported Versions of Red Hat Gluster Storage” for the correct cluster.op-version value for other versions.
14. If you had a meta volume configured prior to this upgrade, and you did not reboot as part of the upgrade process, mount the meta volume:

    # mount /var/run/gluster/shared_storage/

    If this command does not work, review the content of /etc/fstab and ensure that the entry for the shared storage is configured correctly and re-run the mount command. The line for the meta volume in the /etc/fstab file should look like the following:

    hostname:/gluster_shared_storage   /var/run/gluster/shared_storage/   glusterfs   defaults   0 0

15. If you use geo-replication, restart geo-replication sessions when upgrade is complete.

    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start

    Note

    As a result of BZ#1347625, you may need to use the force parameter to successfully restart in some circumstances.

    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start force