Manage object stores using the CLI
This page describes how to view and manage object stores using the CLI.
Using the CLI, you can perform the following actions:
View object stores
Command: weka fs tier obs
Use this command to view information on all the object stores configured to the WEKA system.
Using the GUI, only object store buckets are present. Adding an object store bucket only adds to the present local
or remote
object store. If more than one is present (such as during the time recovering from a remote snapshot), use the CLI.
Edit an object store
Command: weka fs tier obs update
Use the following command line to edit an object store:
weka fs tier obs update <name> [--new-name new-name] [--site site] [--hostname=<hostname>] [--port=<port>] [--auth-method=<auth-method>] [--region=<region>] [--access-key-id=<access-key-id>] [--secret-key=<secret-key>] [--protocol=<protocol>] [--bandwidth=<bandwidth>] [--download-bandwidth=<download-bandwidth>] [--upload-bandwidth=<upload-bandwidth>] [--remove-bandwidth=<remove-bandwidth>] [--max-concurrent-downloads=<max-concurrent-downloads>] [--max-concurrent-uploads=<max-concurrent-uploads>] [--max-concurrent-removals=<max-concurrent-removals>] [--enable-upload-tags=<enable-upload-tags>]
Parameters
Parameter | Description |
---|---|
| Name of the object store to create. |
| New name for the object store. |
| Site location of the object store.
Possible values:
|
| Object store host identifier (hostname or IP address) to use as a default for added buckets. |
| Object store port, to be used as a default for added buckets. |
| Authentication method to use as a default for added buckets.
Possible values: |
| Region name to use as a default for added buckets. |
| Object store access key ID to use as a default for added buckets. |
| Object store secret key to use as a default for added buckets. |
| Protocol type to use as a default for added buckets.
Possible values: |
| Bandwidth limitation per core (Mbps). |
| Object store download bandwidth limitation per core (Mbps). |
| Object store upload bandwidth limitation per core (Mbps). |
| A bandwidth (Mbps) to limit the throughput of delete requests sent to the object store. Setting a bandwidth equal to or lower than the object store deletion throughput prevents an increase in the object store deletions queue. |
| Maximum number of downloads concurrently performed on this object store in a single IO node.
Possible values: |
| Maximum number of uploads concurrently performed on this object store in a single IO node.
Possible values: |
| Maximum number of removals concurrently performed on this object store in a single IO node.
Possible values: |
| Determines whether to enable object-tagging or not. To use as a default for added buckets.
Possible values: |
View object store buckets
Command: weka fs tier s3
Use this command to view information on all the object store buckets configured to the WEKA system.
Add an object store bucket
Command: weka fs tier s3 add
Use the following command line to add an S3 object store:
weka fs tier s3 add <name> [--site site] [--obs-name obs-name] [--hostname=<hostname>] [--port=<port> [--bucket=<bucket>] [--auth-method=<auth-method>] [--region=<region>] [--access-key-id=<access-key-id>] [--secret-key=<secret-key>] [--protocol=<protocol>] [--bandwidth=<bandwidth>] [--download-bandwidth=<download-bandwidth>] [--remove-bandwidth=<remove-bandwidth>] [--upload-bandwidth=<upload-bandwidth>] [--errors-timeout=<errors-timeout>] [--prefetch-mib=<prefetch-mib>] [--enable-upload-tags=<enable-upload-tags>] [--max-concurrent-downloads=<max-concurrent-downloads>] [--max-concurrent-uploads=<max-concurrent-uploads>] [--max-concurrent-removals=<max-concurrent-removals>] [--max-extents-in-data-blob=<max-extents-in-data-blob>] [--max-data-blob-size=<max-data-blob-size>] [--sts-operation-type=<sts-operation-type>] [--sts-role-arn=<sts-role-arn>] [--sts-role-session-name=<sts-role-session-name>] [--sts-session-duration=<sts-session-duration>]
Parameters
Name | Description | Default |
---|---|---|
| Name of the object store to edit. | |
|
|
|
| Name of the existing object store to add this object store bucket to. | If there is only one object store of type mentioned in |
| Object store host identifier or IP. Mandatory, if not specified at the object store level. | The |
| A valid object store port. | The |
| A valid object store bucket name. | |
| Authentication method.
Possible values: | The |
| Region name. Mandatory, if not specified in the object store level . | The |
| Object store bucket access key ID. Mandatory, if not specified in the object store level (can be left empty when using IAM role in AWS or GCP). | The |
| Object store bucket secret key. Mandatory, if not specified in the object store level (can be left empty when using IAM role in AWS or GCP). | The |
| Protocol type to be used.
Possible values: | The |
| Bucket bandwidth limitation per core (Mbps). | |
| Bucket download bandwidth limitation per core (Mbps) | |
| Bucket upload bandwidth limitation per core (Mbps) | |
| A bandwidth (Mbps) to limit the throughput of delete requests sent to the object store. Setting a bandwidth equal to or lower than the object store deletion throughput prevents an increase in the object store deletions queue. | |
| If the object store link is down longer than this timeout period, all IOs that need data return an error.
Possible values: |
|
| The data size (MiB) to prefetch when reading a whole MiB on the object store. |
|
| Whether to enable object-tagging or not.
Possible values: |
|
| Maximum number of downloads we concurrently perform on this object store in a single IO node. Possible values: | |
| Maximum number of uploads we concurrently perform on this object store in a single IO node. Possible values: | |
| Maximum number of removals we concurrently perform on this object store in a single IO node. Possible values: | |
| Maximum number of extents' data to upload to an object store data blob. | |
| Maximum size to upload to an object store data blob. Format: capacity in decimal or binary units: 1B, 1KB, 1MB, 1GB, 1TB, 1PB, 1EB, 1KiB, 1MiB, 1GiB, 1TiB, 1PiB, 1EiB. | |
| AWS operation type to use. Possible values: |
|
| The Amazon Resource Name (ARN) of the role to assume. Mandatory when setting | |
| A unique identifier for the assumed role session. The length must be between 2 and 64 characters. Allowed characters include alphanumeric characters (upper and lower case), underscore (_), equal sign (=), comma (,), period (.), at symbol (@), and hyphen (-). Space is not allowed. | |
| The duration of the temporary security credentials in seconds. Possible values: |
|
When using the CLI, by default a misconfigured object store are not created. To create an object store even when it is misconfigured, use the --skip-verification
option.
The max-concurrent
settings are applied per WEKA compute process and the minimum setting of all object stores is applied.
When you create the object store bucket in AWS, to use the storage classes: S3 Intelligent-Tiering, S3 Standard-IA, S3 One Zone-IA, and S3 Glacier Instant Retrieval, do the following:
Create the bucket in S3 Standard.
Create an AWS lifecycle policy to transition objects to these storage classes.
Make the relevant changes and click Update to update the object store bucket.
Edit an object store bucket
Command: weka fs tier s3 update
Use the following command line to edit an object store bucket:
weka fs tier s3 update <name> [--new-name=<new-name>] [--new-obs-name new-obs-name] [--hostname=<hostname>] [--port=<port> [--bucket=<bucket>] [--auth-method=<auth-method>] [--region=<region>] [--access-key-id=<access-key-id>] [--secret-key=<secret-key>] [--protocol=<protocol>] [--bandwidth=<bandwidth>] [--download-bandwidth=<download-bandwidth>] [--upload-bandwidth=<upload-bandwidth>] [--remove-bandwidth=<remove-bandwidth>] [--errors-timeout=<errors-timeout>] [--prefetch-mib=<prefetch-mib>] [--enable-upload-tags=<enable-upload-tags>] [--max-concurrent-downloads=<max-concurrent-downloads>] [--max-concurrent-uploads=<max-concurrent-uploads>] [--max-concurrent-removals=<max-concurrent-removals>] [--max-extents-in-data-blob=<max-extents-in-data-blob>] [--max-data-blob-size=<max-data-blob-size>] [--sts-operation-type=<sts-operation-type>] [--sts-role-arn=<sts-role-arn>] [--sts-role-session-name=<sts-role-session-name>] [--sts-session-duration=<sts-session-duration>]
Parameters
Name | Value |
---|---|
| A valid name of the object store bucket to edit. |
| New name for the object store bucket |
| A new object store name to add this object store bucket to. It must be an existing object store with the same |
| Object store host identifier or IP. |
| A valid object store port |
| A valid object store bucket name |
| Authentication method.
Possible values: |
| Region name |
| Object store bucket access key ID |
| Object store bucket secret key |
| Protocol type to be used.
Possible values: |
| Bandwidth limitation per core (Mbps) |
| Bucket download bandwidth limitation per core (Mbps) |
| Bucket upload bandwidth limitation per core (Mbps) |
| A bandwidth (Mbps) to limit the throughput of delete requests sent to the object store. Setting a bandwidth equal to or lower than the object store deletion throughput prevents an increase in the object store deletions queue. |
| If the object store link is down longer than this timeout period, all IOs that need data return an error.
Possible values: |
| The data size in MiB to prefetch when reading a whole MiB on the object store |
| Whether to enable object-tagging or not.
Possible values: |
| Maximum number of downloads we concurrently perform on this object store in a single IO node. Possible values: |
| Maximum number of uploads we concurrently perform on this object store in a single IO node. Possible values: |
| Maximum number of removals we concurrently perform on this object store in a single IO node. Possible values: |
| Maximum number of extents' data to upload to an object store data blob. |
| Maximum size to upload to an object store data blob. Format: capacity in decimal or binary units: 1B, 1KB, 1MB, 1GB, 1TB, 1PB, 1EB, 1KiB, 1MiB, 1GiB, 1TiB, 1PiB, 1EiB. |
| AWS operation type to use. Possible values: |
| The Amazon Resource Name (ARN) of the role to assume. Mandatory when setting |
| A unique identifier for the assumed role session. The length must be between 2 and 64 characters. Allowed characters include alphanumeric characters (upper and lower case), underscore (_), equal sign (=), comma (,), period (.), at symbol (@), and hyphen (-). Space is not allowed. |
| The duration of the temporary security credentials in seconds. Possible values: |
List recent operations of an object store bucket
Command: weka fs tier ops
Use the following command line to list the recent operations running on an object store:
weka fs tier ops <name> [--format format] [--output output]...[--sort sort]...[--filter filter]...[--raw-units] [--UTC] [--no-header] [--verbose]
Parameters
Name | Value | Default |
---|---|---|
| A valid object store bucket name to show its recent operations. | |
| Specify the output format.
Possible values: |
|
| Specify the columns in the output.
Possible values:
| All columns |
| Specify the column(s) to consider when sorting the output. For the sorting order, ascending or descending, add - or + signs respectively before the column name. | |
| Specify the values to filter by in a specific column. Usage: | |
| Print values in a readable format of raw units such as bytes and seconds.
Possible value examples: | |
| Don't show column headers in the output, | |
| Show all columns in the output. |
Delete an object store bucket
Command: weka fs tier s3 delete
Use the following command line to delete an object store bucket:
weka fs tier s3 delete <name>
Parameters
Name | Value |
---|---|
| A valid name of the object store bucket to delete. |