The page has been translated by Gen AI.

Install Agent

To use the Parallel File Storage service, you need to connect to the target server and install the Agent. After installing the Agent, mount on the server and use Parallel File Storage.

Install Agent and Connect to Server (Mount)

Agent installation and server connection consist of six steps. Follow the next procedure.

  1. Agent installation
  2. Account Login
  3. Mount Point Creation
  4. Filesystem Mount
  5. Mount check
  6. fstab registration

Agent Installation

Install the Agent using Mount IP.

Reference
Mount IP can be found in the Mount name item on the detail page of the Samsung Cloud Platform Console.
  1. All Services > Storage > Parallel File Storage Click the menu. Go to the Service Home page of Parallel File Storage.
  2. Click the Parallel File Storage menu on the Service Home page. Navigate to the Parallel File Storage list page.
  3. Parallel File Storage List page, click the resource to be used on the connected server. Move to the Parallel File Storage Details page.
  4. Connection Server After checking the server in the item, please connect.
  5. Refer to the following example to install the Volume Agent and proceed with server connection (Mount).
curl <Mount IP>:14000/dist/v1/install | sh
root@RESD-s4sr3h:/# curl http://10.102.160.254:14000/dist/v1/install | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1424  100  1424    0     0  1978k      0 --:--:-- --:--:-- --:--:-- 1390k
Downloading WekaIO CLI 4.2.4.29-hcsf
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 58.7M  100 58.7M    0     0  1079M      0 --:--:-- --:--:-- --:--:-- 1088M
Installing...
Installing agent of version 4.2.4.29-hcsf
The agent is configured to detect cgroups - cgroups v1 not found, cgroups are disabled
Waiting for agent service to be ready
Installation finished successfully
WekaIO CLI 4.2.4.29-hcsf is now installed


## Account Login

Log in using the mount information for server mount.



Reference
You can check the Mount name, Mount account, and password in the Mount information item of the detail page of Samsung Cloud Platform Console.

#weka user login -H root@RESD-s4sr3h:/# weka user login -H 10.102.160.254 Organization (enter name or ID, default: 0) admin_org Username: admin_reg Password: ########### +——————————+ | Login completed successfully | +——————————+


## Mount Point creation

Create a mount point on the server for the filesystem mount.

#mkdir /mnt/weka


## Filesystem Mount

Follow the steps below to mount the filesystem.

1. Use the #ip a command to check the IP and Interface Name information for Mount.

root@RESD-s4sr3h:/# ip a |grep 10.102 inet 10.102.160.248/23 brd 10.102.161.255 scope global ibs4f0.8010 inet 10.102.160.249/23 brd 10.102.161.255 scope global ibP1s8f0.8010


  

Note

The IP information and Interface Name that can be confirmed in the above example are as follows.

  • IP: 10.102.160.10, 10.102.160.11
  • Interface Name: ibs4f0.8010, ibP1s8f0.8010
2. Execute the mount command using the verified IP and Interface Name.

mount -t wekafs / -o net=//mask -o mgmt_ip= /mnt/weka root@RESD-s4sr3h:/# mount -t wekafs -o num_cores=8 -o net:ha=ibs4f0.8010,net:ha=ibP1s8f0.8010,mgmt_ip=‘10.102.160.10+10.102.160.11’ 10.102.160.254/wekafs /mnt/weka Mounting 10.102.161.254/bmtfs on /weka_fs Basing mount on container client Downloading [1/21] http://10.102.160.254:14000/dist/v1/image/envoy-fe-e6b882a6bce3c0de8cd9c7833df1a567.squashfs Downloading [2/21] http://10.102.160.254:14000/dist/v1/image/weka-driver-1.0.0-d10ca9cff59b98778b4314014569e00f.squashfs Downloading [3/21] http://10.102.160.254:14000/dist/v1/image/weka-driver-igb-uio-4.0.0-7eee7dc5b7f1d85a1be0e448d5e97312.squashfs Downloading [4/21] http://10.102.160.254:14000/dist/v1/image/container-s3-tmp-1.57f-9cb61c7e0ae3ca9e2b476c191e4e84ab.squashfs Downloading [5/21] http://10.102.160.254:14000/dist/v1/image/container-smbw-weka-4.7.12.3-9b67132a85a950260f048955dc33c7a9.squashfs Downloading [6/21] http://10.102.160.254:14000/dist/v1/image/weka-drain-tools-2d01044c641816d9002ca594a6ae9d90.squashfs Downloading [7/21] http://10.102.160.254:14000/dist/v1/image/container-ganesha-dev-weka-5-11becf16b21c9635daa23a247340a7bd.squashfs Downloading [8/21] http://10.102.160.254:14000/dist/v1/image/dependencies-1.0.0-9b64fdba87a4d6e6efa9ab5250169ec8.squashfs Downloading [9/21] http://10.102.160.254:14000/dist/v1/image/weka-container-2.3.0-be66bcc7c9739b15cacd910d7cac031e.squashfs Downloading [10/21] http://10.102.160.254:14000/dist/v1/image/weka-hostside-faf9aa30ec9ac7521ffbc9589ac23deb.squashfs Downloading [11/21] http://10.102.160.254:14000/dist/v1/image/api-6f501306831ff9a223a7f706c5a661e1.squashfs Downloading [12/21] http://10.102.160.254:14000/dist/v1/image/weka-s3-3508f2f1afb4900ab11c4772e327b1ac.squashfs Downloading [13/21] http://10.102.160.254:14000/dist/v1/image/weka-ganesha-5c6ef6d08e31f80580f50bab7d1b8134.squashfs Downloading [14/21] http://10.102.160.254:14000/dist/v1/image/dashboard-dfb78995154ab40fb274037ac9fe8a45.squashfs Downloading [15/21] http://10.102.160.254:14000/dist/v1/image/container-samba-weka-4.7.12.3-69835f740573b7ded6faed1dfe737bed.squashfs Downloading [16/21] http://10.102.160.254:14000/dist/v1/image/weka-smbw-8a1430e5f0f2cca6d2a4af603d630882.squashfs Downloading [17/21] http://10.102.160.254:14000/dist/v1/image/ui-1.0.0-5bc747765d326e6e1c3488285822f459.squashfs Downloading [18/21] http://10.102.160.254:14000/dist/v1/image/weka-samba-8102bcf3d3a81f02755cb2e75b1b8d16.squashfs Downloading [19/21] http://10.102.160.254:14000/dist/v1/image/weka-node-fbd17baa570969b6da7e5561f1eb652f.squashfs Downloading [20/21] http://10.102.160.254:14000/dist/v1/image/ofed-b643ca3e4fa06d84416d463afe74a66a.squashfs Downloading [21/21] http://10.102.160.254:14000/dist/v1/image/driver-uio-pci-generic-1.0.0-322a3daa84c41eeb6f0cafd0802fbf50.squashfs Finished getting version 4.2.4.29-hcsf Creating Weka container ‘client’ in version 4.2.4.29-hcsf Preparing version 4.2.4.29-hcsf of container client Base port was not explicitly provided, the container will use 14000 Applying resources Starting container ‘client’ Waiting for container ‘client’ to join cluster Container “client” is ready (pid = 392216) Calling the mount command Cgroups v1 not found, running without cgroups Mount completed successfully



