- Original Message -
> From: "Nir Soffer"
> To: "devel" , "Francesco Romani" ,
> "Eldad Marciano" ,
> "Vinzenz Feenstra" , "Dan Kenigsberg"
> , "Piotr Kliczewski"
>
Hi all,
I noticed that Eldad posted profiling result from 144 cores / 144 vms run:
See https://bugzilla.redhat.com/attachment.cgi?id=1128028
Looking at the profile bellow:
1. Why _rtnl_link_alloc_cache is so expensive?
called only 389 times, but the most expensive call
2. Creating
On Wed, Feb 17, 2016 at 5:47 PM, Yevgeny Zaspitsky wrote:
> Piotr,
>
> According to our checks engine succeed connecting VDSM through ipv6 once the
> work you've reminded has been done. So it looks like jsonrpc is agnostic to
> IP layer it uses underneath.
>
I never tested
Hi everyone,
I've just uploaded a patch that fixes this problem.
You no longer suppose to experience any difficulty creating/editing VMs.
Sorry for the temporary inconvenience.
FYI,
Tomer
- Original Message -
From: "Jakub Niedermertl"
To: "Greg Sheremeta"
Piotr,
According to our checks engine succeed connecting VDSM through ipv6 once
the work you've reminded has been done. So it looks like jsonrpc is
agnostic to IP layer it uses underneath.
Could you please elaborate on why do you think that we break backward
compatibility.
If you compare the
On Wed, Feb 17, 2016 at 08:59:20AM -0500, Martin Perina wrote:
> I think we have created a bug [1] for fencing related ipv6 support.
>
> Martin
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1194055
>
> - Original Message -
> > From: "Eli Mesika"
> > To:
I think we have created a bug [1] for fencing related ipv6 support.
Martin
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1194055
- Original Message -
> From: "Eli Mesika"
> To: "Yevgeny Zaspitsky"
> Cc: "devel" , "Michael
This will require a change also in the fencing arguments
We will have to add inet4_only inet6_only support from the UI/API as a common
field (like port/slot/secure)
See
https://fedorahosted.org/cluster/wiki/FenceArguments
Please add that as well to your doc.
- Original Message -
>
On 16/02/16 15:35, Francesco Romani wrote:
> * Francesco: the `convirt' module mostly (support containers with
> libvirt API) plus cleanup
Hi,
I assume this is a self written module for ovirt/libvirt to manage
containers? Is convirt the real name of it?
Because there seems to be another open
Thank you for the effort.
I have 2 comments:
- In [1] I do not see any information about using ipv6 in jsonrpc
code. I know that there was some work done on vdsm [2]
side but nothing on the engine side.
- We are about to break some backward compatibility so I suggest to
define new type which
10 matches
Mail list logo