此内容没有您所选择的语言版本。
Chapter 3. Creating the NetApp back end environment file
The director already includes default heat templates that configure most of the necessary settings to integrate a NetApp back end. You can also use a custom environment file 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:
/home/stack/templates/netapp-config.yaml
- 1
- Replace NETAPP_USER and NETAPP_USER_PASSWORD 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. This value must 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, on the storage cluster where you want to provision shared file systems. This parameter is required if you want the driver to operate without managing share servers. That is, to be limited to the scope of a single SVM.
- 4
- ROOTVAGGR specifies the name of the aggregate where you want to place the root volume when a new storage virtual machine (SVM) is created to correspond to a manila share server. This parameter is required if you set the value of
ManilaNetappDriverHandlesShareServerstotrue, which means the driver manages the life cycle of share servers. This value is not required if the value ofManilaNetappDriverHandlesShareServersisfalse. - 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
- Set the
ManilaNetappDriverHandlesShareServersparameter totrueorfalseto enable or disable lifecycle management of the share server.
For example:
/home/stack/templates/netapp-config.yaml