otopi access lists have as unique member Alon Bar-Lev who recently
left the project.
Since I work a lot on engine-setup which is based on otopi, I have
some good experience with it, and also worked on otopi itself in the
past, I'm stepping in, proposing myself as maintainer for that
There seems to be a need for an Italian-focused oVirt mailing
list; from what I know, there are ~23 members in the ovirt
community that would benefit from it, mainly in order to discuss
Italian localization issues in oVirt.
There is a similar mailing list for Fedora, for example .
Can you please create a new "ovirt-italian" / "italian" /
"italian-users" / "it-users" (@Mikey/Francesco - feel free
to chime in with your preferred name) mailing list?
Thanks in advance.
After merging a patch for a 3.6.3 bug on the ovirt-engine-3.6 branch the
bug is moved to MODIFIED, since the 3.6.3 branch was opened yesterday the
bug should stay in POST until merged in ovirt-engine-3.6.3 branch as well
can you please add support for access rights to jenkins jobs to yaml files?
Max started doing something here: https://gerrit.ovirt.org/42340
but never finished.
Goal is to allow at least to specify who can trigger a job manually.
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
adding also infra team for visibility on the change in CI.
On Fri, Dec 11, 2015 at 4:19 PM, Francesco Romani <fromani(a)redhat.com>
> ----- Original Message -----
> > From: "Yaniv Bronheim" <ybronhei(a)redhat.com>
> > To: devel(a)ovirt.org, "Francesco Romani" <fromani(a)redhat.com>, "Nir
> Soffer" <nsoffer(a)redhat.com>, "Piotr Kliczewski"
> > <pkliczew(a)redhat.com>
> > Cc: "danken" <danken(a)redhat.com>, "David Caro" <dcaroest(a)redhat.com>,
> "Eyal Edri" <eedri(a)redhat.com>
> > Sent: Thursday, December 10, 2015 6:46:37 PM
> > Subject: Automation CI for vdsm
> > We want to allow developers to trigger the script once reviews and
> > verification are ready (last step before merge). To do so we agreed to
> > Continues Integration flag for each vdsm patch.
This flag will be called 'Workflow' or we can name it otherwise, we just
need to choose what makes sense.
David/Yaniv - Please correct me if I'm wrong.
> Once this flag will be
> > signed with +1 it will trigger Jenkins CI to run the check-merged script
> > (adding new button to gerrit is not an option - you can image that flag
> > a trigger button), on success Jenkins CI flag will turn to +2. on fail
> > we'll get -1 and once new patchset is ready the developer will remove the
> > +1 and add it back to the Continues Integration flag to re-trigger the
> > Please ack the process before we move on with that
> Sounds good, even though I'm a little scared (just gut feeling, no evidence
> whatsoever) that this could add even more complexity and fragility to the
> In the long run, when this is reliable, it will help greatly.
> In the short term, I'm scared because this can lead to false positives and
> Let me stress I don't have concrete item to share or specific flaws.
> As action item on me, I will find some time next week to check virt
> functional tests,
> to see if they need some fixes, work reliably and so forth
> > The patch for those scripts still under review and testing -
> > https://gerrit.ovirt.org/#/c/48268
> Will review asap.
> Francesco Romani
> RedHat Engineering Virtualization R & D
> Phone: 8261328
> IRC: fromani
Supervisor, RHEV CI
EMEA ENG Virtualization R&D
Red Hat Israel
irc: eedri (on #tlv #rhev-dev #rhev-integ)