Show Table of Contents
Chapter 13. Managing Red Hat Gluster Storage Volume Life-Cycle Extensions
Red Hat Gluster Storage allows automation of operations by user-written scripts. For every operation, you can execute a pre and a post script.
Pre Scripts: These scripts are run before the occurrence of the event. You can write a script to automate activities like managing system-wide services. For example, you can write a script to stop exporting the SMB share corresponding to the volume before you stop the volume.
Post Scripts: These scripts are run after execution of the event. For example, you can write a script to export the SMB share corresponding to the volume after you start the volume.
You can run scripts for the following events:
- Creating a volume
- Starting a volume
- Adding a brick
- Removing a brick
- Tuning volume options
- Stopping a volume
- Deleting a volume
While creating the file names of your scripts, you must follow the naming convention followed in your underlying file system like XFS.
To enable the script, the name of the script must start with an S . Scripts run in lexicographic order of their names.
13.1. Location of Scripts
This section provides information on the folders where the scripts must be placed. When you create a trusted storage pool, the following directories are created:
After creating a script, you must ensure to save the script in its respective folder on all the nodes of the trusted storage pool. The location of the script dictates whether the script must be executed before or after an event. Scripts are provided with the command line argument
--volname=VOLNAMEto specify the volume. Command-specific additional arguments are provided for the following volume operations:
- Start volume
--first=yes, if the volume is the first to be started
--first=no, for otherwise
- Stop volume
--last=yes, if the volume is to be stopped last.
--last=no, for otherwise
- Set volume
-o key=valueFor every key, value is specified in volume set command.