[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp

[Barak Korren (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34009#comment-34009 ] 

Barak Korren commented on OVIRT-1549:
-------------------------------------

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...

> run OST as a third-party tester for OpenStack's ovsdbapp
> --------------------------------------------------------
>
>                 Key: OVIRT-1549
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549
>             Project: oVirt - virtualization made easy
>          Issue Type: New Feature
>          Components: oVirt CI
>            Reporter: danken
>            Assignee: infra
>
> 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.



--
This message was sent by Atlassian JIRA
(v1000.1131.0#100055)