openstack/manila
Code Issues Proposed changes

doc: Add explanation about neutron_physical_net_name

Browse Source 
The neutron_physical_net_name option should be configured to use
routed provider networks. Also clarify that neutron_net_id and
neutron_subnet_id are not the options, but the properties used when
creating a share network via API.

Change-Id: I3a056f98c2e076be2f0303cdbfd2c8c11dd79438
Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
This commit is contained in:
Takashi Kajinami
2025-08-28 23:02:44 +09:00
parent ad8087d7a9
commit 421b82dbd8
1 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/admin/shared-file-systems-network-plugins.rst
View File

@@ -60,11 +60,17 @@ Shared File Systems service:
each share driver to support at least one network segmentation type.
a) ``manila.network.neutron.neutron_network_plugin.NeutronNetworkPlugin``.
This is a default network plug-in. It requires the ``neutron_net_id`` and
the ``neutron_subnet_id`` to be provided when defining the share network
that will be used for the creation of share servers. The user may define
any number of share networks corresponding to the various physical
network segments in a project environment.
This is a default network plug-in. It requires the ``neutron_net_id``
property and the ``neutron_subnet_id`` property to be provided when
creating the share network that will be used for the creation of share
servers. The user may define any number of share networks corresponding
to the various physical network segments in a project environment.
.. note::
When a share network contains a router provider network with multiple
segments, the ``neutron_physical_net_name`` option should be
additionally configured in ``manila.conf``.
b) ``manila.network.neutron.neutron_network_plugin.NeutronSingleNetworkPlugin``.
This is a simplification of the previous case. It accepts values for