## Mount Check

<code>#df -h</code> Run the command to check the mount status of the filesystem.
root@RESD-s4sr3h:/# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           202G  3.8M  202G   1% /run
/dev/nvme2n1p2  3.5T   37G  3.3T   2% /
tmpfs          1008G     0 1008G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/nvme2n1p1  511M  6.1M  505M   2% /boot/efi
tmpfs           202G  4.0K  202G   1% /run/user/0
/dev/loop0      2.0G   47M  2.0G   3% /opt/weka/logs
tmpfs          1008G   12K 1008G   1% /opt/weka/data/agent/tmpfss/cleanup
tmpfs          1008G  2.0G 1006G   1% /opt/weka/data/agent/tmpfss/client-persistent-tmpfs
tmpfs          1008G     0 1008G   0% /opt/weka/data/agent/tmpfss/cross-container-rpc-the-tmpfs
tmpfs          1008G  4.0K 1008G   1% /opt/weka/data/agent/tmpfss/cleanup_before_stop_and_delete
bmtfs           1.9T  537G  1.3T  29% /weka_fs

## fstab registration

Register fstab so that it automatically mounts on server reboot.<br>
To register fstab, run the <code>#vi /etc/fstab</code> command, then add the following command.

root@RESD-s4sr3h:/# cat /etc/fstab

/etc/fstab: static file system information.

Use ‘blkid’ to print the universally unique identifier for a

device; this may be used with UUID= as a more robust way to name devices

that works even if disks are added and removed. See fstab(5).

/ was on /dev/nvme2n1p2 during curtin installation

/dev/disk/by-uuid/8683a4fb-ee21-47c2-938e-2be0beea2089 / ext4 defaults 0 1

/boot/efi was on /dev/nvme2n1p1 during curtin installation

/dev/disk/by-uuid/92ED-55CC /boot/efi vfat defaults 0 1 /swap.imgnoneswapsw00 10.102.160.254/wekafs /mnt/weka wekafs num_cores=8,net:ha=ibs4f0.8010,net:ha=ibP1s8f0.8010,mgmt_ip=10.102.160.10+10.102.160.11,x-systemd.requires=wekaagent.service,x-systemd.mount-timeout=infinity,_net dev 0 0


# Disconnect server (Umount)

To disconnect the server, first connect to the server and perform the disconnect operation (Umount), then you must disconnect the server from the Console.<br>
To disconnect the server, follow the steps below.

1. **All Services > Storage > Parallel File Storage** Click the menu. Go to the **Service Home** page of Parallel File Storage.
2. Click the **Parallel File Storage** menu on the **Service Home** page. You will be taken to the **Parallel File Storage** list page.
3. **Parallel File Storage List** page, click the resource to disconnect the server. Move to the **Parallel File Storage Details** page.
4. **Connection Server** after checking the server information in the item, connect to the server.
5. Refer to the commands shown in the following example and proceed with the unmount operation (Umount).

umount /mnt/weka

vi /etc/fstab

Using Snapshots
File-level recovery