From ac3cbb01d4b25aa867b810afacd618510672cbd1 Mon Sep 17 00:00:00 2001 From: Katie Gilligan Date: Wed, 1 Apr 2026 12:02:36 -0400 Subject: [PATCH] copied changes from downstream --- ...oc_adopting-networker-services-to-the-data-plane.adoc | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs_user/modules/proc_adopting-networker-services-to-the-data-plane.adoc b/docs_user/modules/proc_adopting-networker-services-to-the-data-plane.adoc index b018e3ed2..f25440423 100644 --- a/docs_user/modules/proc_adopting-networker-services-to-the-data-plane.adoc +++ b/docs_user/modules/proc_adopting-networker-services-to-the-data-plane.adoc @@ -4,7 +4,14 @@ = Adopting Networker services to the {rhos_acro} data plane [role="_abstract"] -Adopt the Networker services in your existing {rhos_prev_long} deployment to the {rhos_long} data plane. The `Networker` services could be running on `Conroller` nodes or dedicated `Networker` nodes. You decide which services you want to run on the Networker nodes, and create a separate `OpenStackDataPlaneNodeSet` custom resource (CR) for the Networker nodes. You might also decide to implement the following options if they apply to your environment: +Adopt the Networker services in your existing {rhos_prev_long} deployment to the {rhos_long} data plane. The Networker services could be running on Controller nodes or dedicated Networker nodes. You decide which services you want to run on the Networker nodes, and create a separate `OpenStackDataPlaneNodeSet` custom resource (CR) for the Networker nodes. + +[TIP] +==== +By definition, any node that has set `enable-chassis-as-gw` is considered a _Networker node_. After the adoption process, these nodes continue to be Networker nodes. +==== + +You can implement the following options if they apply to your environment: * Depending on your topology, you might need to run the `neutron-metadata` service on the nodes, specifically when you want to serve metadata to SR-IOV ports that are hosted on Compute nodes.