search

msimonin / ombt-orchestrator

Framework to evaluate different message buses using oslo.messaging (via ombt)
GNU General Public License v3.0
3 stars 4 forks source link

Allow constant zipped parameter in campaign incremental #110

Open msimonin opened 6 years ago

msimonin commented 6 years ago

Currently if one specifies:

test_case_1:
  nbr_clients: [1, 2, 3]
  nbr_servers: [1, 1, 1]

We expect the incremental campaign to start (1, 1) then (1, 0) then (1, 0) clients and servers. But I observed that the above results in starting (1, 1) then (1, 1) then (1, 1) clients and servers.

We want to support constant parameters in the zipped parameters.

The function generate_current_values (https://github.com/msimonin/ombt-orchestrator/blob/9204476ec555ae3597019cea9a8b0d665350941b/orchestrator/campaign.py#L82) and the line : https://github.com/msimonin/ombt-orchestrator/blob/9204476ec555ae3597019cea9a8b0d665350941b/orchestrator/campaign.py#L92-L93 causes the above behaviour.

Indeed parameters are treated separately leading the second line to always have previous_servers=0 and current_servers=0. This is due to the plist.index to return the first index of the occurence in a list.