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 mapping 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 to it.
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, select the type of object store, and update the relevant parameters. Select one of the following tabs according to the object store type you choose. For details, see the parameter descriptions in the topic.
It is not mandatory to set the Access Key and Secret Key in the Edit Object Store dialog in AWS. The AWS object store type is accessed from the WEKA EC2 instances to the object store and granted by the IAM roles assigned to the instances.
Add object store buckets to be used for tiering or snapshots.
Procedure
From the menu, select Manage > Object Stores.
Select the +Create button.
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: AWS, AZURE, or OTHER (for GCP and others).
Buckets Default Parameters: Select one of the following tabs according to the object store type you choose.
WEKA supports the following options for creating AWS S3 buckets:
AWS S3 bucket creation for WEKA cluster on EC2.
AWS S3 bucket creation for WEKA cluster not on EC2 using .
Set the following:
Protocol and Port: Select the protocol to use when connecting to the bucket.
Bucket: Set the name of the bucket to store and access data.
Region: Set the region assigned to work with.
For AWS S3 bucket creation for WEKA cluster on EC2: If the WEKA EC2 instances have the required permissions granted by the IAM role, then it is not required to provide the Access Key and Secret Key. Otherwise, set the Access Key and Secret Key of the user granted with read/write access to the bucket.
For AWS S3 bucket creation for WEKA cluster not on EC2 using STS:
Select Enable AssumeRole API.
Role Session Name: Set a unique for the assumed role session.
Session Duration: Set the duration of the temporary security credentials in seconds.
Possible values: 900 - 43200 (default 3600).
Access Key and Secret Key: Set the keys of the user granted with the AssumeRole permissions.
When creating 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.
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.
To validate the connection to the object store bucket, select Validate.
Select Create.
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 it exists).
Procedure
From the menu, select Manage > Object Stores.
The following example shows two object store buckets.
You can modify the object store bucket parameters according to your demand changes.
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.
In the Edit Object Store Bucket dialog, modify the details, and select Update.
For active object store buckets connected to filesystems, the system tracks this activity and provides details about each activity on the Bucket Operations page.
The details include the operation type (download or upload), start time, execution time, previous attempts results, cURL errors, and more.
Procedure
From the menu, select Manage > Object Stores.
Select the three dots on the right of the object store bucket you want to show its recent operation, and select Show Recent Operations.
The recent operations page for the selected object store bucket appears. To focus on specific operations, you can sort the columns and use the filters that appear on the top of the columns.
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.
If you select Enable AssumeRole API, set also the Role ARN and Role Session Name. For details, see the topic.
Role ARN: Set the Amazon Resource Name (ARN) to assume. The ARN must have the equivalent permissions defined in the IAM role for S3 access. See .
Enable Upload Tags: Whether to enable or not.
