Hello, Ben, As part of preparing to move ovn-heater to ovn-org, we thought it would be fun to add a logo.
We made one [0] based on your original work as well as third party work under a different license, and while IANAL, I think this means we need to ask your permission to license your original work under the Free Art License, GPLv3 or CC BY-SA 4.0 license in order to be compatible with the license of the third party work. What do you think? 0: https://github.com/dceara/ovn-heater/pull/158 1: https://creativecommons.org/share-your-work/licensing-considerations/compatible-licenses On Thu, Mar 9, 2023 at 10:52 AM Dumitru Ceara <dce...@redhat.com> wrote: > > On 3/9/23 08:08, Frode Nordahl wrote: > > On Wed, Mar 8, 2023 at 5:27 PM Dumitru Ceara <dce...@redhat.com> wrote: > >> > >> On 3/8/23 16:07, Ilya Maximets wrote: > >>> On 3/8/23 15:32, Dumitru Ceara wrote: > >>>> On Wed, Mar 8, 2023 at 3:15 PM Dumitru Ceara <dce...@redhat.com> 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". > >> > >> Many thanks for pointing this out! I opened an initial PR to take care > >> of some of this: > >> > >> https://github.com/dceara/ovn-heater/pull/155 > >> > >>> > >>> DCO bot is in use by some of the existing ovn-org projects, > >>> so it may help enforcing policies after migration. > >>> > >> > >> Sounds applicable indeed. > >> > >>> My 2c. > >>> > >>> Best regards, Ilya Maximets. > >>> > >> > >> Thanks, > >> Dumitru > >> > > > > Thanks for bringing this up, Dumitru, and I wanted to reiterate our > > interest in the project here. Parts of the repository are universally > > applicable for OVN scale testing and could be useful for other CMSs > > and deployment scenarios. > > > > We would like to deploy it in a slightly different way, so I'll be > > working on a proposal for how we could decouple the deployment > > specific and generic parts and hopefully put up a PR today. > > > > Sure, looking forward to it! > -- Frode Nordahl _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
