Re: [ovirt-devel] [VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode

On Tue, Apr 4, 2017 at 6:33 PM, Michal Skrivanek wrote: > >> On 4 Apr 2017, at 17:26, Dan Kenigsberg wrote: >> >> On Tue, Apr 4, 2017 at 1:16 PM, Michal Skrivanek >> wrote: >>> >>> On 4 Apr 2017, at 12:10, Roy Golan

Re: [ovirt-devel] Engine error: No enum constant ProviderType.http://localhost:9696

On Tuesday, April 4, 2017 12:07:55 PM EDT Jakub Niedermertl wrote: > Hi, > > anyone else is experiencing following error message in engine log? > Yes its a problem with the new ovn provider. If you say no to installing it the problem should go away, or you can manually remove the ovn provider

Re: [ovirt-devel] Live demo session on how to debug oVirt GWT applications

Hello everyone, for those who missed my session, please find the recording at https://bluejeans.com/s/zij35/ (there are two chapters, because I've accidentally clicked "stop recording" during the session) slides are available at

[ovirt-devel] Engine error: No enum constant ProviderType.http://localhost:9696

Hi, anyone else is experiencing following error message in engine log? 2017-04-04 17:38:48,988+02 ERROR [org.ovirt.engine.core.bll.provider.GetAllProvidersQuery] (default task-101) [b421c4c1-1602-4c41-88f6-b5ff20888713] Query 'GetAllProvidersQuery' failed: No enum constant

Re: [ovirt-devel] [VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode

> On 4 Apr 2017, at 17:26, Dan Kenigsberg wrote: > > On Tue, Apr 4, 2017 at 1:16 PM, Michal Skrivanek > wrote: >> >> On 4 Apr 2017, at 12:10, Roy Golan wrote: >> >> >> >> On Tue, Apr 4, 2017 at 12:49 PM Yaniv Kaul

Re: [ovirt-devel] [VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode

On Tue, Apr 4, 2017 at 1:16 PM, Michal Skrivanek wrote: > > On 4 Apr 2017, at 12:10, Roy Golan wrote: > > > > On Tue, Apr 4, 2017 at 12:49 PM Yaniv Kaul wrote: >> >> On Tue, Apr 4, 2017 at 12:29 PM, Roy Golan

Re: [ovirt-devel] [VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode

I wonder why we not go in the same approach as we went for vm status changes. Why not to pull for older versions and expect a push from new implementation. This would allow as to keep current code as it is for backward compatibility purposes and create new one (reuse parts of the old one) for new

Re: [ovirt-devel] [OST] [HC] HE VM fails to start

Hello Sahina, I think I have a fix for that. Can I somehow trigger the test with VDSM refspec/custom RPMs? Thanks, Petr 2017-04-04 8:52 GMT+02:00 Dan Kenigsberg : > On Tue, Apr 4, 2017 at 9:28 AM, Sahina Bose wrote: >> Job's still failing on master. >>

Re: [ovirt-devel] [VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode

> On 4 Apr 2017, at 12:21, Roy Golan wrote: > > > > On Tue, Apr 4, 2017 at 1:16 PM Michal Skrivanek > wrote: >> On 4 Apr 2017, at 12:10, Roy Golan > > wrote:

Re: [ovirt-devel] [VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode

On Tue, Apr 4, 2017 at 1:16 PM Michal Skrivanek wrote: > On 4 Apr 2017, at 12:10, Roy Golan wrote: > > > > On Tue, Apr 4, 2017 at 12:49 PM Yaniv Kaul wrote: > > On Tue, Apr 4, 2017 at 12:29 PM, Roy Golan

Re: [ovirt-devel] [VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode

On Tue, Apr 4, 2017 at 12:49 PM Yaniv Kaul wrote: > On Tue, Apr 4, 2017 at 12:29 PM, Roy Golan wrote: > > I'm working on a POC lately on a change to stats collection and retrieval > by VDSM. The moto is to cut all we can from host/vm stats (possibly caps) >

Re: [ovirt-devel] [VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode

On Tue, Apr 4, 2017 at 12:29 PM, Roy Golan wrote: > I'm working on a POC lately on a change to stats collection and retrieval > by VDSM. The moto is to cut all we can from host/vm stats (possibly caps) > and report only core-business stuff to the engine. Engine will retrieve

[ovirt-devel] [VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode

I'm working on a POC lately on a change to stats collection and retrieval by VDSM. The moto is to cut all we can from host/vm stats (possibly caps) and report only core-business stuff to the engine. Engine will retrieve the rest through a 3rd party provider (nevermind what is it atm) Being

Re: [ovirt-devel] [OST] [HC] HE VM fails to start

Job's still failing on master. Could this be related to network patches that got merged on Mar 28, for instance https://gerrit.ovirt.org/#/c/74390/ ? On Thu, Mar 30, 2017 at 11:41 AM, Sahina Bose wrote: > The error in vdsm.log > > Traceback (most recent call last): > File