From b939c24faab3308ea15f12a1a909284b4e0e73de Mon Sep 17 00:00:00 2001 From: cid Date: Wed, 26 Mar 2025 12:30:48 +0100 Subject: [PATCH] docs: Clarify physical_network should be a name Clarify physical_network should be a name matching Neutron configuration Change-Id: I4ed4e9bd02b8ea103dc3602ece590f50f4e829f6 --- doc/source/admin/networking.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/source/admin/networking.rst b/doc/source/admin/networking.rst index 05ffd85b9d..627bf1452d 100644 --- a/doc/source/admin/networking.rst +++ b/doc/source/admin/networking.rst @@ -204,9 +204,13 @@ Physical networks An Ironic port may be associated with a physical network using its ``physical_network`` field. Ironic uses this information when mapping between virtual ports in Neutron and physical ports and -port groups. A port's physical network field is optional, and if not +port groups. A port's physical network field is optional, and if not set then any VIF may be mapped to that port, provided that no free Ironic port with a suitable physical network assignment exists. +When set, its value must be a name that corresponds to a physical network +in Neutron for the networking-baremetal integration to properly reconcile +the port. This has to be a name (not a UUID) since physical networks are +configured in Neutron by name. The physical network of a port group is defined by the physical network of its constituent ports. The Ironic service ensures that all ports in a port