squashme: minor fixes after the AI agent work

Signed-off-by: Bohdan Dobrelia <[email protected]>

Author: bogdando

dt/nova/nova04delta/edpm/nodeset/kustomization.yaml

@@ -38,7 +38,7 @@ replacements:
         options:
           create: true
 
-  # Nova compute PCI passthrough customization
+  # Nova compute CPU pinning customization
   - source:
       kind: ConfigMap
       name: edpm-nodeset-values
@@ -51,6 +51,7 @@ replacements:
           - data.25-cpu-pinning-nova\.conf
         options:
           create: true
+  # Nova compute PCI passthrough customization
   - source:
       kind: ConfigMap
       name: edpm-nodeset-values

dt/nova/nova04delta/edpm/nodeset/nova_gpu.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: v1
 kind: ConfigMap
 metadata:

dt/nova/nova04delta/edpm/nodeset2/kustomization.yaml

@@ -38,7 +38,7 @@ replacements:
         options:
           create: true
 
-  # Nova compute PCI passthrough customization
+  # Nova compute CPU pinning customization
   - source:
       kind: ConfigMap
       name: edpm-nodeset-values
@@ -51,6 +51,7 @@ replacements:
           - data.25-cpu-pinning-nova\.conf
         options:
           create: true
+  # Nova compute PCI passthrough customization
   - source:
       kind: ConfigMap
       name: edpm-nodeset-values

dt/nova/nova04delta/edpm/nodeset2/nova_gpu.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: v1
 kind: ConfigMap
 metadata:

examples/dt/nova/nova04delta/README.md

@@ -29,6 +29,7 @@ The following parameters are crucial for host-level configuration:
 
 ## Nova Configuration
 
+# FIXME: this looks only used in PCI groups in placement? The same pci_passthrough:alias should be used in both cases it seems?
 Nova control plane is configured for requesting PCI devices from Placement
 through `resources:VGPU=X` flavor extra specs.
 That is a contrary to the legacy mode where PCI devices used to be requested through

examples/va/nvidia-vfio-passthrough/README.md

@@ -16,6 +16,7 @@ with nested virtualization and requires real baremetal hosts.
 
 ### Nova
 
+# FIXME: this looks only used in PCI groups in placement? The same pci_passthrough:alias should be used in both cases it seems?
 Nova control plane is configured for requesting PCI devices from Placement
 by setting `resources:VGPU=X` in flavor extra specs.
 That is a contrary to the legacy mode where PCI devices used to be requested through

examples/va/nvidia-vfio-passthrough/control-plane/kustomization.yaml

@@ -40,7 +40,7 @@ replacements:
           - spec.neutron.template.customServiceConfig
         options:
           create: true
-  # OVN control plane SRIOV customization
+  # OVN control plane customization
   - source:
       kind: ConfigMap
       name: service-values

examples/va/nvidia-vfio-passthrough/edpm/nodeset/kustomization.yaml

@@ -48,6 +48,18 @@ replacements:
           - spec.baremetalSetTemplate
         options:
           create: true
+  - source:
+      kind: ConfigMap
+      name: edpm-nodeset-values
+      fieldPath: data.nova.compute.conf
+    targets:
+      - select:
+          kind: ConfigMap
+          name: cpu-pinning-nova
+        fieldPaths:
+          - data.25-cpu-pinning-nova\.conf
+        options:
+          create: true
   - source:
       kind: ConfigMap
       name: edpm-nodeset-values

va/nvidia-vfio-passthrough/edpm/nodeset/kustomization.yaml

@@ -38,7 +38,7 @@ replacements:
         options:
           create: true
 
-  # Nova compute PCI passthrough customization
+  # Nova compute CPU pinning customization
   - source:
       kind: ConfigMap
       name: edpm-nodeset-values
@@ -51,6 +51,7 @@ replacements:
           - data.25-cpu-pinning-nova\.conf
         options:
           create: true
+  # Nova compute PCI passthrough customization
   - source:
       kind: ConfigMap
       name: edpm-nodeset-values

va/nvidia-vfio-passthrough/edpm/nodeset/nova_gpu.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: v1
 kind: ConfigMap
 metadata: