Add more workload scenarios

[huikang]

There are limited workload scenarios in ovn-scale-test, e.g., creating network, creating and binding port, ACL [1]. We need add more workload scenarios.

Lets use this thread to collect idea about useful scenarios. Thanks.

[1]https://github.com/openvswitch/ovn-scale-test/tree/master/ansible/roles/rally/templates

[manand2]

Scenarios to be added to Rally:

1. create/delete/update/list routers
2. create large number of resources (networks,ports,acls, routers etc.,) per tenant
3. create and delete ports while scaling - create 100, delete 50 of them iteratively

[huikang]

@manand2 Thanks for your input.

• Can you illustrate some details about 2) because I feel it may duplicate 1)?
• For 3), current ovn-scale-test support creating and deleting ports? Do you mean delete partial of the ports in the network? Thanks.

[manand2]

#1 is focused on scaling routers only, which will include create network, subnet, router. So create a tenant, create x networks, y subnets and z routers.

#2 adds ports and acls. We have seen issues when larger number of resources created for fewer tenants.

#3 Yes create 100 and delete 50 in a loop.

[mbanikazemi]

the above sounds reasonable. For routers, one may want to distinguish between routers and gateway routers.

[huikang]

@manand2 @mbanikazemi Thanks for your inputs!
The existing ovn-scale-test doc is very ad hoc, which causes the difficulty to in adding new test scenarios for new developers. I will add a how-to doc for this. Meanwhile, could you create some bash script for the above test cases (and paste the the link here)? Thanks.

[hzhou8]

My list of TODOs:

• Scale test with ACLs
• Scale test with large number of small networks
• Scale test with large networks
• Scale test with large number of small logical routers
• Scale test with large logical routers
• Scale test with large number of small logical routers but all connected together by another lswitch

[huikang]

@hzhou8 in your last scenario, do you mean the following steps?

1. create M routers; for each router N ports are created. M is large, while N is a small number.
2. Connect the M routers together to a "Join" logical switch [1]

Is my understanding correct? Thanks.

[1] https://github.com/openvswitch/ovs/blob/master/tests/ovn.at#L3338-L3350

[hzhou8]

@huikang, sorry for the confusion. For "small" and "large" logical routers I meant the number of logical switches connected to the logical router. The purpose of this scenario is similar as "Scale test with large logical routers", for the concern of the scalability of the current ovn implementation when every lport is able to talk to any other lports.

1. create M routers; for each router N ports are created. M is large, while N is a small number.

For each router, not only create N lports but also connect to N lswitches (each lswitch may be "normal" size).

1. Connect the M routers together to a "Join" logical switch [1]

That's right!

[huikang]

@hzhou8 Thanks for the clarification. For the N lswitches connecting to a logical router, I have a patched merged. Some new variables are added to configure the number of routers and the number of network/switch connected to each router [2].

An additional PR was just added to bind the ports to hypervisors for the router tasks. If you have time, please review the PR [3]. Thanks.

[2] b59e6a7#diff-607e6e5925d0031dafa79eb80d198640

[3] #132