On Fri, Jan 22, 2016 at 5:52 PM, Milan Zamazal wrote:
> Yaniv Bronheim writes:
>
>> 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
On Fri, Jan 22, 2016 at 5:33 PM, Sandro Bonazzola wrote:
> Hi:
> http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Disabled/job/vdsm_master_storage-tests_wip_testing/
> is disabled since may 2015 and marked as wip.
> Looks like it's not really a WIP... Can we delete it?
>
On Fri, Jan 22, 2016 at 11:28 AM, Piotr Kliczewski
wrote:
> On Thu, Jan 21, 2016 at 5:02 PM, Milan Zamazal wrote:
>> I work on inclusion of Vdsm into Debian. I don't know what are the
>> reasons for having separate `infra', `xmlrpc', `yajsonrpc',
On Thu, Jan 21, 2016 at 5:02 PM, Milan Zamazal wrote:
> I work on inclusion of Vdsm into Debian. I don't know what are the
> reasons for having separate `infra', `xmlrpc', `yajsonrpc', and
> `jsonrpc' packages.
>
- infra package contains infra related modules like
On Fri, Dec 18, 2015 at 3:06 PM, Sandro Bonazzola
wrote:
>
>
> On Tue, Dec 1, 2015 at 9:44 AM, Sandro Bonazzola
> wrote:
>
>>
>>
>> On Mon, Nov 30, 2015 at 2:11 PM, Dan Kenigsberg
>> wrote:
>>
>>> On Mon, Nov 30, 2015 at 01:11:25PM
Hi,
in oVirt 4.0 the RestApiSessionAcquired event will be replaced
with API to create authenticated requests for Engine services.
Using REST API persistent session mechanism where UI acquires
a single session to be shared by all UI plugins led us to many
problems in the past, typically observed
Yaniv Bronheim writes:
> 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 ?
Sure, I'm going to update Debian information on Wiki (as well as
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
FYI, when I performed my simple Vdsm leak test some time ago, I've found
a leak in Python multiprocessing module, where
multiprocessing.util._afterfork_registry dictionary grows on each
supervdsm call. It's not much dramatic from the point of memory usage
but maybe the possibly large dictionary
Hi:
http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Disabled/job/vdsm_master_storage-tests_wip_testing/
is disabled since may 2015 and marked as wip.
Looks like it's not really a WIP... Can we delete it?
If noone take ownership, we'll delete it on February 1st.
--
Sandro Bonazzola
Better
10 matches
Mail list logo