Hi Dan, Thanks for your input. Parsing putput of ansible modules is indeed cumbersome. I think I will stick to parsing lsblk output On Wed, Nov 14, 2018 at 1:05 PM Dan Kenigsberg <danken@redhat.com> wrote:
On Wed, Nov 14, 2018 at 9:08 AM Kaustav Majumder <kmajumde@redhat.com> wrote:
Hi all, I have been working on making vdsm-gluster python 3 compatible. I had some queries regarding the tool used for getting storage devices
info. Till now vdsm uses python blivet for getting the device tree information.
python3-blivet supports only py3; python2-blivet1 supports only py2. You may re-implement vdsm.gluster.storagedev with python3-blivet if six.PY3 and keep the current code if six.PY2.
I am not sure if blivet is compatible with python 3 so I had two
propositions which I want some advice on.
1) Using lsblk and parsing the output
I'd do this if parsing lsblk is simpler than calling python3-blivet
2) Using ansible modules locally in the vdsm hosts.
Do you plan to parse their output? How are they implemented? This seems like to most cumbersome option.
Although I feel the 2nd way will add more dependencies to the project
but it can help us in the long run to add more functionality easily.
Thanks, Kaustav _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org 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/devel@ovirt.org/message/DJORSIZMTZ3HSA...
-- KAUSTAV MAJUMDER ASSOCIATE SOFTWARE ENGINEER Red Hat India PVT LTD. <https://www.redhat.com/> kmajumder@redhat.com M: 08981884037 IM: IRC: kmajumder <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatway <https://twitter.com/redhatway> @redhatinc <https://instagram.com/redhatinc> @redhatsnaps <https://snapchat.com/add/redhatsnaps>