Creating a new share backend on the OpenStack controller node
A backend is an instance of the OpenStack Manila share service, which is defined in a section of the manila.conf file. Each backend has exactly one driver.
To create a new share backend va-share1 in OpenStack Manila, make the following changes on the OpenStack controller node, and restart the OpenStack Manila driver.
To create a new share backend on the OpenStack controller node
- On the OpenStack controller node, add the following configuration entries in the OpenStack Manila
/etc/manila/manila.conffile.In the DEFAULT section, add the following:
##### enabled_share_backends=va-share1 #####
If the entry generic1 is already there, add the va-share1 entry after a comma. For example:
enabled_share_backends = generic1,va-share1
At the end of all sections in the
/etc/manila/manila.conffile, add the following configuration entries:##### [va-share1] share_driver= manila.share.drivers.veritas.veritas_isa.VeritasShareDriver driver_handles_share_servers = False share_backend_name = va-share1 va_server_ip = 10.182.96.179 va_port = 14161 va_fstype = simple va_user = master va_pwd = password va_pool = pool1 #####
The following table describes the options.
share_backend_name
Name of the share backend. This name can be different for each share backend.
share_driver
OpenStack Manila driver name.
va_server_ip
Console IP address of the Access Appliance cluster.
va_port
14161
The port on Access Appliance to which the Manila driver is connected.
va_fstype
Type of file system to be created on the specified pool. It can be simple.
va_user
Root user name.
va_pwd
Root password.
va_pool
Existing storage pool on Access Appliance from which the file systems are to be created.
You use the OPENSTACK> manila configure command to display the configuration options that need to be performed on the OpenStack controller node.
- Restart the OpenStack Manila services.
The restart is on the OpenStack controller node, not on Access Appliance.