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

[danken (oVirt JIRA)]

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

danken commented on OVIRT-1549:
-------------------------------

Sorry for missing the link to gerrit: https://review.openstack.org/#/q/project:openstack/ovsdbapp

*  I believe they build RPMs daily from merged code, but...
*  I don't think they currently release them officially
*  I want ovsdbapp to get a CI-1 if they break OST. I think that means "tracking the project at the source level". I believe that ovsdbapp would not mind adding automation/build-artefacts.sh if this is required

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