Hi Yaniv
We attempted to share the code a few years back, but I don't think it got
accepted.
In vdsm.conf we have two bridged interfaces, each connected to a SAN uplink:
[irs]
iscsi_default_ifaces = san1,san2
And here is a diff of the file
/usr/lib/python2.7/site-packages/vdsm/storage/ vs the o
On Fri, Feb 9, 2018 at 4:06 PM, Gary Lloyd wrote:
> Hi
>
> Is it possible/supported to upgrade from Ovirt 3.6 straight to Ovirt 4.2 ?
>
No, you go through 4.0, 4.1.
> Does live migration still function between the older vdsm nodes and vdsm
> nodes with software built against Ovirt 4.2 ?
>
Yes
Hello Gary,
as far as i know upgrade path isn't direct and you have to migrate
first to 4.0, then 4.1 and finally 4.2.
You can migrate vms from 3.6 to 4.0 IIRC. But don't know if mixing 4.2
and 3.6 it's possible.
Luca
On Fri, Feb 9, 2018 at 3:06 PM, Gary Lloyd wrote:
> Hi
>
> Is it possible/su
Hi
Is it possible/supported to upgrade from Ovirt 3.6 straight to Ovirt 4.2 ?
Does live migration still function between the older vdsm nodes and vdsm
nodes with software built against Ovirt 4.2 ?
We changed a couple of the vdsm python files to enable iscsi multipath on
direct luns.
(It's a fairl
4 matches
Mail list logo
