Chapter 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 and create an environment file with the following contents:


  ManilaNetappLogin: 'NETAPP_USER'  # 1
  ManilaNetappPassword: 'NETAPP_USER_PASSWORD'
  ManilaNetappServerHostname: 'HOSTNAME' # 2
  ManilaNetappVserver: 'SVM' # 3
  ManilaNetappRootVolumeAggr: 'ROOTVAGGR' # 4
  ManilaNetappTraceFlags: 'TRFLAGS' # 5
  ManilaNetappDriverHandlesShareServers: 'false' # 6

Replace NETAPP_USER and NETAPP_USER_PASSWORD with the credentials of the administrative account used to access the storage system (specifically, HOSTNAME).
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.
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).
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. This parameter is required if the value of ManilaNetappDriverHandlesShareServers is set to true, which means the driver manages the life cycle of share servers. This value is not required if the value of ManilaNetappDriverHandlesShareServers is `false`.
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 include method and api.
The ManilaNetappDriverHandlesShareServers parameter sets whether the driver should handle the lifecycle of the share server (false means it should not).

For example:


   ManilaNetappLogin: 'netapp_user'
   ManilaNetappPassword: 'netapp_user_password'
   ManilaNetappServerHostname: ''
   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.