On 16/06/2025 13:09, Thomas Goirand wrote:
On 6/14/25 05:07, Dmitriy Rabotyagov wrote:
On Sat, 14 Jun 2025, 01:24 , <thomas@goirand.fr <mailto:thomas@goirand.fr>> wrote:
Right. Plus I don't get why operators get to choose what class of bugs they may experience, and how they will know beter than contributors. Cheers,
Well, at least some class of bugs might be already known and operators might be willing to accept them, while the new ones could be not known by project maintainers and take quite some time to realize and patch.
So being able to rollback to old behavior might save the day.
This is FUD. IMO, either upstream OpenStack provides a working setup, either it's not.
sayint its FUD is not helpful. we got a driect ask form operator and soem core to not do a hard switch over. and while i wanted to only support one model for each binary at a time we were sepcificly ask to make it configurable.
In the later case, your only available action is help fixing bugs. It is not up to the operators to double-guess what may or may not work.
correct we are not planning to document how to change mode we were planning to only use this configuration in ci and operator would be told for a given release deploy this way. this is an internal impelation detail however we are not prepared to deprecate usign eventlet until we are convicned that we can run properly without it.
For beginners, this would be a horrible nightmare if default options simply wouldn't work. We *must* ship OpenStack working by default. no one is suggesting we do otherwise.
Cheers,
Thomas Goirand (zigo)