Eduardo Olivares 093a3d4642 Multinode jobs use nested-virt nodes
The nodes acting as computes should be nested-virt nodes.
The devstack-tobiko-multinode job is modified to use ML2/OVN instead of
ML2/OVS.

Change-Id: If03d768503c14ee87a091d4c8d86b50519d8b9af
2025-01-22 12:42:24 +01:00

59 lines
1.4 KiB
YAML

---
- nodeset:
name: devstack-tobiko-focal
nodes:
- name: controller
# label: ubuntu-focal
label: nested-virt-ubuntu-focal
groups: &STANDALONE_GROUPS
- name: tempest
nodes:
- controller
- nodeset:
name: devstack-tobiko-jammy
nodes:
- name: controller
# label: ubuntu-jammy
label: nested-virt-ubuntu-jammy
groups: *STANDALONE_GROUPS
# --- MULTINODE --------------------------------------------------------------
- nodeset:
name: devstack-tobiko-multinode
nodes:
- name: controller
label: nested-virt-ubuntu-jammy
- name: compute1
label: nested-virt-ubuntu-jammy
- name: compute2
label: nested-virt-ubuntu-jammy
groups: &MULTINODE_GROUPS
# Node where tests are executed and test results collected
- name: tempest
nodes:
- controller
# Nodes running the compute service
- name: compute
nodes:
- controller
- compute1
- compute2
# Nodes that are not the controller
- name: subnode
nodes:
- compute1
- compute2
# Switch node for multinode networking setup
- name: switch
nodes:
- controller
# Peer nodes for multinode networking setup
- name: peers
nodes:
- compute1
- compute2