The Dell EMC Shared File Systems service driver framework (EMCShareDriver) utilizes the Dell EMC storage products to provide the shared file systems to OpenStack. The Dell EMC driver is a plug-in based driver which is designed to use different plug-ins to manage different Dell EMC storage products.
The VMAX plug-in manages the VMAX to provide shared file systems. The EMC driver framework with the VMAX plug-in is referred to as the VMAX driver in this document.
This driver performs the operations on VMAX eNAS by XMLAPI and the file command line. Each back end manages one Data Mover of VMAX. Multiple Shared File Systems service back ends need to be configured to manage multiple Data Movers.
Enable Unicode on Data Mover.
The VMAX driver requires that the Unicode is enabled on Data Mover.
Warning
After enabling Unicode, you cannot disable it. If there are some file systems created before Unicode is enabled on the VMAX, consult the storage administrator before enabling Unicode.
To check the Unicode status on Data Mover, use the following VMAX eNAS File commands on the VMAX control station:
server_cifs <MOVER_NAME> | head
# MOVER_NAME = <name of the Data Mover>
Check the value of I18N mode field. UNICODE mode is shown as
I18N mode = UNICODE
.
To enable the Unicode for Data Mover, use the following command:
uc_config -on -mover <MOVER_NAME>
# MOVER_NAME = <name of the Data Mover>
Refer to the document Using International Character Sets on VMAX for File on EMC support site for more information.
Enable CIFS service on Data Mover.
Ensure the CIFS service is enabled on the Data Mover which is going to be managed by VMAX driver.
To start the CIFS service, use the following command:
server_setup <MOVER_NAME> -Protocol cifs -option start [=<n>]
# MOVER_NAME = <name of the Data Mover>
# n = <number of threads for CIFS users>
Note
If there is 1 GB of memory on the Data Mover, the default is 96 threads. However, if there is over 1 GB of memory, the default number of threads is 256.
To check the CIFS service status, use the following command:
server_cifs <MOVER_NAME> | head
# MOVER_NAME = <name of the Data Mover>
The command output will show the number of CIFS threads started.
NTP settings on Data Mover.
VMAX driver only supports CIFS share creation with share network which has an Active Directory security-service associated.
Creating CIFS share requires that the time on the Data Mover is in sync with the Active Directory domain so that the CIFS server can join the domain. Otherwise, the domain join will fail when creating a share with this security service. There is a limitation that the time of the domains used by security-services, even for different tenants and different share networks, should be in sync. Time difference should be less than 10 minutes.
We recommend setting the NTP server to the same public NTP server on both the Data Mover and domains used in security services to ensure the time is in sync everywhere.
Check the date and time on Data Mover with the following command:
server_date <MOVER_NAME>
# MOVER_NAME = <name of the Data Mover>
Set the NTP server for Data Mover with the following command:
server_date <MOVER_NAME> timesvc start ntp <host> [<host> ...]
# MOVER_NAME = <name of the Data Mover>
# host = <IP address of the time server host>
Note
The host must be running the NTP protocol. Only 4 host entries are allowed.
Configure User Mapping on the Data Mover.
Before creating CIFS share using VMAX driver, you must select a method of mapping Windows SIDs to UIDs and GIDs. DELL EMC recommends using usermapper in single protocol (CIFS) environment which is enabled on VMAX eNAS by default.
To check usermapper status, use the following command syntax:
server_usermapper <movername>
# movername = <name of the Data Mover>
If usermapper does not start, use the following command to start the usermapper:
server_usermapper <movername> -enable
# movername = <name of the Data Mover>
For a multiple protocol environment, refer to Configuring VMAX eNAS User Mapping on EMC support site for additional information.
Configure network connection.
Find the network devices (physical port on NIC) of the Data Mover that has access to the share network.
To check the device list, go to
.The following parameters need to be configured in the
/etc/manila/manila.conf
file for the VMAX driver:
emc_share_backend = vmax
emc_nas_server = <IP address>
emc_nas_password = <password>
emc_nas_login = <user>
emc_nas_server_container = <Data Mover name>
emc_nas_pool_names = <Comma separated pool names>
share_driver = manila.share.drivers.emc.driver.EMCShareDriver
emc_interface_ports = <Comma separated ports list>
The plug-in name. Set it to vmax
for the VMAX driver.
The control station IP address of the VMAX system to be managed.
The fields that are used to provide credentials to the VMAX system. Only local users of VMAX File is supported.
Name of the Data Mover to serve the share service.
Comma separated list specifying the name of the pools to be used by this back end. Do not set this option if all storage pools on the system can be used. Wild card character is supported.
Examples: pool_1, pool_*, *
Comma-separated list specifying the ports (devices) of Data Mover that can be used for share server interface. Do not set this option if all ports on the Data Mover can be used. Wild card character is supported.
Examples: spa_eth1, spa_*, *
Restart of the manila-share
service is needed for the configuration
changes to take effect.
The VMAX driver has the following restrictions:
active_directory
security
service should be unique even for different tenants.Configuration options specific to this driver are documented in Description of EMC share driver configuration options.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.