NetApp Back End Guide for the Shared File System Service
Deploying Multiple NetApp Back Ends for the Shared File System Service in a Red Hat OpenStack Platform Overcloud
Abstract
1. Introduction
The OpenStack Shared File Systems service (openstack-manila) provides the means to easily provision shared file systems that can be consumed by multiple instances. In the past, OpenStack users needed to manually deploy shared file systems before mounting them on instances. The OpenStack Shared File Systems service, on the other hand, allows users to easily provision shares from a pre-configured storage pool, ready to be mounted securely. This pool, in turn, can be independently managed and scaled to meet demand.
This release supports the use of the NetApp unified driver (manila.share.drivers.netapp.common.NetAppDriver). This driver allows the Shared File System service to use NetApp storage controllers (running Data ONTAP) as a back end.
While you can manually configure the Shared File System service by directly editing its node’s /etc/manila/manila.conf file, any settings can be overwritten by the Red Hat OpenStack Platform director in future overcloud updates. As such, the recommended method for configuring a Shared File System back end is through the director. Doing so involves writing a custom environment file.
With this release, the director can now deploy the Shared File System with a NetApp back end on the overcloud. This document explains how to do so.
2. Requirements
The following sections assume that:
- A NetApp storage controller has already been deployed, and is ready to be used as a back end.
- You intend to only use one NetApp storage controller as a back end for your Shared File System service.
- You can use the director installation user account, which is created as part of the overcloud deployment. See Creating a Director Installation User (from Director Installation and Usage) for more information.
- The Shared File System service will still be installed on the Controller nodes, as is the default behavior.
This document will not discuss the different deployment configurations possible for your NetApp back end. Rather, to learn more about possible NetApp storage deployment configurations suitable for the Shared File System service, consult the upstream NetApp documentation (in particular, see Theory of Operation and Deployment Choices).
After mapping out your target configuration (as in, the settings you want for each NetApp back end), you can then translate your configuration to a custom environment file. The director will then use this file to orchestrate the configuration of your back ends, and make them persistent across overcloud updates.
3. Create the Environment File
The director already includes Heat templates to configure most of the necessary settings to integrate a NetApp back end. An environment file allows you to define settings specific to your deployment.
To start, log in as the stack user on the undercloud. Then, create an environment file with the following contents:
/home/stack/templates/netapp-config.yaml
parameter_defaults: ManilaNetappLogin: 'ADMIN' # 1 ManilaNetappPassword: 'ADMINPW' ManilaNetappServerHostname: 'HOSTNAME' # 2 ManilaNetappVserver: 'SVM' # 3 ManilaNetappRootVolumeAggr: 'ROOTVAGGR' # 4 ManilaNetappTraceFlags: 'TRFLAGS' # 5 ManilaNetappDriverHandlesShareServers: 'false' # 6
- 1
- Replace ADMIN and ADMINPW with the credentials of the administrative account used to access the storage system (specifically, HOSTNAME).
- 2
- Replace HOSTNAME with the storage system or proxy server. The value of this option should be the IP address or hostname of either the cluster management logical interface (LIF) or Storage Virtual Machine (SVM) LIF.
- 3
- SVM specifies the storage virtual machine (previously called a vserver) name on the storage cluster on which provisioning of shared file systems should occur. This parameter is required if the driver should operate without managing share servers (that is, be limited to the scope of a single SVM).
- 4
- ROOTVAGGR specifies the name of the aggregate upon which the root volume should be placed when a new storage virtual machine (SVM) is created to correspond to a Manila share server.
- 5
- Replace TRFLAGS with a comma-separated list of options that control which trace info is written to the Shared File System service logs when the debug level is set to
True. Supported values includemethodandapi. - 6
- The
ManilaNetappDriverHandlesShareServersparameter sets whether the driver should handle the lifecycle of the share server (falsemeans it should not).
For example:
/home/stack/templates/netapp-config.yaml
parameter_defaults: ManilaNetappLogin: 'admin' ManilaNetappPassword: 'netapp123' ManilaNetappServerHostname: '10.8.18.108' ManilaNetappVserver: 'vserver_1' ManilaNetappRootVolumeAggr: 'aggr1_n1' ManilaNetappTraceFlags: 'method,api' ManilaNetappDriverHandlesShareServers: 'false'
The next section describes how to use the /home/stack/templates/netapp-config.yaml environment file to orchestrate the configuration of your NetApp back end.
4. Deploy the Shared File System Service with NetApp Back Ends
Once you create /home/stack/templates/netapp-config.yaml, log in as the stack user on the undercloud. Then, deploy the configured back end by running:
$ source ~/stackrc $ openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/environments/manila-netapp-config.yaml -e /home/stack/templates/netapp-config.yaml
The /usr/share/openstack-tripleo-heat-templates/environments/manila-netapp-config.yaml used here is the environment file provided with the director for deploying NetApp back ends for the Shared File System service. The /home/stack/templates/netapp-config.yaml file we created in the previous section allows you to override the default settings to suit your deployment.
If you passed any extra environment files when you created the overcloud, pass them again here using the -e option to avoid making undesired changes to the overcloud. For more information, see Modifying the Overcloud Environment (from Director Installation and Usage).
