From f19c577edf1b0b31bcf37e5825ad6a7570907120 Mon Sep 17 00:00:00 2001 From: Balazs Gibizer Date: Wed, 6 Sep 2023 14:19:33 +0200 Subject: [PATCH] [doc]Trigger nova discover hosts after EDPM deploy The periodic host discovery is now disabled in nova-scheduler as it is not scaling well. Instead after EDPM compute node deployment the nova-manage cell_v2 discover_hosts CLI needs to be run to trigger the discovery. This PR documents the new necessary manual step. Related-To: openstack-k8s-operators/nova-operator#519 Related: https://issues.redhat.com/browse/OSPRH-319 --- docs/deploying.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/deploying.md b/docs/deploying.md index 624d4d826..19601b3ed 100644 --- a/docs/deploying.md +++ b/docs/deploying.md @@ -387,6 +387,13 @@ edpm-compute-0 True DataPlaneNode Ready edpm-compute-1 True DataPlaneNode Ready ``` +If the deployment involved adding new compute nodes then after the deployment +is ready those compute nodes need to be mapped in nova. To do that run the +following command: +```console +oc rsh nova-cell0-conductor-0 nova-manage cell_v2 discover_hosts --verbose +``` + ### Understanding dataplane conditions Each dataplane resource has a series of conditions within their `status`