On Mon, Jan 29, 2018 at 9:40 AM Francesco Romani wrote:
> Hi all,
>
>
> It is time again to reconsider branching out the 4.2 stable branch.
>
> So far we decided to *not* branch out, and we are taking tags for ovirt
> 4.2 releases from master branch.
>
> This means we are
On Wed, Jan 10, 2018 at 6:04 PM Nir Soffer wrote:
> On Wed, Jan 10, 2018 at 11:38 AM Francesco Romani
> wrote:
>
>> On 01/09/2018 06:54 PM, Michal Skrivanek wrote:
>>
>>
>>
>> On 9 Jan 2018, at 18:48, Nir Soffer wrote:
>>
>> On Tue,
+1
On Tue, Jan 9, 2018 at 1:47 PM Piotr Kliczewski wrote:
> +1
>
> On Tue, Jan 9, 2018 at 12:43 PM, Dan Kenigsberg wrote:
>
>> Hello,
>>
>> I would like to nominate Milan Zamazal and Petr Horacek as maintainers
>> of vdsm stable branches. This job
a server using
> vdsm
> yajsonrpc code. I'm worried about incompatibilities between the go stomp
> library and our own stomp implementation, not used by any other code.
>
> When it works, we can convert vdsm-client to go :-)
>
> On Sat, Jul 15, 2017 at 8:53 AM Yaniv Bronheim <y
Erray !! :P Great work
On Wed, Jun 14, 2017 at 4:29 PM Alexander Wels wrote:
> Hi,
>
> I have just merged [1] which is a huge patch to update the look and feel of
> the webadmin UI to be more modern and based on Patternfly. I believe this
> is a
> huge step forward for the UI
do you still see that after merged? seems like broken version of lago in ci
On Mon, May 22, 2017 at 4:36 PM Nir Soffer wrote:
> I see these failure in check-merge
>
> *13:26:59* Error occured, aborting*13:26:59* Traceback (most recent call
> last):*13:26:59* File
>
> On Apr 23, 2017 5:21 PM, "Yaniv Bronheim" <ybron...@redhat.com> wrote:
>
> All, Great to hear the interest.
> Sandro - Maybe I can install sos-abrt package - I didn't try. However,
> ovirt collects only vdsm-sos report and I want to include this information
think about it much..
maybe it can be nice. From my point of you, having abrt output locally and
exposed by vdsm is enough for ovirt orchestration with abrt.
On Fri, Apr 21, 2017 at 2:38 PM Dan Kenigsberg <dan...@redhat.com> wrote:
> On Wed, Apr 19, 2017 at 5:43 PM, Yaniv Bronhe
Hi, I posted the new integration [1] to 4.1 -
https://gerrit.ovirt.org/#/q/topic:backport-abrt-intgr for review.
Abrt is a service that runs in parallel to vdsm and collect binaries and
python crashes under /var/run/tmp - to try that out you can crash a qemu
process or vdsm with signal -6 and
Thanks! I would mention it in the main ovirt-engine README file, its basic
usage and very useful.
On Tue, Apr 18, 2017 at 2:41 PM Martin Betak wrote:
> On Tue, Apr 18, 2017 at 9:52 AM, Roy Golan wrote:
>
>> Ever wanted to raise level of the engine logs and
The abrt packages are indeed not included. thanks for the report
https://gerrit.ovirt.org/#/c/74654/1/common/yum-repos/ovirt-master.repo
Verifying
On Sun, Mar 26, 2017 at 4:56 PM Yaniv Kaul wrote:
> 2017-03-26 09:50:47,235-04 ERROR
>
we merged https://gerrit.ovirt.org/#/c/71231/ yesterday, calling vdsm-tool
configure without specifying modules will run this new lvm configure.
didn't see any issues that can come up, but it is a regression
On Mon, Feb 6, 2017 at 10:26 AM, Yaniv Kaul wrote:
> +Nir
>
> On Feb
craziness .. cool thing though
On Mon, Jan 9, 2017 at 5:08 PM, Nir Soffer wrote:
> Hi all,
>
> Please enjoy this visualization of vdsm development since 2011:
> https://www.youtube.com/watch?v=Ui1ouZiENU0
>
> If you want to create your own:
>
> dnf install gourse ffmpeg
>
; On Sun, Jan 1, 2017 at 4:59 PM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
>
>> Hi,
>> I'm not sure if I'm right or wrong so before filing a bug let me know if
>> I don't miss anything - I think the audit log on fail deploy that says the
>> path for
Hi,
I'm not sure if I'm right or wrong so before filing a bug let me know if I
don't miss anything - I think the audit log on fail deploy that says the
path for the deploy log is wrong. few times I already faced that it points
to somewhere under /tmp/ovirt-host-deploy... but the log is actually
er this patch it used to work (check the jobs
after the merge)
so something in https://gerrit.ovirt.org/#/c/68078/ broke it
>
> On Thu, Dec 22, 2016 at 5:14 PM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
>
>> Hi guys and Leon,
>>
>> https://gerrit.ovirt.org/#
Hi guys and Leon,
https://gerrit.ovirt.org/#/c/68078/ broke the check-merged job with really
tough exception:
*15:23:34* sh: [17766: 1 (255)] tcsetattr: Inappropriate ioctl for
device*15:23:34* Took 2586 seconds*15:23:34* Slave went offline during
the build
Hello devels,
I just introduced ovirt-4.1 branch in vdsm - which will be the base for
ovirt-4.1 alpha build.
Now master is tagged v4.20.0 and first ovirt-4.1 tag is v4.19.1.
Basically it means that every fix that should be in 4.1 needs to be
backported and merged to ovirt-4.1 branch by fromani
On Wed, Nov 16, 2016 at 4:56 PM, Nir Soffer <nsof...@redhat.com> wrote:
> On Wed, Nov 16, 2016 at 9:35 AM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
> > Hi
> >
> > After merging
> > https://gerrit.ovirt.org/#/q/status:open+project
On Mon, Nov 14, 2016 at 6:51 PM, Sandro Bonazzola
wrote:
> I've been made aware of:
>
> commit 195937c2da592d9993ada7609aea84f64523a711
> Author: Nir Soffer
> Date: Sun Oct 9 20:05:36 2016 +0300
>
> build: Disable tests during build
>
> Tests
Hi
After merging
https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:cross-imports
we
need now for any new requirement to add a line in:
check-patch.packages.el7
check-patch.packages.fc24
check-merged.packages.el7
check-merged.packages.fc24
vdsm.spec.in
Dockerfile.centos
yes. the revert is in https://gerrit.ovirt.org/62922. check if you run
later commit and first remove all vdsm* to clean your env
On Mon, Sep 5, 2016 at 10:05 PM, Eyal Edri wrote:
> Did we end up reverting the VDSM change?
>
> I see now failures on OST with the version issues
yes, sounds like that. please take the patch, I plan to publish new build
with that change and without the exclusive arch that I added
On Fri, Sep 2, 2016 at 3:59 PM, Nir Soffer wrote:
> On Fri, Sep 2, 2016 at 2:26 PM, Sandro Bonazzola
> wrote:
>
>>
Hi,
In https://gerrit.ovirt.org/#/c/62672 we removed the release from vdsm*
requirements. Although it sounds reasonable and quite safe, it was not.
In development env it causes mixup of versions when upgrading.
"yum install vdsm" will eventually cause this mixup as vdsm won't require
the newer
On Tue, Aug 2, 2016 at 11:06 AM, Martin Polednik
wrote:
> Hey devels,
>
> last week, I've been working on patch series that moves most of
> configuration and "static" files away from our source code to a dir
> called "static"[1]. (based on the previous' week VDSM weekly)
>
On Tue, Jul 19, 2016 at 4:56 PM, Tomáš Golembiovský
wrote:
> On Thu, 14 Jul 2016 17:25:28 +0300
> Nir Soffer wrote:
>
> > After https://gerrit.ovirt.org/#/c/46733/ you should be able to create
> > the pipeline in python like this:
> >
> > v2v =
Hi,
In oVirt-4.0 we introduced integration with metrics collectors, In [1] you
will find a guide for utilizing your environment to retrieve visualized
reports about hosts and vms statistics.
I encourage to try that out and send us requests for additional valuable
metrics that you think vdsm
On Mon, Jul 11, 2016 at 12:53 PM, Tomáš Golembiovský <tgole...@redhat.com>
wrote:
> On Wed, 6 Jul 2016 18:37:54 +0300
> Yaniv Bronheim <ybron...@redhat.com> wrote:
>
> > On Wed, Jul 6, 2016 at 5:07 PM, Tomáš Golembiovský <tgole...@redhat.com>
> > wrote:
&g
On Wed, Jul 6, 2016 at 5:07 PM, Tomáš Golembiovský <tgole...@redhat.com>
wrote:
> On Tue, 5 Jul 2016 11:18:58 +0300
> Yaniv Bronheim <ybron...@redhat.com> wrote:
>
> > On Tue, Jul 5, 2016 at 10:44 AM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
> >
>
On Tue, Jul 5, 2016 at 10:44 AM, Yaniv Bronheim <ybron...@redhat.com> wrote:
> Hi
> I do work to remove the cpopen usages from execCmd. Using std popen over
> py3 and subprocess32 over py2 which both implements the same api. The only
> gap is the output object for async
Hi
I do work to remove the cpopen usages from execCmd. Using std popen over
py3 and subprocess32 over py2 which both implements the same api. The only
gap is the output object for async calls that we need to align with the
standard implementation and modify our current usages. I don't think that
On Sun, May 29, 2016 at 3:31 PM, Dan Kenigsberg wrote:
> On Sun, May 29, 2016 at 02:53:41PM +0300, Nir Soffer wrote:
> > On Sun, May 29, 2016 at 12:36 PM, Dan Kenigsberg
> wrote:
> > > On Sat, May 28, 2016 at 03:16:10PM +0300, Nir Soffer wrote:
> > >> Hi
ok .. https://gerrit.ovirt.org/56122 . and
https://gerrit.ovirt.org/#/c/55604/ can get in too
On Thu, Apr 14, 2016 at 10:59 AM, Nir Soffer <nsof...@redhat.com> wrote:
> On Thu, Apr 14, 2016 at 10:45 AM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
> > I don't think t
Romani" <from...@redhat.com>
> *Cc: *"Eyal Edri" <ee...@redhat.com>, "Dan Kenigsberg" <dan...@redhat.com>,
> "devel" <devel@ovirt.org>, "Yaniv Bronheim" <ybron...@redhat.com>, "Nir
> Soffer" <nsof...@redhat.com>
&
right, since 3.5 we use libvirt default configurations which is to report
logs to syslog, about the cmd line log to /var/log/libvirt/qemu/.. I think
its done by libvirt - doesn't it? probably you can disable it by some
libvirtd.conf\qemu.conf line . vdsm should not change it by default
On Thu,
yep, we don't wait for the process inside cpopen code - we expect the
caller to take care of it. if you use execCmd with sync=False (as in
virt-v2v) - you have to take care for killing the process and wait for its
pid after its done - you can see that with the fix we raise exception and
this
will be higher
On Tue, Mar 8, 2016 at 10:52 AM, Sandro Bonazzola <sbona...@redhat.com>
wrote:
>
>
> On Tue, Mar 8, 2016 at 9:45 AM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
>
>> No. the jobs alright. ovirt-3.6 build each night will output vdsm
>> 4.17.19. older
at 10:30 AM, Sandro Bonazzola <sbona...@redhat.com>
wrote:
>
>
> On Tue, Mar 8, 2016 at 9:07 AM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
>
>> its reasonable that you can't upgrade 4.17.23 to 4.17.19 and it shouldn't
>> be that way.. latest (which a
wrote:
>
>
> On Mon, Mar 7, 2016 at 1:29 PM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
>
>> Again, I should understand the direction you ack here ... and its not
>> clear in any way I try to read it
>> lets summaries current status:
>> master == v4.17.999
I suspect that it relates to the desire to remove the dependency in
vdsm-cli - https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and
Fabian created the iso without vdsm-cli so the deploy failed in the middle.
after it failed it couldn't recover even when vdsm-cli was installed.
sounds
On Tue, Feb 23, 2016 at 10:54 PM, Nir Soffer <nsof...@redhat.com> wrote:
> On Tue, Feb 23, 2016 at 6:30 PM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
>
>> (Nir, Adam, YanivB, Dan, Milan, Piotr, Francesco, Martin Polednik, Edward)
>>
>> - Some of us sta
(Nir, Adam, YanivB, Dan, Milan, Piotr, Francesco, Martin Polednik, Edward)
- Some of us started to work on refactoring for python3, basic file
movements and improving testings
- We added functional tests to check-merged automation script - currently,
for some reason, it doesn't run tests that
On Mon, Feb 22, 2016 at 9:06 PM, Yaniv Kaul <yk...@redhat.com> wrote:
> On Mon, Feb 22, 2016 at 5:25 PM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
>
>> Hi,
>> I added recently to check-merged phase a job for automatic functional
>> test run. see for
Hi,
I added recently to check-merged phase a job for automatic functional test
run. see for example
http://jenkins.ovirt.org/job/vdsm_master_check-merged-fc23-x86_64/52/
https://gerrit.ovirt.org/#/c/48268/58/automation/check-merged.sh -
generally, it installs lago in the jenkins machine, set up
(ybronhei, piotr, fromani, mzamazal, edwafh, ydary)
Hi,
Yaniv Dary raised the desire to modify vdsm name to ovirt-host-agent. The
motivation is to align with ovirt components (ovirt-agent, ovirt-engine,
ovirt-host-deploy, ovirt-node and so on). In addition, vdsm versions
are not aligned
I'd love to have such handling also in our rpm build..
we started some work in https://gerrit.ovirt.org/#/c/42491 , lets try to
align the handling in both debian and fedora packaging.
feel free to post a patch for that as well and I promise to push it forward
On Mon, Jan 25, 2016 at 10:14 AM,
On Sat, Jan 23, 2016 at 8:05 PM, Nir Soffer <nsof...@redhat.com> wrote:
> On Sat, Jan 23, 2016 at 7:11 PM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
> > any updates about that?
> >
> > https://gerrit.ovirt.org/#/c/52357/ - this can be verified and get it
&g
com>
wrote:
> - Original Message -
> > From: "Yaniv Bronheim" <ybron...@redhat.com>
> > To: "devel" <devel@ovirt.org>, "Shahar Havivi" <shav...@redhat.com>,
> "Francesco Romani" <from...@redhat.com>, "Ni
If in debian we will have different set of rpms for vdsm, can you please
also add section about how to build and install vdsm over debian in
https://www.ovirt.org/Vdsm_Developers ?
On Fri, Jan 22, 2016 at 3:34 PM, Milan Zamazal wrote:
> Thank you for clarification. So as
Hi all,
(Participated: Piotr, Francesco, Adam, Nir, Edy and I)
We discussed about the following topics:
Python3 - terminating contextmanager is ready
https://gerrit.ovirt.org/51407 - this allows us to remove deathSignal
usages and safely kill processes on failures.
Francesco already covered
Hi guys,
Following the work to omit deathSignal attribute from our cpopen
implementation we posted https://gerrit.ovirt.org/51407 which is ready for
use.
Currently locations that should use it are:
(I wrote above who I expect to check the area and post a patch for that -
we'll discuss it during
(edwad, nsoffer, pkliczew, alitke, fromani, ybronhei)
Python3 current work and gaps -
https://docs.google.com/a/redhat.com/spreadsheets/d/180F-C1jU54ajUn7TuR-NwrKRZY1IiZI1Z8U5HWbvEvM/edit?usp=sharing
Current main gaps are the removal of deathSignal to unify cpopen api to
standard Popen api, and
(fromani, nsoffer, ybronhei, alitke)
- Removing xmlrpc for good - who should accept it? where do we stand with
full jsonrpc client ? (we didn't get to any conclusions and said that we'll
reraise this topic next week with pioter)
- Moving from nose to pytest - generally good approach to
On Sun, Jan 10, 2016 at 10:26 PM, Nir Soffer wrote:
> Hi all,
>
> We are having vdsm call each Tuesday, 17:00 – 17:30
> at https://bluejeans.com/2061366027
>
> Topics for this week call:
> - jsonrpc client
> - Killing vdsClient
> - Removing xmlrpc
> - Anything else *you* like
Nothing hiding there.. the automation CI method is the only thing we need
to keep to avoid leaving garbage that nobody looks at
On Tue, Dec 22, 2015 at 9:59 AM, Barak Korren wrote:
> > Please remove it - unless you have plans to revert the
> > automation/*-based approach.
>
On Sun, Dec 20, 2015 at 9:46 AM, Nir Soffer <nsof...@redhat.com> wrote:
> On Sun, Dec 20, 2015 at 8:49 AM, Barak Korren <bkor...@redhat.com> wrote:
> > On 19 December 2015 at 13:05, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
> >> for some runs it is inst
ests pass or disabled.
>
> There is no point in broken or flaky functional tests.
>
> On Wed, Dec 16, 2015 at 5:34 PM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
> > So its not stable. It won't block merges and at least give us report
> after
> > each merge.
pep8 violation that was introduced by commit
2a053f98a1cf1fb717b90b1900bf4c7b4318d254
there you go - https://gerrit.ovirt.org/#/c/50383
On Sun, Dec 13, 2015 at 12:23 PM, Fred Rolland wrote:
> Hi ,
>
> I have issues building the engine on master.
>
> The build finishes quick
We currently manage debian packaging files under
https://gerrit.ovirt.org/#/q/project:releng-tools instead of in the project
itself. imo it makes it harder, as developer won't update the debian folder
while changing spec parts , which makes much more observation work for
Simone..
But if we keep to
Hi all,
We want to run functional tests as part of Vdsm CI for each patch before
merge. Therefore we need to declare how to automate this process without
overloading our jenkins machines.
The functional tests will run using lago (https://github.com/ovirt/lago) -
It will initiate multiply vms,
Yes, sounds like the overriding of vdsm.conf is an issue that we need to avoid
what I wonder is that it is not a regression, old versions of vdsm also
overwrited the vdsm.conf file during deploy, so how is it harming us only now?
please open a bug on the overwriting issue
Thanks.
Yaniv
- Original Message -
From: Sven Kieske s.kie...@mittwald.de
To: Alon Bar-Lev alo...@redhat.com, Eli Mesika emes...@redhat.com
Cc: engine-devel@ovirt.org
Sent: Thursday, December 12, 2013 2:16:53 PM
Subject: Re: [Engine-devel] CodeQuality/Automated Checking
Yeah of course it's
Hey,
Most of the issues you mentioned in slides 11-13
(http://www.ovirt.org/images/5/57/Shanghai-VDSM-on-Ubuntu.pdf) are already
solved (if not all of them),
If there are more issues to solve can you please open RFE bz on them to close
those gaps (like making the services' names configurable)?
- Original Message -
From: Zhou Zheng Sheng zhshz...@linux.vnet.ibm.com
To: Ayal Baron aba...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, vdsm-de...@lists.fedorahosted.org
Sent: Wednesday, September 25, 2013 5:16:16 AM
Subject: Re: [Engine-devel] [vdsm] stale gerrit patches
+1
- Original Message -
From: Itamar Heim ih...@redhat.com
To: Liran Zelkha liran.zel...@gmail.com
Cc: engine-devel engine-devel@ovirt.org, infra in...@ovirt.org
Sent: Sunday, September 15, 2013 12:57:29 PM
Subject: Re: [Engine-devel] fake VDSM as oVirt project?
On 09/13/2013
, Yaniv Bronheim ybron...@redhat.com
Sent: Sunday, May 19, 2013 1:15:29 PM
Subject: Re: [Engine-devel] Odd Host Activation with mgmt-if
Most probably, when SSL is enabled and configured properly this will not
work...
One need:
vdsClient -s hostname_as_specified_in_certificate
Agree.. Until we'll upload better solution for the zombies issue I prefer to
merge that patch.
- Original Message -
From: Dan Kenigsberg dan...@redhat.com
To: Dead Horse deadhorseconsult...@gmail.com
Cc: engine-devel@ovirt.org, Yaniv Bronhaim ybron...@redhat.com, Royce Lv
67 matches
Mail list logo