Currently we filter out local devices in getDeviceList()
I'd assume you'd want that to stop.
This means having the engine filter them out according to the
flow.
This has backward compatibility implications. It can easily be solved
with making the current behaviour the default and adding an "include
I had to use Wireshark to try and find what happens
to messages in transit.
To help me filter messages in Wireshark I wrote a
quick and dirty STOMP dissector.
You all can use it too.
Help in making it less dirty is more than welcome.
https://github.com/ficoos/wireshark-stomp-plugin
It's well known.
The problem is that there is no simplejson in EL6\7
(unless the situation changed since I last checked).
I already did extensive profiling on the jsonrpc framework.
The patches [1] move us on par with XML-RPC for sequential requests and
*way* faster for concurrent commands.
There
First let me say kudos on kickstarting the discussion
having a CLI client is essential for admins and (as the
current CLI can show us) it's important to get it right.
We currently have a Python client used in testing.
It's efficient and low level enough to be used by
any consumer of the VDSM API.
- Original Message -
> From: "Michal Skrivanek"
> To: "Saggi Mizrahi"
> Cc: devel@ovirt.org, "Martyn Taylor"
> Sent: Wednesday, October 22, 2014 10:55:34 AM
> Subject: Re: [ovirt-devel] ioprocess 0.14.0 released
>
>
- Original Message -
> From: "Nir Soffer"
> To: "Saggi Mizrahi"
> Cc: devel@ovirt.org, "Douglas Schilling Landgraf" ,
> "Barak Azulay" , "Dan
> Kenigsberg"
> Sent: Wednesday, October 22, 2014 12:26:49 PM
> Su
As those of you that have been developing VDSM might know
some time ago yappi profiling support was added to VDSM.
This was a good idea but yappi has no fedora\el RPMs
which forced each developer to find and download yappi
from around the internet.
Also, I personally don't like using disutils as t
ioprocess 0.14.0 has been tagged and released.
The changelog includes:
- python-bindings: IOProcess objects can be collected by the GC
- python-bindings: Slave processes can optionally be collected
by zombie reaper
It's recommended that everyone upgrade to the latest version.
- Original Message -
> From: "Itamar Heim"
> To: "Saggi Mizrahi" , "Balamurugan Arumugam"
>
> Cc: devel@ovirt.org
> Sent: Monday, September 29, 2014 10:34:29 AM
> Subject: Re: [ovirt-devel] physical disk management for gluster in vdsm
- Original Message -
> From: "Balamurugan Arumugam"
> To: "Saggi Mizrahi"
> Cc: devel@ovirt.org
> Sent: Thursday, September 25, 2014 3:41:05 AM
> Subject: Re: [ovirt-devel] physical disk management for gluster in vdsm
>
>
> ----- Ori
- Original Message -
> From: "Balamurugan Arumugam"
> To: devel@ovirt.org
> Sent: Tuesday, September 23, 2014 2:46:59 PM
> Subject: [ovirt-devel] physical disk management for gluster in vdsm
>
>
> Hi All,
>
> Currently gluster management in ovirt is not complete if disks in hosts are
ioprocess 0.12.0 has been released
The only chage is a fix for the memory leak in the python bindings.
It is recommended update for ever
You can find the build for el\fc in bodhi
Don't forget to give karma ;)
https://admin.fedoraproject.org/updates/search/ioprocess-0.12.0
__
Hi, ioprocess 0.10.0 released.
Major changes are:
* Fixed to races in queue limiting
* Fixed unsafe use of strerror
* Fixed cases where log lines would
not be broken properly
Most of the changes are for issues that
are very rare or are not yet utilized by
VDSM so there is no immediate need to
u
In 3.6 we are intending to have events in the json-rpc interface.
That means that a lot of the problems this is trying to fix will
no longer be an issue.
Changes about VM status will be sent as soon as they are available
instead of when the engine is polling.
This means that the messages will be
- Original Message -
> From: "Nir Soffer"
> To: "Saggi Mizrahi"
> Cc: "Francesco Romani" , devel@ovirt.org, "Michal
> Skrivanek" , "Federico
> Simoncelli" , "Dan Kenigsberg"
> Sent: Sunday, July 13, 2014 2
the same interface internally.
- Original Message -
> From: "Nir Soffer"
> To: "Francesco Romani"
> Cc: devel@ovirt.org, "Michal Skrivanek" , "Federico
> Simoncelli" , "Saggi
> Mizrahi" , "Dan Kenigsberg"
> Sent: Satu
- Original Message -
> From: "Nir Soffer"
> To: "Saggi Mizrahi"
> Cc: "Francesco Romani" , devel@ovirt.org, "Federico
> Simoncelli" , "Michal
> Skrivanek"
> Sent: Sunday, July 6, 2014 6:21:35 PM
> Subject: R
- Original Message -
> From: "Francesco Romani"
> To: devel@ovirt.org
> Sent: Friday, July 4, 2014 1:09:44 PM
> Subject: [ovirt-devel] [VDSM] VDSM threads as in vdsm 4.15.0
>
> Hi,
>
> I'm trying to enumerate all the daemon threads VDSM uses, as in 4.15.0
> (to be exact, as in master 3
The more I think about it the more it looks like it's
purely a libvirt issue. As long as we can make calls
that get stuck on D state we can't scale under stress.
In any case, seems like having an interface like.
libvirtConnectionPool.request(args, callback)
Would be a better solution than a thre
Hi, we moved all of our stuff from github to
ovirt.gerrit.org.
If you had pending pull-requests for:
* ioprocess
* cpopen
* pthreading
Please resend them on Gerrit.
Don't forget to update your git/config.
ssh://gerrit.ovirt.org:29418/pthreading
ssh://gerrit.ovirt.org:29418/ioprocess
ssh://gerr
t; Sent: Wednesday, June 18, 2014 12:25:11 PM
> Subject: Re: [ovirt-devel] Github Repositories
>
> On Wed, Jun 18, 2014 at 11:51:20AM +0300, Roy Golan wrote:
> > On 06/17/2014 02:31 AM, Nir Soffer wrote:
> > >- Original Message -
> > >>From: "E
- Original Message -
> From: "Martin Polednik"
> To: devel@ovirt.org
> Sent: Tuesday, June 24, 2014 1:26:17 PM
> Subject: [ovirt-devel] [vdsm] Infrastructure design for node (host) devices
>
> Hello,
>
> I'm actively working on getting host device passthrough (pci, usb and scsi)
> expo
It's good to see us moving away from minidom.
I do think there is a place though to abstract out
common use cases so we are not tied to an API and that
we do the optimal thing more most use cases.
- Original Message -
> From: "Francesco Romani"
> To: devel@ovirt.org
> Sent: Friday, June 2
- Original Message -
> From: "Nir Soffer"
> To: "Saggi Mizrahi"
> Cc: devel@ovirt.org, "Yeela Kaplan" , bazu...@redhat.com,
> "Dan Kenigsberg"
> Sent: Sunday, June 29, 2014 2:48:49 PM
> Subject: Re: Failed to run &q
om: "Dan Kenigsberg"
> > > To: "Nir Soffer"
> > > Cc: "ybronhei" , "Oved Ourfali" ,
> > > "Eli Mesika" , "Yeela
> > > Kaplan" , "Saggi Mizrahi"
> > > Sent: Thursday, June 26, 20
We are moving all ovirt stuff from my own user to
the newly created ovirt-infra group on github.
Update your git remotes!
https://github.com/ovirt-infra
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
sort of infra we would not do it. I just think it would probably
be tied to some common algorithm or idiom than something truly generic
used by every API call.
Hope I made things clearer, sorry if I came out a bit rude.
I'm off, I have my country's birthday to celebrate.
- Ori
- Original Message -
> From: "Nir Soffer"
> To: "Jiri Moskovcak"
> Cc: devel@ovirt.org
> Sent: Monday, May 5, 2014 1:01:12 AM
> Subject: Re: [ovirt-devel] vdsm disabling logical volumes
>
> - Original Message -
> > From: "Jiri Moskovcak"
> > To: "Nir Soffer"
> > Cc: devel@ovi
That was quick. Thanks!
- Original Message -
> From: "Vinzenz Feenstra"
> To: "Saggi Mizrahi" , "Dan Kenigsberg"
> , "Douglas Landgraf"
> , "ybronhei" , "Federico
> Simoncelli"
> Cc: devel@ovirt.org
> Sen
I'd appreciate some karma.
https://admin.fedoraproject.org/updates/ioprocess-0.3-1.fc20
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
IIC the reason we have a separate package for the schema is because
we had the possibility of distributing it with vdsClient but seeing
as the in the future we would probably get it from the server we
could remove the schema package.
- Original Message -
> From: "Dan Kenigsberg"
> To: "P
- Original Message -
> From: "David Teigland"
> To: "Nir Soffer"
> Cc: "Dan Kenigsberg" , "Saggi Mizrahi"
> , devel@ovirt.org, "Federico
> Simoncelli" , "Allon Mureinik"
> Sent: Wednesday, April 30, 2014 8:
The thread became a bit too long for me to follow who said what when.
So I'll just say how things are going to work:
VDSM is going to have a a non disk persistent tasks.
The only reason I'm even giving a way to list running
tasks is so that legacy operations can use it.
New verbs should not rely
Yaniv synced the github version with the code
that was released.
1.3 is now tagged.
https://github.com/ficoos/cpopen/tree/1.3.0
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
34 matches
Mail list logo
