Chapter 3. Post-deployment configuration You must complete two post-deployment configuration tasks before you create NFS shares, grant user access, and mount NFS shares. Map the Networking service (neutron) StorageNFS network to the isolated data center Storage NFS network. You can omit this option if you do not want to isolate NFS traffic to a separate network. For more information, see Generating the custom roles file . Create the default share type. After you complete these steps, the tenant compute instances can create, allow access to, and mount NFS shares. 3.1. Creating the storage provider network You must map the new isolated StorageNFS network to a Networking (neutron) provider network. The Compute VMs attach to the network to access share export locations that are provided by the NFS-Ganesha gateway. For information about network security with the Shared File Systems service, see Hardening the Shared File Systems Service in the Security and Hardening Guide . Procedure The openstack network create command defines the configuration for the StorageNFS neutron network. From an undercloud node, enter the following command: On an undercloud node, create the StorageNFS network: You can enter this command with the following options: For the --provider-physical-network option, use the default value datacentre , unless you set another tag for the br-isolated bridge through NeutronBridgeMappings in your tripleo-heat-templates. For the --provider-segment option, use the VLAN value set for the StorageNFS isolated network in the heat template, /usr/share/openstack-tripleo-heat-templates/network_data_ganesha.yaml . This value is 70, unless the deployer modified the isolated network definitions. For the --provider-network-type option, use the value vlan . 3.2. Configure the shared provider StorageNFS network Create a corresponding StorageNFSSubnet on the neutron-shared provider network. Ensure that the subnet is the same as the storage_nfs network definition in the network_data.yml file and ensure that the allocation range for the StorageNFS subnet and the corresponding undercloud subnet do not overlap. No gateway is required because the StorageNFS subnet is dedicated to serving NFS shares. Prerequisites The start and ending IP range for the allocation pool. The subnet IP range. 3.2.1. Configuring the shared provider StorageNFS IPv4 network Create a corresponding StorageNFSSubnet on the neutron-shared IPv4 provider network. Procedure Log in to an overcloud node. Source your overcloud credentials. Use the example command to provision the network and make the following updates: Replace the start=172.17.0.4,end=172.17.0.250 IP values with the IP values for your network. Replace the 172.17.0.0/20 subnet range with the subnet range for your network. 3.2.2. Configuring the shared provider StorageNFS IPv6 network Create a corresponding StorageNFSSubnet on the neutron-shared IPv6 provider network. Procedure Log in to an overcloud node. Use the sample command to provision the network, updating values as needed. Replace the fd00:fd00:fd00:7000::/64 subnet range with the subnet range for your network. 3.3. Configuring a default share type You can use the Shared File Systems service (manila) to define share types that you can use to create shares with specific settings. Share types work like Block Storage volume types. Each type has associated settings, for example, extra specifications. When you invoke the type during share creation the settings apply to the shared file system. With Red Hat OpenStack Platform (RHOSP) director, you must create a default share type before you open the cloud for users to access. For CephFS with NFS, use the manila type-create command: For more information about share types, see Creating a share type in the Storage Guide .

Commands:
[stack@undercloud ~]USD source ~/overcloudrc
(overcloud) [stack@undercloud-0 ~]USD openstack network create StorageNFS --share --provider-network-type vlan --provider-physical-network datacentre --provider-segment 70
[stack@undercloud-0 ~]USD openstack subnet create --allocation-pool start=172.17.0.4,end=172.17.0.250 --dhcp --network StorageNFS --subnet-range 172.17.0.0/20 --gateway none StorageNFSSubnet
[stack@undercloud-0 ~]USD openstack subnet create --ip-version 6 --dhcp --network StorageNFS --subnet-range fd00:fd00:fd00:7000::/64 --gateway none --ipv6-ra-mode dhcpv6-stateful --ipv6-address-mode dhcpv6-stateful StorageNFSSubnet -f yaml
manila type-create default false