https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation.
ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp.
If they don't release RPMs, how are our users supposed to consume this?
The point of OST is to emulate what the user does, so 1st decide what the user does...
Also WRT CI-1 on Gerrit, OST was never designed to do this, it takes far too long and far too many resources to be reasonable to run for every patch set. This is why we keep the process semi-automatic even for oVirt's own repos...
They do release RPMs as part of RDO https://trunk.rdoproject.org/centos7-master/current/ but not per patch.
If ovirt-infra does not have resources to have this per patch, we can start with a nightly run. ovsdbapp said that they can wait 40 minutes for our vote.
is this still needed? how often were we broken from this pkg or needed to consume it early so it will worth the time and resource invesment?
I am not aware of ovsdbapp breaking us.
However, openvswtich did, which would have been caught had we have such CI.
I don't know if it is "worth it", as I have not estimated the resources needed, but I think that it would be beneficial for ovirt and its CI system.
The repo you provided has an 'openstack-netron-openvswitch' pkg, so we can't use it because it has different naming that what oVirt uses right?
Is there a different repo that has nightly builds or something similar that can we used in OST?