CI: Use 16GB nodes for debian-bookworm nodes

We have seen OOM issues in particular for debian jobs, let's see whether
using larger nodes helps.

Signed-off-by: Dr. Jens Harbott <[email protected]>
Change-Id: Ie225474520a2720439bd8014dc3179ddc8dfefed
(cherry picked from commit 622f294)

Author: osfrickler

zuul.d/nodesets.yaml

@@ -6,10 +6,10 @@
         label: centos-9-stream
 
 - nodeset:
-    name: kolla-ansible-debian-bookworm-8GB
+    name: kolla-ansible-debian-bookworm
     nodes:
       - name: primary
-        label: debian-bookworm-8GB
+        label: debian-bookworm
 
 - nodeset:
     name: kolla-ansible-debian-bookworm-16GB
@@ -18,10 +18,10 @@
         label: debian-bookworm-16GB
 
 - nodeset:
-    name: kolla-ansible-debian-bookworm-aarch64-8GB
+    name: kolla-ansible-debian-bookworm-aarch64
     nodes:
       - name: primary
-        label: debian-bookworm-arm64-8GB
+        label: debian-bookworm-arm64
 
 - nodeset:
     name: kolla-ansible-ubuntu-noble-8GB
@@ -55,6 +55,16 @@
       - name: secondary2
         label: debian-bookworm-16GB
 
+- nodeset:
+    name: kolla-ansible-debian-bookworm-multi-16GB
+    nodes:
+      - name: primary
+        label: debian-bookworm-16GB
+      - name: secondary1
+        label: debian-bookworm-16GB
+      - name: secondary2
+        label: debian-bookworm-16GB
+
 - nodeset:
     name: kolla-ansible-rocky9
     nodes: