Re: [ovirt-devel] [vdsm] new internal stable modules + proposal

.org> >> Sent: Tuesday, March 29, 2016 6:00:56 PM >> Subject: Re: [ovirt-devel] [vdsm] new internal stable modules + proposal > [...] >> > Lastly, i have a proposal about better handling of those modules. >> > >> > First, the mere fact a module is p

Re: [ovirt-devel] [vdsm] new internal stable modules + proposal

- Original Message - > From: "Nir Soffer" <nsof...@redhat.com> > To: "Francesco Romani" <from...@redhat.com> > Cc: "devel" <devel@ovirt.org> > Sent: Tuesday, March 29, 2016 6:00:56 PM > Subject: Re: [ovirt-devel] [vdsm]

Re: [ovirt-devel] [vdsm] new internal stable modules + proposal

- Original Message - > From: "Nir Soffer" <nsof...@redhat.com> > To: "Francesco Romani" <from...@redhat.com> > Cc: "devel" <devel@ovirt.org> > Sent: Tuesday, March 29, 2016 6:00:56 PM > Subject: Re: [ovirt-devel] [vdsm] new in

Re: [ovirt-devel] [vdsm] new internal stable modules + proposal

On Tue, Mar 29, 2016 at 6:12 PM, Francesco Romani wrote: > Hi, > > 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 >

[ovirt-devel] [vdsm] new internal stable modules + proposal

Hi, 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 ->