From e86488e30560bb4d76b4d3b17bc802a74b617ddb Mon Sep 17 00:00:00 2001 From: Jonathan Rosser Date: Mon, 8 Feb 2021 09:47:14 +0000 Subject: [PATCH] Add reference to netplan config example Change-Id: Iff0e3c544b12215b2e2a654364d0529fb2d1983c --- doc/source/user/network-arch/example.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/doc/source/user/network-arch/example.rst b/doc/source/user/network-arch/example.rst index a1aa926ed5..417b3d8432 100644 --- a/doc/source/user/network-arch/example.rst +++ b/doc/source/user/network-arch/example.rst @@ -54,6 +54,22 @@ Additional VLANs may be required for the following purposes: Network interfaces ~~~~~~~~~~~~~~~~~~ +Configuring network interfaces +------------------------------ + +OpenStack-Ansible does not mandate any specific method of configuring +network interfaces on the host. You may choose any tool, such as ifupdown, +netplan, systemd-networkd, networkmanager or another operating-system +specific tool. The only requirement is that a set of functioning network +bridges and interfaces are created which match those expected by +OpenStack-Ansible, plus any that you choose to specify for neutron +physical interfaces. + +A selection of network configuration example files are given in +the ``etc/network`` and ``etc/netplan`` for ubuntu systems, and it is +expected that these will need adjustment for the specific requirements +of each deployment. + Single interface or bond ------------------------