Manage object stores using the GUI
This page describes how to view and manage object stores using the GUI.
Last updated
This page describes how to view and manage object stores using the GUI.
Last updated
Using the GUI, you can perform the following actions:
Object store buckets can reside in different physical object stores. To achieve good QoS between the buckets, Weka requires to map the buckets to the physical object store.
You can edit the default local and remote object stores to meet your connection demands. When you add an object store bucket, you apply the relevant object store on the bucket.
Editing the default object store provides you with the following additional advantages:
Set restrictions on downloads from a remote object store. For on-premises systems where the remote bucket is in the cloud, to reduce the cost, you set a very low bandwidth for downloading from a remote bucket.
Ease of adding new buckets. You can set the connection parameters on the object store level and, if not specified differently, automatically use the default settings for the buckets you add.
Procedure
From the menu, select Manage > Object Stores.
On the left, select the pencil icon near the default object store you want to edit.
On the Edit Object Store dialog, set the following:
Type: Select the type of object store.
Buckets Default Parameters: Set the protocol, hostname, port, bucket folder, authentication method, region name, access key, and secret key.
The object store buckets are displayed on the Object Stores page. Each object store indicates the status, bucket name, protocol (HTTP/HTTPS), port, region, object store location (local or remote), authentication method, and error information (if exists).
Procedure
From the menu, select Manage > Object Stores.
The following example shows two object store buckets.
Add object store buckets to be used for tiering or snapshots.
Procedure
From the menu, select Manage > Object Stores.
Select the +Create button.
3. In the Create Object Store Bucket dialog, set the following:
Name: Enter a meaningful name for the bucket.
Object Store: Select the location of the object store. For tiering and snapshots, select the local object store. For snapshots only, select the remote object store.
Type: Select the type of object store.
Buckets Default Parameters: Set the protocol, hostname, port, bucket folder, authentication method, region name, access key, and secret key.
4. To validate the connection to the object store bucket, select Validate.
5. Optional: If your deployment requires a specific upload and download configuration, select Advanced, and set the parameters:
Download Bandwidth: Object store download bandwidth limitation per core (Mbps).
Upload Bandwidth: Object store upload bandwidth limitation per core (Mbps).
Max concurrent Downloads: Maximum number of downloads concurrently performed on this object store in a single IO node.
Max concurrent Uploads: Maximum number of uploads concurrently performed on this object store in a single IO node.
Max concurrent Removals: Maximum number of removals concurrently performed on this object store in a single IO node,
6. Select Create.
You can modify the object store bucket parameters according to your demand changes over time.
Procedure
From the menu, select Manage > Object Stores.
Select the three dots on the right of the object store you want to modify, and select Edit.
3. In the Edit Object Store Bucket dialog, modify the details, and select Update.
You can delete an object store bucket if it is no longer required. The data in the object store remains intact.
Procedure
From the menu, select Manage > Object Stores.
Select the three dots on the right of the object store bucket you want to delete, and select Remove.
To confirm the object store bucket deletion, select Yes.
Enable Upload Tags: Whether to enable or not.
