Il giorno mer 3 apr 2019 alle ore 08:25 Sandro Bonazzola <
[email protected]> ha scritto:

> So, according to the thread we have a few action items:
> - Decide if we'll drop export domain and iso domain in 4.4
> - Move requirements from safelease to vdsm for numactl, dmidecode and
> virt-v2v if not already done
>

*Bug 1696313* <https://bugzilla.redhat.com/show_bug.cgi?id=1696313> - Drop
unneeded dependencies from safelease
*Bug 1696316* <https://bugzilla.redhat.com/show_bug.cgi?id=1696316> - Add
dependencies inherited from safelease to vdsm



> - Elect a maintainer for safelease for 4.3 scope
>

Any volunteer?


> - Deprecate safelease in 4.3 and remove it on master if we agree on
> removing iso and export domain in 4.4
>
> Il giorno mar 2 apr 2019 alle ore 18:14 Nir Soffer <[email protected]>
> ha scritto:
>
>> On Tue, Apr 2, 2019 at 6:40 PM Dan Kenigsberg <[email protected]> wrote:
>>
>>>
>>>
>>> On Tue, Apr 2, 2019 at 6:07 PM Nir Soffer <[email protected]> wrote:
>>>
>>>> On Tue, Apr 2, 2019 at 5:00 PM Sandro Bonazzola <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>> I stumbled upon safelease package, introduced in oVirt 3.6.
>>>>> I realigned the spec file with Fedora Rawhide:
>>>>> https://gerrit.ovirt.org/#/c/99123/
>>>>> and then I stopped working on it and decided to open a thread here.
>>>>>
>>>>> safelease package is required in vdsm.
>>>>> I searched for the home page for this package since it moved and
>>>>> found: https://ovirt.org/develop/developer-guide/vdsm/safelease.html
>>>>> This says that sanlock is meant to obsolete safelease.
>>>>> I'm assuming that safelease was used in 3.6 and replaced later by
>>>>> sanlock then kept for backward compatibility.
>>>>> In 4.3 we dropped support for 3.6 level clusters, is this package
>>>>> still needed?
>>>>>
>>>>
>>>> safelease is our clusterlock with V1 storage domains - export and iso
>>>> domains.
>>>>
>>>> https://github.com/oVirt/vdsm/blob/f433ed5aaf67729b787cf82ee21b0f17af968be4/lib/vdsm/storage/clusterlock.py#L127
>>>> https://github.com/oVirt/vdsm/blob/master/lib/vdsm/storage/sd.py#L320
>>>>
>>>> Once we remove these domains we can remove also safelease.
>>>>
>>>> If it's still needed, why is it requiring:
>>>>> # Numactl is not available on s390[x] and ARM
>>>>> %ifnarch s390 s390x %{arm}
>>>>> Requires: numactl
>>>>> %endif
>>>>>
>>>>> %ifarch x86_64
>>>>> Requires: python2-dmidecode
>>>>> Requires: dmidecode
>>>>> Requires: virt-v2v
>>>>> %endif
>>>>>
>>>>
>>>> These are hacks Yaniv added so we can make vdsm noarch package. Since
>>>> then we reverted
>>>> back to vdsm arch specific package but the bad requirements remained in
>>>> safelease.
>>>>
>>>> We can safely remove the requirements from safelease if vdsm requires
>>>> these packages, but
>>>> I'm not sure who has time to work on safelease.
>>>>
>>>> I think it is time to remove export and iso domain in 4.4.
>>>>
>>>
>>> Would it be possible?
>>> If an ovirt-4.3 storage pool has an ISO domain, and we add an ovirt-4.4
>>> host to it, we would like it to be able to become SPM.
>>>
>>
>> In rhel 8.1, vdsm 4.4, I don't want to support export or iso domain
>> regardless of the
>> cluster version.
>>
>> We don't have the time to port all code in vdsm to python 3. If you want
>> python 3, you need
>> to remove some features.
>>
>> If you want to mix 4.4. host with 4.3, env, detach the iso domain and
>> export domain?
>>
>> Tal, what do you think?
>>
>>>
>
> --
>
> SANDRO BONAZZOLA
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA <https://www.redhat.com/>
>
> [email protected]
> <https://red.ht/sig>
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA <https://www.redhat.com/>

[email protected]
<https://red.ht/sig>
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/3UCAOCZGJZBQEDJSYMCRDB6WPTFXRZBJ/

Reply via email to