On 3/8/23 15:32, Dumitru Ceara wrote: > On Wed, Mar 8, 2023 at 3:15 PM Dumitru Ceara <[email protected]> wrote: >> >> Hi all, >> >> Frode brought up during last week's OVN IRC meeting the possibility of >> moving ovn-heater [0] to the ovn-org [1] organization. >> >> For some context: today ovn-heater uses containers on multiple bare >> metal machines to simulate OVN nodes provisioned by ovn-kubernetes >> (already part of ovn-org [2]) in various scenarios. This is used to >> benchmark OVN (and ovsdb-server and other OVS components) at scale in >> these scenarios. >> >> We (at Red Hat) have been using ovn-heater consistently (weekly runs) >> throughout the last year in order to benchmark OVN in OpenShift like >> scenarios in clusters scaling up to 500 nodes. These runs have already >> helped us pin-point a lot of the scale related issues (both OVN and >> ovsdb-server) that have been fixed in the last months/year. >> >> The core of ovn-heater is (rather simple) python code so there should be >> no reason that would block us from adding more scale test scenarios to >> simulate clusters provisioned by other CMS (e.g., OpenStack) turning >> ovn-heater into a generic OVN scale testing tool. >> >> I cc-ed all the OVN maintainers and all GitHub ovn-org owners but >> feedback from the whole community is more than welcome!
As a piece of feedback from the contributor to that project, I think it needs a contribution guide and a documented contribution policy such as adoption of DCO, for example. AUTHORS file may need some updates. I'm pretty sure that all the contributors so far had a right to contribute their code. But these policies might be good to iron out before "going public". DCO bot is in use by some of the existing ovn-org projects, so it may help enforcing policies after migration. My 2c. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
