* 1 main, controller and networker like, without nova-compute service on
it, this node has "dvr_snat" set as L3 agent's mode,
* 2 compute like nodes with nova compute and L3 agent in "dvr" mode
Even though there is only one "dvr_snat" node in the job, it keeps
"l3_ha" option set to "true" in Neutron's config. That way we are still
testing "ha" code path of the centralized part of the router but also
job is now closer to the real life, and supported deployments topology.
Additionally this patch adds nodeset for 3 nodes with Ubuntu Jammy and
controller node not running compute service as there is no such nodeset
defined globally.
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/874536 /opendev. org/openstack/ neutron/ commit/ 169ef0558926656 fe9ef38fea42dca da2786ae0d
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 169ef0558926656 fe9ef38fea42dca da2786ae0d
Author: Slawek Kaplonski <email address hidden>
Date: Tue Feb 21 09:18:51 2023 +0100
Change neutron- ovs-tempest- dvr-ha- multinode- full job's config
Now this job runs on 3 nodes:
* 1 main, controller and networker like, without nova-compute service on
it, this node has "dvr_snat" set as L3 agent's mode,
* 2 compute like nodes with nova compute and L3 agent in "dvr" mode
Even though there is only one "dvr_snat" node in the job, it keeps
"l3_ha" option set to "true" in Neutron's config. That way we are still
testing "ha" code path of the centralized part of the router but also
job is now closer to the real life, and supported deployments topology.
Additionally this patch adds nodeset for 3 nodes with Ubuntu Jammy and
controller node not running compute service as there is no such nodeset
defined globally.
Related-Bug: #1934666
Change-Id: Id6a91795ebc73b e26bb34d9eaf8a5 3b2b6a1ba0c