Mounting ZebClient with Azure Blob Storage

Step 1: Download and Install ZebClient CLI

Run the following command to download and install the ZebClient CLI on the Linux machine (in the cloud or on-premise) you want to use the filesystem with where the user has granted permission to use the sudo command:

curl -s https://zebclient-deployment.s3.eu-west-1.amazonaws.com/zc-cli/install-zc-cli.sh | bash

This machine should be in the same whitelisted public address as provided earlier during the deployment of the Terraform script.

After installation, you should see the message "The installation of zc-cli is completed!".

Step 2: Deploy an Agent Node

To start the ZebClient CLI, run:

zc-cli

1. Choose option 1 for "Agent and server operation".

2. In the sub-menu, choose option 1 for "Install ZebClient agent locally".

3. Select Azure as your cloud provider

4. Enter the required information (all required information can be found in Terraform Output)

5. Enter the local directory where you want to mount ZebClient (default is /zcfs).

6. Confirm the installation by entering 'Y' when prompted.

When you are providing value for the Azure container name, it is important to provide just the container name which is: zc{your prefix}

The script will download the ZebClient binary. You should see a progress bar indicating the download process.

zebclient-linux-amd64         100%[================================================>]  44.99M  25.1MB/s    in 1.8s

Step 3: Verify ZCFS Filesystem

After successful installation, you will see the following message:

ZCFS filesystem is now up and running!
ZebClient version: v2.2

Exit ZebClient CLI and verify ZCFS mount point:

mount | grep zebclient

You should see a line indicating the ZCFS mount point.

user@host:/zcfs$ mount | grep zebclient
ZCFS:zebclient on /zcfs type fuse.zcfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other)

Next Step

ZebClient is now ready to connect to your applications. If you wish to add remote agents to access this filesystem, please proceed to Mount additional agent.

This is a first-step deployment that allows you to access the filesystem, use Mount additional agent to expand your cluster for your production environment or refer to the Tuning section for advanced solutions.