On 2/2/24 20:12, Mark Goddard wrote:
Hi,
The Kolla project is planning to support SLURP upgrades [1] in the Caracal release cycle, allowing users to upgrade from Antelope to Caracal. There are two areas in which I'd like to request information from the various project teams.
# 1. SLURP support
We understand that for various reasons there can be a gap between TC resolutions and implementation across projects. Using some rudimentary grepping through various codebases I found that many projects have added the grenade-skip-level job (or a variation of it) to their CI pipelines, and a few mention SLURP in their release notes. There's little mention of it in documentation at this stage.
AFAICT the following projects have SLURP upgrade jobs: Cinder, Glance, Ironic, Manila, Neutron, Nova, Octavia
While I could not find a SLURP job in these: Barbican, Bifrost, Blazar, Cloudkitty, Designate, Heat, Horizon, Keystone, Magnum, Placement
Question: Does your project explicitly support SLURP upgrades? Do you have or are you planning to add testing and documentation for SLURP upgrades?
For heat, we haven't made any incompatible db schema change or message queue changes so direct upgrade from 2023.1 to 2024.1 is supposed to work. I've proposed a change to add skip-level job and seems the job is now passing. I don't expect that any doc update may be needed specifically for SLURP. https://review.opendev.org/c/openstack/heat/+/907735 I'm not too sure if we have to mention explicitly about SLURP in individual projects. (AFAIK SLURP is not something a project can opt-in but should be a global policy, or do we have a mechanism to state that the project does/will not support SLURP ?) For the other projects as much as I know ... Skip level upgrade of keystone and placement are tested in CI of the other projects but probably adding the same skip level job to these two projects would make sense. https://review.opendev.org/c/openstack/keystone/+/907749 https://review.opendev.org/c/openstack/placement/+/907742 I also created a change to add skip-level jobs for designate. The jobs are passing now which is promising. https://review.opendev.org/c/openstack/designate/+/907741 It seems grenade job in brabican is currently broken (idk why it's kept non-voting now) so skip-level upgrade job is not passing either, so we may need someone from Barbican to look into these. https://review.opendev.org/c/openstack/barbican/+/907750 I'm not too sure how we may test upgrade scenario specific to horizon. Horizon itself has no local datastore and truly rely on the backend apis. One point I can think of is testing horizon N+2 and the other services N but I think we don't cover scenario of mixing versions. I'm not very familiar with the other projects (Blazar, Cloudkitty and Magnum) but they may also be able to try adding skip-level job following the existing approaches in a few projects like octavia[1] or what I proposed above. [1] https://github.com/openstack/octavia/blob/master/zuul.d/jobs.yaml#L91
# 2. Rolling SLURP upgrades
The TC resolution [1] states that rolling upgrades are optional for SLURP releases. This could affect the upgrade procedure required in Kolla Ansible. Nova mentions in its Antelope release notes that it supports rolling SLURP upgrades, but I could not find any information from other projects. It would be helpful if this was documented for each project.
Question: Does your project support or plan to support rolling upgrades? If changes to the upgrade procedure for SLURP are required, are they documented?
Thank you in advance for your responses. Apologies if I have missed any obvious source of information on this.
Regards, Mark
[1] https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adj... <https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adjustment.html>