CinderZedPTGSummary

Introduction

The fifth virtual PTG for the Zed cycle of Cinder was conducted from Tuesday, 5th April, 2022 to Friday, 8th April, 2022, 4 hours each day (1300-1700 UTC). This page will provide a summary of all the topics discussed throughout the PTG.

File:Cinder-zed-ptg.png

This document aims to give a summary of each session. More context is available on the cinder Zed PTG etherpad:

• https://etherpad.opendev.org/p/zed-ptg-cinder

The sessions were recorded, so to get all the details of any discussion, you can watch/listen to the recording. Links to the recordings are located at appropriate places below.

Tuesday 05 April

recordings

• https://www.youtube.com/watch?v=OuSv_lu2PZc
• https://www.youtube.com/watch?v=6yuOlGckkGE

For the benefit of people who haven't attended, this is the way the cinder team works at the PTG:

• sessions are recorded
• please sign in on the "Attendees" section of this etherpad for each day
• all notes, questions, etc. happen in the etherpad; try to remember to preface your comment with your irc nick
• anyone present can comment or ask questions in the etherpad
• also, anyone present should feel free to ask questions or make comments during any of the discussions
• we discuss topics in the order listed in the etherpad, making adjustments as we go for sessions that run longer or shorter
• we stick to the scheduled times for cross-project sessions, but for everything else we are flexible

Release cadence discussion: tick-tock model

https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adjustment.html

There was a PTL-TC session about this on 4th April, 2022 (Monday) and the following points were discussed:

• This only affects the upgrade path and not the release model which remains same (i.e. 6 months)
• It proposes a tick-tock release model where if a release is tick, the subsequent release will be tock and so on
• This new effort provides the ability to upgrade from tick->tick release (skipping one release) but we cannot upgrade (directly) from tock-> tock release
• There is a job in place, grenade-skip-level, that will run on tick releases and check upgrade from tick-> tick release (or N-2 to N release)

There's a patch up by Gorka documenting the impact of the new release cadence on Cinder and it requires changes based on the discussion at PTG about the following points: Patch: https://review.opendev.org/c/openstack/cinder/+/830283

• removal of configuration option
• deprecating or removing a driver
• Python version support
• Backports (works the same way)
• New deprecation policy (deprecation policy in the project team guide: https://docs.openstack.org/project-team-guide/deprecation.html)

There will be a 2 cycle deprecation process which we can see with the following example, Suppose we have a config option "cinder_option_foo" deprecated in AA (tick), we need to continue the deprecation process in BB (tock), then we can remove that option in CC (tick + 1).

conclusions

1. action geguileo to update the patch with the current discussion points

Best review practices doc

whoami-rajat is working on putting together a review doc that would help new reviewers to efficiently review changes hence increasing the quality of review. link: https://review.opendev.org/c/openstack/cinder/+/834448 The discussion had a great point that should be mentioned in the review doc regarding a reviewer doesn't have to review everything but mentioning what they reviewed would benefit the other reviewers a lot. Eg: If someone reviewed the releasenote, it saves other reviewers time looking at the releasenote. Also there is a suggestion regarding adding the tick/tock release cadence specific review points.

conclusions

1. action whoami-rajat to update the review doc with the suggested points