Updated docs for nova-04delta/vfio DT/VA

Add Nova migration SSH secret customization to nova04delta and nvidia-vfio

Add finalize GPU installation steps to NVIDIA VFIO passthrough docs

Co-authored-by: aider (gemini/gemini-2.5-pro) <[email protected]>
Signed-off-by: Bohdan Dobrelia <[email protected]>

Author: bogdando

examples/dt/nova/nova04delta/data-plane.md

@@ -12,35 +12,81 @@ oc project openstack
 ```
 Change to the nova/nova04delta directory
 ```
-cd architecture/examples/va/nova/nova04delta/edpm
+cd architecture/examples/dt/nova/nova04delta/edpm
 ```
-Edit the [nodeset/values.yaml](nodeset/values.yaml), [nodeset2/values.yaml](nodeset/values.yaml)
+Edit the [nodeset/values.yaml](nodeset/values.yaml), [nodeset2/values.yaml](nodeset2/values.yaml)
 and [deployment/values.yaml](deployment/values.yaml) files to suit
 your environment.
+In `nodeset/values.yaml` and `nodeset2/values.yaml`, pay special attention to the `baremetalhosts` section. You will need to provide details for each of your baremetal compute nodes, including:
+- `bmc.address`: The IP address of the Baseboard Management Controller (BMC).
+- `bootMACAddress`: The MAC address of the network interface that the node will use to PXE boot.
+- Other parameters as described in the main [README.md](README.md).
+
+Additionally, you need to provide SSH keys for Nova live migration. The following keys in `nodeset/values.yaml` and `nodeset2/values.yaml` must be populated with base64 encoded values:
+- `nova.migration.ssh_keys.private`
+- `nova.migration.ssh_keys.public`
+
+You can encode your keys using the `base64` command, for example: `cat ~/.ssh/id_rsa | base64 -w0`.
 ```
 vi nodeset/values.yaml
 vi nodeset2/values.yaml
 vi deployment/values.yaml
 ```
-Generate the dataplane nodeset CRs.
+
+### Configure BMO - Provisioning to watch all namespaces
+
 ```
-kustomize build nodeset > dataplane-nodeset.yaml
-kustomize build nodeset2 > dataplane-nodeset2.yaml
+oc patch provisioning provisioning-configuration --type merge -p '{"spec":{"watchAllNamespaces": true }}'
 ```
-Generate the dataplane deployment CR.
+
+### Configure BMO - Provisioning to use external network for virtual-media
+
 ```
-kustomize build deployment > dataplane-deployment.yaml
+oc patch provisioning provisioning-configuration --type merge -p '{"spec":{"virtualMediaViaExternalNetwork": true }}'
+```
+
+### Create the BareMetalHost CRs
+
+Also, ensure the `bmhLabelSelector` in `baremetalSetTemplate` matches the labels you have defined for your `baremetalhosts`. For example, if you use `app: openstack`, your `baremetalhosts` should have a corresponding label.
+
+Before applying the nodeset configuration, you must also create the `bmc-secret` secret that contains the BMC credentials. You can create it with the following command:
+```
+oc create secret generic bmc-secret --from-literal=username=CHANGEME --from-literal=password=CHANGEME
+```
+
+Generate the dataplane nodeset CRs, which include the BareMetalHost definitions.
+```
+kustomize build nodeset > dataplane-nodeset.yaml
+kustomize build nodeset2 > dataplane-nodeset2.yaml
 ```
 
-## Create CRs
-Create the nodeset CR
+Apply the CRs to create the BareMetalHosts and the nodesets.
 ```
 oc apply -f dataplane-nodeset.yaml
 oc apply -f dataplane-nodeset2.yaml
 ```
-Wait for dataplane nodeset setup to finish
+
+Wait for the BareMetalHosts to become available. You can monitor the status with:
+```
+oc get bmh -w
+```
+The state should change to `available`.
+
+### Configure and deploy the dataplane
+
+Edit `deployment/values.yaml` if needed.
+```
+vi deployment/values.yaml
+```
+Generate the dataplane deployment CR.
+```
+kustomize build deployment > dataplane-deployment.yaml
+```
+
+Wait for dataplane nodesets setup to finish.
 ```
 oc wait osdpns openstack-edpm --for condition=SetupReady --timeout=600s
+oc wait osdpns openstack-edpm-2 --for condition=SetupReady --timeout=600s
 ```
 
 Start the deployment
@@ -50,7 +96,7 @@ oc apply -f dataplane-deployment.yaml
 
 Wait for dataplane deployment to finish
 ```
-oc wait osdpns openstack-edpm --for condition=Ready --timeout=40m
+oc wait osdpd edpm-deployment --for condition=Ready --timeout=40m
 ```
 
 ## Generate yamls necessary to finialize Nvidia GPU installation
@@ -80,4 +126,4 @@ oc apply -f dataplane-post-driver-deployment.yaml
 Wait for dataplane deployment to finish
 ```
 oc wait osdpd edpm-deployment-post-driver --for condition=Ready --timeout=20m
-```
+```

examples/va/nvidia-vfio-passthrough/data-plane-pre.md

@@ -33,6 +33,12 @@ Edit the `edpm/nodeset/values.yaml` file to suit your environment. Pay special a
 - `bootMACAddress`: The MAC address of the network interface that the node will use to PXE boot.
 - Other parameters as described in the main [README.md](README.md).
 
+Additionally, you need to provide SSH keys for Nova live migration. The following keys in `edpm/nodeset/values.yaml` must be populated with base64 encoded values:
+- `nova.migration.ssh_keys.private`
+- `nova.migration.ssh_keys.public`
+
+You can encode your keys using the `base64` command, for example: `cat ~/.ssh/id_rsa | base64 -w0`.
+
 Also, ensure the `bmhLabelSelector` in `baremetalSetTemplate` matches the labels you have defined for your `baremetalhosts`. For example, if you use `app: openstack`, your `baremetalhosts` should have a corresponding label.
 
 Before applying the nodeset configuration, you must also create the `bmc-secret` secret that contains the BMC credentials. You can create it with the following command:
@@ -80,3 +86,32 @@ Wait for dataplane deployment to finish.
 ```
 oc wait osdpns openstack-edpm --for condition=Ready --timeout=60m
 ```
+
+## Generate yamls necessary to finialize Nvidia GPU installation
+After the Nvidia drivers have been blacklisted on the EDPM nodes, the computes need
+to be rebooted. Below explains the necessary steps to apply a reboot on the necessary nodesets.
+
+Change to the nvidia-vfio-passthrough/edpm-post-driver directory
+```
+cd architecture/examples/va/nvidia-vfio-passthrough/edpm-post-driver/
+```
+Edit the [deployment/values.yaml](edpm-post-driver/deployment/values.yaml) files to suit
+your environment.
+```
+vi deployment/values.yaml
+```
+Generate the dataplane deployment CR.
+```
+kustomize build deployment > dataplane-post-driver-deployment.yaml
+```
+
+## Create CRs to finalize GPU installation
+Start the deployment
+```
+oc apply -f dataplane-post-driver-deployment.yaml
+```
+
+Wait for dataplane deployment to finish
+```
+oc wait osdpd edpm-deployment-post-driver --for condition=Ready --timeout=20m
+```