On 31 May 2018 at 13:00, Milan Zamazal <mzamazal@redhat.com> wrote:
Nir Soffer <nsoffer@redhat.com> writes:
I know that new ovirt CI solved some of the issues, but nobody sent patches to convert vdsm to the new standard yet.
I asked Barak about possible Vdsm conversion at his deep dive and he responded that the new CI may need more real-use testing before projects such as Vdsm switch. It's a couple of weeks since then and if there are no problems with projects that already use it (such as oVirt system tests), maybe we should start working on a conversion patch?
Let me clarify what I said back then a bit - since engine and VDSM are the two big flagship projects, I want then to be the last projects to be converted. So its not a matter of time its a matter of converting all the other projects first. Now the thing is, we will not do this on our own - maintainers need to be in the loop as we move projects, so while we do want to be proactive about this, given the other task load we have, things work best when the maintainers actively approach us as some like the ovirt-provider-ovn maintainers did. So please if you're a small-ish project maintainer shoot an email to infra-support@ovirt.org asking your project to be covered and then monitor the jira ticket. The actual setup takes just a few minutes and we will use the Jira ticket to update you on progress and rely any project-specific questions you may have.
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community- guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/ message/BI2TZYNRFSYFZEKQJHZMDV5AKY2DF5QZ/
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted