Creating a Gluster Volume
Format
Method | POST |
---|---|
URL | /tasks/create |
Request contents | GlusterVolumeCreate Object |
Successful answer | TaskResult Object |
Unexpected error | HTTP 500 |
GlusterVolumeCreate Object
Schema
type | String | Task type identifier. In this case, "gvolume_create" |
---|---|---|
volume_id | String | Unique identifier for the new Gluster Volume |
image_storage_id | String | ID of the parent Image Storage |
gvolume_name | String | Name of the Gluster volume as seen by the OS. If it is the empty string, the volume will be named ${image_storage_id}_${volume_id} |
redundancy | String | Relation of the number of data bricks to redundant bricks. E.g. "2:1", "4:1", "1:1", etc... The following conditions must be met:
|
brick_paths | String Array | List of paths where bricks will be found in each host of the Image Storage. The resulting number of bricks of the volume is the length of this list times the number of hosts. Brick paths must:
|
JSON example
{ "type": "gvolume_create", "volume_id": "templates", Â "image_storage_id": "local", "gvolume_name": "", "redundancy": "2:1", "brick_paths": [ "/data/brick1", "/data/brick2", "/data/brick3" ] }