2:23 p.m.
Hi all,
As some of you might recall, some time ago we made otopi default to
python3, and quickly reverted that, realizing this causes too much
breakage.
Now things should hopefully be more stable, and I now merged a patch
to default to python3 again.
Current status:
engine-setup works with python3 on fedora.
host-deploy works with python3 on fedora, with both engine being on
el7 and on fedora. Didn't try on el7, might work as well.
hosted-engine --deploy is most likely broken on fedora, but I think it
was already broken. We are working on that, but it will require some
more time - notably, having stuff from vdsm on python3 (if not fully
porting vdsm to python3, which I understand will take even more time).
If you want to use python2, you can do that with:
OTOPI_PYTHON=/bin/python hosted-engine --deploy
On el7, if you manually added python3 (which is not available in the
base repos), things will break - use above workaround if needed.
Best regards,
--
Didi
6:45 p.m.
On Thu, Nov 29, 2018, 13:25 Yedidyah Bar David <didi(a)redhat.com wrote:
Hi all,
As some of you might recall, some time ago we made otopi default to
python3, and quickly reverted that, realizing this causes too much
breakage.
Now things should hopefully be more stable, and I now merged a patch
to default to python3 again.
Current status:
engine-setup works with python3 on fedora.
host-deploy works with python3 on fedora, with both engine being on
el7 and on fedora. Didn't try on el7, might work as well.
I hope that "might work" good enough :-)
hosted-engine --deploy is most likely broken on fedora, but I think it
was already broken. We are working on that, but it will require some
more time - notably, having stuff from vdsm on python3
vdsm is not available on python 3, but this should not be a problem
since you should not import anything from vdsm.
You should use only the vdsmclient package to connect to vdsm and
use vdsm public APIs. But even this library is not available yet for
python 3.
(if not fully
porting vdsm to python3, which I understand will take even more
time).
And we need also sanlock, ioprocess, mom, and ovirt-imageio for python 3.
If you want to use python2, you can do that with:
OTOPI_PYTHON=/bin/python hosted-engine --deploy
Why not keep it using python 2 and provide option to use py3?
Nir
11:03 a.m.
On Thu, Nov 29, 2018 at 5:46 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
On Thu, Nov 29, 2018, 13:25 Yedidyah Bar David <didi(a)redhat.com wrote:
>
> Hi all,
>
> As some of you might recall, some time ago we made otopi default to
> python3, and quickly reverted that, realizing this causes too much
> breakage.
>
> Now things should hopefully be more stable, and I now merged a patch
> to default to python3 again.
>
>
> Current status:
>
> engine-setup works with python3 on fedora.
>
> host-deploy works with python3 on fedora, with both engine being on
> el7 and on fedora. Didn't try on el7, might work as well.
I hope that "might work" good enough :-)
If it's not, remove python3 from your el7 machine. I do not think we
need to support that. If there is a need, please open a bug, and state
exactly what's needed (e.g. epel, scl, self-built, etc.).
> hosted-engine --deploy is most likely broken on fedora, but I think it
> was already broken. We are working on that, but it will require some
> more time - notably, having stuff from vdsm on python3
vdsm is not available on python 3, but this should not be a problem
since you should not import anything from vdsm.
I know, but we do. Mostly in ovirt-hosted-engine-ha, which is used
also by ovirt-hosted-engine-setup. I guess we'll need to handle these
separately, and decided it's not a blocker.
You should use only the vdsmclient package to connect to vdsm and
use vdsm public APIs. But even this library is not available yet for
python 3.
Indeed.
> (if not fully
> porting vdsm to python3, which I understand will take even more time).
And we need also sanlock, ioprocess, mom, and ovirt-imageio for python 3.
Indeed.
Is this tracked somewhere?
>
> If you want to use python2, you can do that with:
>
> OTOPI_PYTHON=/bin/python hosted-engine --deploy
Why not keep it using python 2 and provide option to use py3?
We already provided the option for some years now :-), and I
do not think many people used it. Since we hope at some point
to drop python2 completely, and consider python3 support more
important now in the past, we decided now is a good time to
(re-)introduce it as default. Of course, we might revert if it
causes too much pain, but according to our tests it should be
reasonable now.
Thanks,
--
Didi
2181
days inactive
2184
days old
2 comments
2 participants
participants (2)
-
Nir Soffer -
Yedidyah Bar David