Hammerspace has been validated for use with Wasabi. To use this product with Wasabi, follow the instructions below.
Reference Architecture
Requirements
Anvil metadata node installed
Hammerspace DSX data node installed
An active Wasabi account
Wasabi bucket (see Bucket Creation Guide)
Access & Secret Key Pair (see Creating a User Account and Access Key)
Adding Wasabi as a Hammerspace Storage System
Log in to Hammerspace admin portal via browser https://:8443
Click Infrastructure.
Navigate to Storage Systems. Click Add Storage System.
In the Add Storage System dialog box, provide the following details and click Add Storage System.
Name—Provide a name for the Storage System.
Type—Select Wasabi Cloud Storage from the drop-down menu.
Access Key—Wasabi access key
Secret Key—Wasabi secret key
Endpoint—Endpoint URL of the Wasabi region where the bucket is located
Trust self-signed certificates—Optional
Use virtual host bucket signing—Optional
Use V4 auth signing—Leave empty
Proxy Host—Optional
Proxy Port—Optional
For information on the Wasabi service URLs, refer to our Service URLs for Wasabi's Storage Regions.
Creating a Volume
The Wasabi storage system created earlier will now be listed in the Storage Systems tab. Click + Volume in the column listing Wasabi.
In the Add Volumes wizard, under Selections, select the checkbox(es) for the Wasabi bucket(s) to add to Hammerspace. In this example, we are adding a single bucket, but it is just as simple to add multiple buckets at once if desired. Click Next Step .
In the Data tab, do not check Shared Volume. This must be empty unless creating a Hammerspace Global File System. Click Next Step.
Contact Hammerspace if you are configuring a Global File System.
Under Manage Capacity tab, select the desired capacity to limit the capacity, or choose Auto for unlimited capacity. Click Next Step, and the new volume will be created.
The new volume will be listed in the Volumes tab.
The next step is to create a share for SMB and NFS export.
Creating a Share
Click Share icon in the left navigation pane. Click Create Share.
The Create Share configuration window will open. From the Share Details tab, fill out the following information.
Name—Provide a name for the SMB.
NFS Export Path—Automatically filled out (from the Name form field above).
Max Share Size—Set the desired maximum size for the share.
Alert Threshold—Set a percentage-of-capacity trigger for alerting (soft quota).
Select NFS tab to view or edit additional configuration options. These are standard NFS configuration options. Click Update if making changes.
Export Subnet
Permissions
Root Squash
Secure Port
The SMB tab allows us to configure:
SMB Aliasing—The name must be unique across all shares.
SMB Alias Path—(Relative to the root of the share). Must begin with a forward slash (“/”).
Whether or not to make the Share browsable (checkbox).
Click Update if making changes.
Click Objectives. Click Add Objective. Select place-on-My-Wasabi from the Objective dropdown menu.
Click Add to apply the Objective. Click Close.
The name My-Wasabi was chosen in the section Adding Wasabi to Hammerspace. This name will vary depending on your configuration.
This objective will move data non-disruptively from another Storage System, Volume, Site, or Cloud to Wasabi.
To apply to existing shares, navigate to Shares from the left navigation pane. Click the edit pencil to the far right in the appropriate row corresponding to the share containing data to migrate to Wasabi.
This will open up the share configuration window (seen in previous images). Add the objective as directed in Step 5.
Alignment
Alignment is the term used to describe when data conforms with an objective. While data is moving an orange bar will be displayed.
In the Shares tab, by hovering over the Active Objectives column and row with our target share, the highlighted information displays, showing that our newly applied objective has taken effect.
We can also click on the Share itself and browse subfolders and files. The green color in the Alignment column tells us that the data has been aligned with its Objective. In other words, data has been moved to its declared destination (“place-on-My-Wasabi”).
