Hi,
thanks for your reply.
So for a stable 3.3. deployment vdsm-python-cpopen would suffice but when I want to upgrade to 3.4. I'll need python-cpopen anyway.
I guess you got some version/deprecation problems in rpm/yum to properly replace vdsm-p-c with p-c.
To be a little bit more precise:
I want to know, which option should I chose if I want to deploy a 3.3.2 stable today, with the ability to upgrade to 3.4 somewhere in time:
a) install python-cpopen b) install vdsm-python-cpopen
and which downside each option has regarding upgrades, and if the different bugs in the different upgradepaths will get resolved until 3.4 release.
I think this should lead, in the end, to a stable 3.4 with python-cpopen installed instead of vdsm-python-cpopen.
The question is, again, if you would advice to install python-cpopen or vdsm-python-cpopen on 3.3.2 when you take into account the different upgrade bugs and if they get resolved until 3.4 release, assuming that for the 3.3. installation there is no difference if you install python-cpopen or vdsm-python-cpopen.
Thank you.
Am 30.01.2014 10:20, schrieb Dan Kenigsberg:
python-cpopen includes some improvements and bug fixes, that are going to be needed in ovirt-3.4. vdsm-python-cpopen is shipped by ovirt-3.3.
python-cpopen wast intended to deprecate and replace vdsm-python-cpopen, but we have had way too many issues trying to do that properly in rpm/yum. Most of the bugs are ours, at least one is yum's.
At the moment, the existence of python-cpopen in Fedora confuses `yum install vdsm`.
To avoid this unfortunate delay, we can either include python-cpopen in ovirt-stable or exclude vdsm-python-cpopen from there. Both options are unfavorable, but so is continuing to wait.
Regards, Dan.