Open Stack

On Thu, Oct 6, 2022, at 9:24 AM, Rodolfo Alonso Hernandez wrote:
> I don't see in the documentation (probably I didn't check all of it) 
> that an OpenStack version upgrade doesn't imply other 
> library/modules/services upgrade. In this case, you will need to bump 
> the OVN/OVS version, keeping the same OVS/NB/SB information (probably 
> not the same database structures).
>

I don't know about documentation (but that may have come along with the new SLURP stuff), but Grenade enforces this sort of thing in CI. When we run Grenade against a branch we install the old version of OpenStack on the platform that the old version of OpenStack was tested on and then upgrade to the new current version of OpenStack. This upgrade is done on a host without upgrading the host itself.

> In any case, I'll try to make the Neutron server compatible with both 
> scenarios, but that will take some time to implement (if possible).
>
> On Thu, Oct 6, 2022 at 6:13 PM Jeremy Stanley <fungi at yuggoth.org> wrote:
>> On 2022-10-06 17:08:18 +0200 (+0200), Rodolfo Alonso Hernandez wrote:
>> [...]
>> > I've opened [3]. The default OVN version installed in the CI, using Ubuntu
>> > 20.04, is v20.03, that is a bit old. I've proposed to bump to v21.06,
>> > extensively tested in the Neutron CI. Any tempest job from any project is
>> > inherited from this one.
>> > 
>> > Once we have migrated to Ubuntu 22.04 during this cycle, we'll remove this
>> > forced OVN installation from source.
>> [...]
>> 
>> What's the implication for upgrades? Historically, we've needed the
>> software to be operable on the prior platform (upgrade OpenStack
>> from Zed to 2023.1/Antelope, then upgrade Ubuntu from Focal to
>> Jammy). Now with SLURP in the picture, we'll even need OpenStack
>> 2023.2/B working on Focal before upgrading to Jammy, right?
>> -- 
>> Jeremy Stanley