[CI][nova-next]test with placement ac optimizations
The nova-next job will run tempest with allocation candidate generation optimizations enabled: [placement] allocation_candidates_generation_strategy = breadth-first max_allocation_candidates = 100000 [workarounds] optimize_for_wide_provider_trees = True Depends-On: https://review.opendev.org/c/openstack/devstack/+/939825 Deepnds-On: https://review.opendev.org/c/openstack/placement/+/962776 Change-Id: Icbfc568bead950a3be22784746421cc11382b2d7 Signed-off-by: Balazs Gibizer <gibi@redhat.com>
This commit is contained in:
1 changed files with 9 additions and 0 deletions
@@ -383,6 +383,9 @@
Starting in Wallaby, the job defaults to the q35 machine type.
Starting in Yoga, the job tests noVNC from source and enables unified limits.
Starting in Caracal, the job compiles the mdev sample drivers from source.
Starting in Gazpacho, the job test placement with
allocation_candidates_generation_strategy=breadth-first and
optimize_for_wide_provider_trees=True.
Runs all tempest compute API and most scenario tests concurrently.
irrelevant-files:*nova-base-irrelevant-files
# Run post-tempest tests like for nova-manage commands.
@@ -450,6 +453,12 @@
tunnel_types:gre,vxlan
ml2:
type_drivers:flat,geneve,vlan,gre,local,vxlan
$PLACEMENT_CONF:
placement:
allocation_candidates_generation_strategy:breadth-first
max_allocation_candidates:100000
workarounds:
optimize_for_wide_provider_trees:True
test-config:
$TEMPEST_CONFIG:
network-feature-enabled:
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.