On Wed, Oct 17, 2012 at 10:07:43AM -0500, Adam Litke wrote:
Thanks for posting your idea on the list here. I like the idea of a more
fine-grained version query API. getVdsCapabilities has become too much of a
catch-all and I agree that something lighter is useful. I do think vdsm will
want
On Wed, Oct 17, 2012 at 11:44:54AM -0400, Laszlo Hornyak wrote:
- Original Message -
From: Adam Litke a...@us.ibm.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: vdsm-devel@lists.fedorahosted.org
Sent: Wednesday, October 17, 2012 5:09:12 PM
Subject: Re: [vdsm] vdsClient error
currently getVdsCaps() does a lot of unrelated things most of them have no
relation to capabilites.
This was done because of HTTP overhead. Instead of calling multiple commands we
will call one that does everything.
I agree with the suggestion that getVdsCaps() will actually return the
On 10/18/2012 12:13 PM, Alon Levy wrote:
On 10/16/2012 12:18 AM, David Jaša wrote:
Ewoud Kohl van Wijngaarden píše v Po 15. 10. 2012 v 22:46 +0200:
On Tue, Oct 16, 2012 at 12:51:23AM +0800, Xu He Jie wrote:
[SNIP]
Hi, Adam, Could you explain more detail about how streaming API
can
survive a
On 10/18/2012 06:03 PM, Saggi Mizrahi wrote:
currently getVdsCaps() does a lot of unrelated things most of them have no
relation to capabilites.
This was done because of HTTP overhead. Instead of calling multiple commands we
will call one that does everything.
I agree with the suggestion that
On 10/18/2012 08:34 PM, Itamar Heim wrote:
On 10/18/2012 06:03 PM, Saggi Mizrahi wrote:
currently getVdsCaps() does a lot of unrelated things most of them
have no relation to capabilites.
This was done because of HTTP overhead. Instead of calling multiple
commands we will call one that does
On 10/18/2012 09:13 PM, Dave Allan wrote:
On Thu, Oct 18, 2012 at 02:21:44AM +0200, Itamar Heim wrote:
On 10/15/2012 07:41 PM, Dave Allan wrote:
On Fri, Oct 12, 2012 at 11:25:47AM -0500, Ryan Harper wrote:
* Adam Litke a...@us.ibm.com [2012-10-12 08:13]:
On Fri, Oct 12, 2012 at 04:55:20PM
I don't see how pyinotify is even related to storage stats.
It doesn't work with NFS and is a bit flaky when it comes to VFSs like proc or
dev.
Also it doesn't check liveness or latency so the events don't really give us
anything useful.
The data is being taken from cache. I assume there is a
18.10.2012 18:03, Saggi Mizrahi kirjoitti:
currently getVdsCaps() does a lot of unrelated things most of them have no
relation to capabilites.
This was done because of HTTP overhead. Instead of calling multiple commands
we will call one that does everything.
skip /
Can I please make a small
…
Just to be clear: yes, I think, that getVdsCapabilities() can and should
be optimized, but as well it has quite different meaning for different
purposes.
And what about capabilities «bag» — its format also can be a subject of
a change (e.g. long int bitmask ⇒ list of literals), but the version
On Thu, Oct 18, 2012 at 02:12:58AM -0400, lvro...@linux.vnet.ibm.com wrote:
Royce Lv has posted comments on this change.
Change subject: schema: New type VmParameters
..
Patch Set 4:
Adam,
I saw 3 kinds of vm
11 matches
Mail list logo