[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=34007#comment-34007 ] 

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

Without going into too much detail yet, the instruction you posted seem to refer to Gerrit projects, while the project you linked to is on GitHub? Is that project actually maintained in Gerrit? If so, where?

Some more questions:
* Does the project build RPMs?
* Are those RPMs officially released somewhere?
* Do we really want to track the project at the source level? If so, will the maintainers be willing to add an 'automation' directory and the related scripts?

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