-
Notifications
You must be signed in to change notification settings - Fork 54
gluster_volume
Sachidananda Urs edited this page May 18, 2018
·
1 revision
Create, start, stop, delete, or configure GlusterFS volumes
- GlusterFS >= 4.0
| Parameter | Choices | Default value | Comments |
|---|---|---|---|
| name | Name of the GlusterFS volume. | ||
| state | present / absent / started / stopped | NONE | Create, delete, start, stop a volume |
| start_on_create | yes/no | yes | Whether to start the volume upon creation. |
| hosts | List of ip addresses or hostnames which will form the volume. Optionally each host can have a brick separated by a colon. For eg. 10.0.0.1:/mnt/brick. | ||
| bricks | List of comma separated bricks. If a single brick is present, the same brick name is used in all the hosts. If more than one brick is present then multiple bricks are used for every node. | ||
| force | yes / no | no | Force while starting/stopping/creating/deleting volume |
| transport | tcp / rdma / tcp,rdma | tcp | Transport type of the volume |
| replica_count | 2 / 3 | Replica count for creating a distributed replicate volume | |
| arbiter_count | Arbiter count for the volume | ||
| disperse_count | Disperse count for the volume | ||
| redundancy_count | Redundancy count for the disperse volume. | ||
| data_count | Disperse data count for the disperse volume. | ||
| add_brick | Add bricks to the volume. | ||
| remove_brick | Remove bricks from the cluster. | ||
| replace_brick | Replace bricks from the cluster. |
Options
- If options is specified, state can be one of present, started, stopped.
- If the state is present, the volume is created and options are set.
- If the state is started, the options are set on the volume and volume is started.
- If the state is stopped, the options are set and the volume is stopped.
Disperse
- If disperse_count is provided, disperse_redundancy and disperse_data are optional.
- If redundancy_count is provided then data_count is mandatory and disperse_count is optional.