----- Original Message -----
From: "Nir Soffer" <nsoffer(a)redhat.com>
To: "Francesco Romani" <fromani(a)redhat.com>
Cc: "devel" <devel(a)ovirt.org>
Sent: Tuesday, March 29, 2016 6:00:56 PM
Subject: Re: [ovirt-devel] [vdsm] new internal stable modules + proposal
On Tue, Mar 29, 2016 at 6:12 PM, Francesco Romani <fromani(a)redhat.com> wrote:
> in the last Vdsm developer call we agreed to promote a few modules in the
> common repository.
> The common repository provides the additional guarantees over regular
> modules in lib/vdsm/
> - stable API
> - (thus) safe to use across verticals
> the planned moves are:
> lib/vdsm/schedule.py -> lib/vdsm/common/schedule.py
I think we want to move also the executor, used by virt and jsonrpc.
We plan to move all storage jobs
to the executor.
> lib/vdsm/periodic.py -> lib/vdsm/common/periodic.py
Is it used outside of virt?
Yes, sorry, I meant executor.py. Periodic.py will stay in virt for a little more.
> lib/vdsm/virt/api.py -> lib/vdsm/common/api.py
> Question is if those modules should go under common/ or under another
> subdirectory, maybe infra?
I would not add infra package, common *is* infra.
OK, to explain further we have already
BTW I'm fine using lib/vdsm/common/ directly.
The move will be done this friday unless anyone objects.
RedHat Engineering Virtualization R & D