Manila Network Plugins

To set up the standalone network plugin, the following options should be added to the driver-specific stanza within the Manila configuration file (manila.conf):

                    network_api_class = manila.network.standalone_network_plugin.StandaloneNetworkPlugin
                    standalone_network_plugin_allowed_ip_ranges = 10.0.0.10-10.0.0.254
                    standalone_network_plugin_ip_version = 4
                    standalone_network_plugin_segmentation_id = 314
                    standalone_network_plugin_network_type = vlan
                    standalone_network_plugin_mask = 255.255.255.0
                    standalone_network_plugin_gateway = 10.0.0.1
                

Table 6.11, “Configuration options for Standalone Network Plugin ” lists the configuration options available for the standalone network plugin:

In this configuration, administrators set up a single neutron network and specify the network information in manila.conf. Manila will create network ports on the network and gather details regarding the IP address, gateway, netmask and MTU from this network. These details are used by the NetApp driver to create Data Logical Interfaces (LIFs) for the Vserver created. In this configuration, tenants need to create "empty" share network objects, without specifying any network information. To set up the simple Neutron network plugin, the following options should be added to the driver-specific stanza within the Manila configuration file (manila.conf):

                    network_api_class = manila.network.neutron.neutron_network_plugin.NeutronSingleNetworkPlugin
                    neutron_net_id = 37fb9f7e-4ffe-4900-8dba-c6d4251e588e
                    neutron_subnet_id= 447732be-4cf2-42b0-83dc-4b6f4ed5368c
                

Table 6.12, “Configuration options for Neutron Network Plugin ” lists the configuration options available for the Neutron network plugin:

In this configuration, tenants can specify network details in their own share network objects. These network details can be from administrator created Neutron provider networks or tenant created Neutron networks. To set up the configurable Neutron network plugin, the following options should be added to the driver-specific stanza within the Manila configuration file (manila.conf):

                    network_api_class = manila.network.neutron.neutron_network_plugin.NeutronNetworkPlugin
                

In this configuration, administrators set up a single neutron network, and Manila will send any binding profiles configured in manila.conf to Neutron while creating ports on the network. As noted prior, Neutron may be configured with a hardware switch to provide tenant networks with access to devices connected to the hardware switch. You may use the switch vendor's ML2 mechanism driver to dynamically allocate segments corresponding to the segments created on the OpenStack compute hosts by OVS. This port binding network plugin is crucial to ensure that port binding occurs at the mechanism driver. Verify with your switch vendor if they support binding profiles. While most vendors support port binding, some may not support the "baremetal" vnic_type. Use of this plugin is preferable when using a hierarchical virtual network that uses different network segments. These segments can be of different network types (ex: VLAN within the rack and VXLAN between the top-of-rack and core switches). To set up the simple Neutron port binding network plugin, the following options should be added to the driver-specific stanza within the Manila configuration file (manila.conf). The Neutron binding profile in this example is for a Cisco Nexus 9000 switch:

                    network_api_class = manila.network.neutron.neutron_network_plugin.NeutronBindSingleNetworkPlugin
                    neutron_net_id = 37fb9f7e-4ffe-4900-8dba-c6d4251e588e
                    neutron_subnet_id = 447732be-4cf2-42b0-83dc-4b6f4ed5368c
                    neutron_host_id = netapp_lab42
                    neutron_vnic_type = baremetal
                    neutron_binding_profiles = phys1

                    [phys1]
                    neutron_switch_id = 10.63.152.254
                    neutron_port_id = 1/1-4
                    neutron_switch_info = switch_ip:10.63.152.254
                

Table 6.13, “Configuration options for Simple Neutron Port Binding Network Plugin ” lists the configuration options available for the Simple Neutron Port Binding network plugin:

In spirit this plugin works exactly like the Simple Neutron Port Binding Network Plugin that is mentioned above. The only difference being that the Neutron network is not configured within manila.conf by the administrator. Use of this plugin allows Manila to derive network information from the Share Network objects created by the tenants. To set up the configurable Neutron port binding network plugin, the following options should be added to the driver-specific stanza within the Manila configuration file (manila.conf). The Neutron binding profile in this example is for a Cisco Nexus 9000 switch:

                    network_api_class = manila.network.neutron.neutron_network_plugin.NeutronBindNetworkPlugin
                    neutron_host_id = netapp_lab42
                    neutron_vnic_type = baremetal
                    neutron_binding_profiles = phys1

                    [phys1]
                    neutron_switch_id = 10.63.152.254
                    neutron_port_id = 1/1-4
                    neutron_switch_info = switch_ip:10.63.152.254
                

Table 6.14, “Configuration options for the tenant configurable Neutron Port Binding Network Plugin ” lists the configuration options available for the configurable Neutron Port Binding network plugin: