[ovirt-devel] Trouble in switch type to OVS process

[Dan Kenigsberg]

On Tue, Jan 16, 2018 at 10:22 AM, Sandro Bonazzola <sbonazzo at redhat.com>
wrote:

> Adding some relevant people
>
> 2018-01-15 23:13 GMT+01:00 Dmitry Semenov <zend0 at ya.ru>:
>
>> Hi everyone!
>>
>>
>> I have installed oVirt ver 4.2 on three nodes with shared storage (FC)
>> and linux bridge setting:
>> - node01
>>
>> - node02 (self-hosted Engine host)
>>
>> - node03 (self-hosted Engine host)
>>
>>
>> I wanted to set cluster network switch type to OVS (for OVN)
>>
>> (followed this instruction
>> *https://ovirt.org/develop/release-management/features/network/provider-physical-network/*
>> <https://ovirt.org/develop/release-management/features/network/provider-physical-network/>
>> )
>>
>
Please note that OVN overlays work just fine with Linux Bridge switchtype.
You need to move to OVS only if you want OVN on non-overlays.


>>
>> After this step “*Set OVS networking on all vdsm hosts.* For each host,
>> enable Maintenance mode, Sync All Networks” - my node01 disappeared. I
>> don’t know what to do further.
>>
>
In "disappeared" do you mean it became non-responsive? Would you share with
us your supervdsm.log from the disappearing host?

For the rest 2 nodes (node02 and node03) i didn’t check this step.
>>
>>
>> Each node has bond (from 2 NIC), and each bond has configuration with 3
>> VLANS for: ovirtmgmt, migration, display.
>>
>>
>> How can I return node01 to cluster with OVS and switch other nodes to OVS?
>>
>> Best regards,
>>
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
>
> --
>
> SANDRO BONAZZOLA
>
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>
> Red Hat EMEA <https://www.redhat.com/>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20180116/9c5d43c0/attachment-0001.html>