On 4/25/24 11:51, Vladislav Odintsov wrote:
>
>
>> On 25 Apr 2024, at 12:20, Ilya Maximets <i.maxim...@ovn.org> wrote:
>>
>> On 4/25/24 10:53, Vladislav Odintsov wrote:
>>> Hi Ilya,
>>>
>>> I’ve got question regarding upgrade of clustered ovsdb-servers from 3.1 to
>>> 3.2+ version.
>>> ovsdb(7) states that the recommended path for upgrade is to upgrade
>>> ovsdb-servers one-by-one
>>> and that after upgrade ovsdb-server should be started with option
>>> --disable-file-no-data-conversion
>>> and after whole cluster is upgradede, it is needed to enable no-data
>>> conversion via appctl.
>>>
>>> I’ve ran through code and did some upgrade tests, so my question is:
>>> Do I understand correctly, that if there is no necessity to call schema
>>> conversion after start
>>> and before end of cluster upgrade, so it is allowed just to restart
>>> ovsdb-servers without
>>> --disable-file-no-data-conversion option and this will not have any
>>> downsides?
>>
>> Simply re-starting removing the option is enough. There is no need
>> to enable specifically via appctl in this case.
>
> I’m talking about a bit another thing:
> I want not to start each upgraded ovsdb-server with
> --disable-file-no-data-conversion at all,
> because it guaranteed in my case that there will be no schema conversions
> before full cluster
> upgrade is finished.
> So, in this case there will be no need to enable it back via appctl or
> removing ''disable"
> option and restart.
>
> Am I right, or I’m missing something?
Ah, sorry. If you're sure that there will be no conversion
before all the servers are upgraded, then it should be fine
to just upgrade as usual.
>
>>
>> Also, we did actually backport parts of the format change to 3.1.
>> It should be in v3.1.2 release and newer. So, technically, if you're
>> performing upgrade from v3.1.2+, it should be safe to just upgrade as
>> usual. ovsdb-servr v3.1.2 understands new database format, though it
>> can't produce it on its own. See the following commit on branch-3.1:
>>
>> 9529e9aa967c ("ovsdb: Allow conversion records with no data in a clustered
>> storage.")
>
> Hmm, nice. But mine source version is 3.0 and this is not applicable :)
The same change should be available in v3.0.5.
>
>>
>> It would be painful to document all the combinations of minor versions,
>> so it's not an officially supported upgrade path, but it is there if
>> you know what are you doing.
>
> Sure.
>
>>
>> Best regards, Ilya Maximets.
>
>
> Regards,
> Vladislav Odintsov
>
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
