dynamic ownership changes
by Martin Polednik
Hey,
I've created a patch[0] that is finally able to activate libvirt's
dynamic_ownership for VDSM while not negatively affecting
functionality of our storage code.
That of course comes with quite a bit of code removal, mostly in the
area of host devices, hwrng and anything that touches devices; bunch
of test changes and one XML generation caveat (storage is handled by
VDSM, therefore disk relabelling needs to be disabled on the VDSM
level).
Because of the scope of the patch, I welcome storage/virt/network
people to review the code and consider the implication this change has
on current/future features.
[0] https://gerrit.ovirt.org/#/c/89830/
mpolednik
6 years
oVirt CI now supports Fedora 28
by Barak Korren
Since Fedora 28 was released yesterday, we've added support for it in
the oVirt CI system.
To use Fedora 28 just use 'fc28' as you would for other Fedora
versions in the CI YAML files and/or file extensions in the
'automation/' directory.
The synchronisation for our local mirror is ongoing at this time, so
until it is done, the upstream Fedora mirrors will be used, this can
cause some breakage.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
6 years
Broken deps wihle testing master? Here some info
by Sandro Bonazzola
Hi,
ovirt-release-master enables testing repos from CentOS.
Testing repos are now switching to CentOS 7.5.1804 so you now need to
enable also the CR repo when testing master on CentOS.
CentOS 7.5 should be released this week or in worst case next week, so this
is just a temporary issue while 7.5 is being rolled out.
oVirt release 4.2 uses stable repos and is not affected by this temporary
glitch.
Thanks,
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>
<https://redhat.com/summit>
6 years
Re: [ovirt-devel] default maintainers plugin for other projects
by Barak Korren
(adding devel because this might be interesting for others).
On 1 May 2018 at 21:16, Greg Sheremeta <gshereme(a)redhat.com> wrote:
> How would I get this plugin added to ovirt-engine-dashboard and
> ovirt-engine-node* ?
>
Its already available for all projects in gerrit.ovirt.org.
> And then how would I configure it? (Add myself as a default, at least)
>
Two ways:
With the GUI:
-----------------
In Gerrit UI go to:
Admin -> Projects -> (Old UI) -> (Your project) -> Reviewers (from top bar)
Fill in filter (A file glob pattern - can be '*') and reviewer (An email
address ora gerrit group ) and click "Add".
Don't forget to switch back to new UI from the bottom right link.
>From the command line
-------------------------------
In a Git clone of the relevant project do:
# git fetch origin refs/meta/config:meta-config
# git checkout meta-config
Then you can edit the 'reviewers.config' file (Make it if it isn't there)
and put in something like the following:
[filter "*"]
reviewer = jenkins-maintainers
reviewer = dron(a)redhat.com
Once you're done with it commit the change and push it with:
# git push -u origin meta-config refs/meta/config
Since we have '-u' there, the next time around you change the 'meta-config'
branch you can just do:
# git push -u origin
And that's about it.
One thing to note - every project has a '<project-name>-maintainers' group,
so its useful to add it it default.
> ---------- Forwarded message ----------
> From: Roy Golan <rgolan(a)redhat.com>
> Date: Mon, Jun 19, 2017 at 7:17 AM
> Subject: Re: [ovirt-devel] [ENGINE][ACTION_NEEDED] - default maintainers,
> per path
> To: devel <devel(a)ovirt.org>
>
>
> The patch is now merged and the it should start working immediately. For
> anyone who is listed as a default reviewer I suggest to test it with a test
> patch by some other submitter. (except for those who used groups of course)
>
> Thanks everyone for the cooperation on this.
>
>
> On Mon, May 29, 2017 at 2:24 PM Roy Golan <rgolan(a)redhat.com> wrote:
>
>> Hi all,
>>
>> Some time ago the infra team enabled *gerrit default reviewer plugin*
>> which you probably noticed if you logged in to gerrit.
>>
>> What we can do is for example set the stable branch maintainers per
>> branch automatically:
>>
>> [filter "branch:ovirt-engine-4.1"]
>> reviewer = stableBranchMaintainersGroup
>>
>> Put people based on path:
>>
>> [filter "branch:master file:^frontend/.*"]
>> reviewer = j.r.r.t(a)shire.me
>>
>>
>>
>> *Action Needed:*
>> Nominate yourself, or others, by amending this patch online [1]. Once
>> this patch is fully acked and agreed we will merge it. If something can't
>> get consensus we will defer it from the patch till maintainers agree.
>>
>> [1] https://gerrit.ovirt.org/#/c/77488/
>>
>>
>>
>>
>>
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> <https://www.redhat.com/>
>
> gshereme(a)redhat.com IRC: gshereme
> <https://red.ht/sig>
>
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
6 years
