Configure the WekaFS plug-in for Manila

Configure a WEKA cluster as a Manila backend so that OpenStack can provision WEKA-backed shares.

Prepare the Manila server and add the WEKA backend to the Manila configuration. The Manila server is the Linux server that runs the manila-share service. It is not a WEKA storage server.

Before you begin

OpenStack Hibiscus (2026.2) or later is running.
A WEKA cluster is running.
The Manila server runs RHEL 8 or later, or Ubuntu 20.04 or later, with Python 3.9 or later.
The Manila server can reach the cluster on TCP port 14000 (REST API) and on the WEKA data network.

Verify network connectivity

On the Manila server, confirm that the cluster REST API responds. Replace <weka-ip> with the cluster management IP address.

   curl -k https://<weka-ip>:14000/api/v2/status

The response returns the cluster status as JSON. If the command reports a connection error, open TCP port 14000 between the Manila server and the cluster, and then retry. Do not continue until this command succeeds.

Install the WekaFS client (WekaFS shares only)

Skip this procedure if you use only the NFS protocol.

Download and install the client package from the cluster, so the client version matches the cluster version:

   curl -k -o weka-client.tar https://<weka-ip>:14000/dist/v1/install/<weka-version>
   tar xf weka-client.tar
   sudo ./install.sh

Load the kernel module, and confirm that it is loaded:

   sudo modprobe wekafsio
   lsmod | grep wekafsio

Persist the module across reboots:

   echo "wekafsio" | sudo tee /etc/modules-load.d/wekafs.conf

Create a dedicated API user

Create a dedicated WEKA user for Manila instead of using the admin account. This limits exposure if the credentials leak.

Create the user:

   weka user login admin "<weka-admin-password>" --hostname "<weka-ip>"
   weka user add manila-driver --password "<manila-user-password>" --role OrgAdmin

The OrgAdmin role grants permission to create and manage filesystems and organizations.

Confirm that the new credentials work:

   curl -k -X POST https://<weka-ip>:14000/api/v2/login \
     -H 'Content-Type: application/json' \
     -d '{"username":"manila-driver","password":"<manila-user-password>","org":"Root"}'

The response contains an access_token.

Configure the backend

Create the base directory for WekaFS mounts. Assign ownership to the user that runs the Manila share service:

   sudo mkdir -p /mnt/weka
   sudo chown manila:manila /mnt/weka

In /etc/manila/manila.conf, add weka to enabled_share_backends in the [DEFAULT] section, and then add the [weka] backend section:

ini

   [DEFAULT]
   enabled_share_backends = weka
   enabled_share_protocols = NFS,WEKAFS

   [weka]
   share_driver = manila.share.drivers.weka.driver.WekaShareDriver
   share_backend_name = weka
   driver_handles_share_servers = false

   # Feature flags
   snapshot_support = true
   create_share_from_snapshot_support = true
   revert_to_snapshot_support = true

   # Connection
   weka_api_server = <weka-ip>
   weka_api_port = 14000
   weka_ssl_verify = true

   # Authentication
   weka_username = manila-driver
   weka_password = <manila-user-password>
   weka_organization = Root

   # Filesystem settings
   weka_filesystem_group = default
   weka_share_name_prefix = manila_

   # WekaFS client on the Manila server
   weka_mount_point_base = /mnt/weka
   weka_num_cores = 1

   # NFS gateway (required for NFS shares and create share from snapshot)
   weka_nfs_server = <weka-nfs-interface-group-ip>

Set weka_nfs_server to the NFS interface group IP address, not the API server IP address. To find it, run weka nfs interface-group.

Restart the Manila share service, and confirm that it is running:

   sudo systemctl restart openstack-manila-share
   sudo systemctl status openstack-manila-share

Confirm that the backend is registered:

   openstack share pool list --detail
   openstack share service list

The WEKA backend appears in the pool list, and the manila-share service shows State: up. If the backend does not appear within two minutes, check the share service log.