summaryrefslogtreecommitdiff
path: root/rally-jobs
diff options
context:
space:
mode:
authorBence Romsics <bence.romsics@gmail.com>2019-06-03 18:34:45 +0200
committerBence Romsics <bence.romsics@gmail.com>2019-06-06 10:56:34 +0200
commitccef17605d1e28c418821c2235ba24c15893fff2 (patch)
tree6fe13b4d9d2dab4d79aa74878299a426b7598a8b /rally-jobs
parent36428d60a643ee6c8a6a7a7c0cb649a4969047df (diff)
downloadneutron-ccef17605d1e28c418821c2235ba24c15893fff2.tar.gz
Run nova's VM boot rally scenario in the neutron gate
As discussed on the neutron_performance meeting [1] we'd like to run a rally scenario in the neutron gate that boots a vm. Combined with Slawek's work to integrate osprofiler with rally [2] we should start to get some insight into neutron's vif plugging performance even if that's not something directly exposed and measurable through the API. [1] http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/latest.log.html#t2019-06-03T16:12:17 [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006769.html Change-Id: I7e2c19e8cdb62cb85046500f862e8dbd42306225
Diffstat (limited to 'rally-jobs')
-rw-r--r--rally-jobs/task-neutron.yaml22
1 files changed, 22 insertions, 0 deletions
diff --git a/rally-jobs/task-neutron.yaml b/rally-jobs/task-neutron.yaml
index baa7932b35..a0c747da70 100644
--- a/rally-jobs/task-neutron.yaml
+++ b/rally-jobs/task-neutron.yaml
@@ -1,4 +1,6 @@
{% set floating_network = floating_network or "public" %}
+{% set image_name = "^(cirros.*-disk|TestVM)$" %}
+{% set flavor_name = "m1.tiny" %}
---
version: 2
@@ -468,3 +470,23 @@
quotas:
neutron:
security_group: -1
+ -
+ title: VM booting workloads
+ workloads:
+ -
+ scenario:
+ NovaServers.boot_and_delete_server:
+ flavor:
+ name: {{flavor_name}}
+ image:
+ name: {{image_name}}
+ auto_assign_nic: true
+ runner:
+ constant:
+ times: 2
+ concurrency: 2
+ contexts:
+ users:
+ tenants: 2
+ users_per_tenant: 2
+ network: {}