Difference between revisions of "CinderCaracalMidCycleSummary"
(→recordings) |
(→recordings) |
||
Line 39: | Line 39: | ||
** Refactoring of an old driver | ** Refactoring of an old driver | ||
** #action: Review the patch | ** #action: Review the patch | ||
+ | |||
* NFS online extend | * NFS online extend | ||
** Blueprint: https://blueprints.launchpad.net/cinder/+spec/extend-volume-completion-action | ** Blueprint: https://blueprints.launchpad.net/cinder/+spec/extend-volume-completion-action | ||
Line 56: | Line 57: | ||
*** https://review.opendev.org/c/openstack/devstack-plugin-nfs/+/896196 | *** https://review.opendev.org/c/openstack/devstack-plugin-nfs/+/896196 | ||
**** Enable attached volume extend tests in devstack-plugin-nfs-tempest-full | **** Enable attached volume extend tests in devstack-plugin-nfs-tempest-full | ||
− | * | + | ** Slides to explain the current workflow and the changes going to be made by the feature |
+ | *** https://github.com/kgube/cinder-2024.1-midcycle-1/blob/main/nfs_online_resize.pdf | ||
+ | ** #action: review the patches (at least ones that are blocking nova side reviews) | ||
+ | |||
+ | * acceptable usage of `__init__()` in os-brick | ||
+ | ** Patch: https://review.opendev.org/c/openstack/os-brick/+/887576 | ||
+ | ** Eric's concern is that this code in __init__ shouldn't affect other brick connectors | ||
+ | *** by failing initialization of other connectors | ||
+ | *** by holding the initialization for too long (a heavy weight call to backend) | ||
+ | ** The above concerns shouldn't be an issue in this case | ||
+ | ** #action: document standards for working on os-brick connectors | ||
+ | |||
* CI Monitoring | * CI Monitoring | ||
+ | ** Etherpad: https://etherpad.opendev.org/p/cinder-caracal-ci-tracking | ||
+ | ** Lately we have been facing too many CI issues | ||
+ | ** There are also issues reported from Nova and Glace team for some cinder related failures | ||
+ | ** The actions to fix the CI have mostly been reactive so it would be better to monitor the CI proactively | ||
+ | ** Jon Bernard volunteered to actively monitor our CI and integrate it in weekly bug report status | ||
+ | ** cinder-tempest-plugin-cbak-s3 history has also been consistently failing | ||
+ | *** https://zuul.opendev.org/t/openstack/builds?job_name=cinder-tempest-plugin-cbak-s3 | ||
+ | ** swap space increase patch to make gate stable | ||
+ | *** https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/901672 | ||
+ | ** #action rosmaita - get info from infra team about the nodepool nodes and what kind of control we have over configuration from the zuul side | ||
+ | ** #action whoami-rajat: check the blocker for concurrency effort - talk to Luigi as he was working on it some time ago | ||
* Supporting AND operation on time comparison filters | * Supporting AND operation on time comparison filters | ||
* Several patches to the StorPool Cinder driver | * Several patches to the StorPool Cinder driver |
Revision as of 12:56, 27 December 2023
Introduction
Welcome to the Cinder 2024.1 (Caracal) midcycle summary page!
We conduct 2 midcycles between the OpenStack development cycle (6 months) that acts as a checkpoint for the following:
- Revisiting/following up the topics discussed at PTG
- Discuss topics that were missed during PTG due to author's unavailability or lack of time or any other reason
- Status of work items based on the milestone
There could be more reasons but the above highlighted are the major ones.
For 2024.2 (Caracal), the Midcycle will happen at:
- R-17: 6th December, 2023 (Wednesday) 1400-1600 UTC
- R-7: 14th February, 2023 (Wednesday) 1400-1600 UTC
Etherpad: https://etherpad.opendev.org/p/cinder-caracal-midcycles
Session One: R-17: 06 December 2024
recordings
- Recording for Midcycle 1 (YouTube): https://youtu.be/QSKWA1St97A
We held our first mid cycle of the 2024.1 (Caracal) development Cycle on 6th December (R-17 week) between 1400-1600 UTC.
- Retiring cinderlib
- Etherpad: https://etherpad.opendev.org/p/cinderlib-retirement
- Major consumers of Cinderlib are Ember-CSI and oVirt
- They are happy with old releases of cinderlib and don't require new development work into it
- We will not transition to 2024.1 (Caracal) development
- We will not accept any new patches in cinderlib
- We will support the last 3 stable releases i.e. 2023.2, 2023.1 and Zed (approximately 18 months)
- EM branches will transition to Unmantained (Victoria -> Yoga)
- #action: rosmaita to follow up on work associated with the deprecation
- Rework of JovianDSS Driver
- Patch: https://review.opendev.org/c/openstack/cinder/+/889284
- Refactoring of an old driver
- #action: Review the patch
- NFS online extend
- Blueprint: https://blueprints.launchpad.net/cinder/+spec/extend-volume-completion-action
- Patches in order of dependency
- https://review.opendev.org/c/openstack/cinder/+/873557
- Add the os-extend-volume-completion volume action
- https://review.opendev.org/c/openstack/python-cinderclient/+/873558
- Support the new volume action in python-cinderclient
- https://review.opendev.org/c/openstack/nova/+/873560
- Make Nova use the new volume action when handling "volume-extended" events
- https://review.opendev.org/c/openstack/cinder/+/891602]
- Make the new feature available for volume drivers
- https://review.opendev.org/c/openstack/cinder/+/873686
- Add support in the NFS driver
- https://review.opendev.org/c/openstack/cinder/+/873889
- Add support in the Netapp NFS driver
- https://review.opendev.org/c/openstack/devstack-plugin-nfs/+/896196
- Enable attached volume extend tests in devstack-plugin-nfs-tempest-full
- https://review.opendev.org/c/openstack/cinder/+/873557
- Slides to explain the current workflow and the changes going to be made by the feature
- #action: review the patches (at least ones that are blocking nova side reviews)
- acceptable usage of `__init__()` in os-brick
- Patch: https://review.opendev.org/c/openstack/os-brick/+/887576
- Eric's concern is that this code in __init__ shouldn't affect other brick connectors
- by failing initialization of other connectors
- by holding the initialization for too long (a heavy weight call to backend)
- The above concerns shouldn't be an issue in this case
- #action: document standards for working on os-brick connectors
- CI Monitoring
- Etherpad: https://etherpad.opendev.org/p/cinder-caracal-ci-tracking
- Lately we have been facing too many CI issues
- There are also issues reported from Nova and Glace team for some cinder related failures
- The actions to fix the CI have mostly been reactive so it would be better to monitor the CI proactively
- Jon Bernard volunteered to actively monitor our CI and integrate it in weekly bug report status
- cinder-tempest-plugin-cbak-s3 history has also been consistently failing
- swap space increase patch to make gate stable
- #action rosmaita - get info from infra team about the nodepool nodes and what kind of control we have over configuration from the zuul side
- #action whoami-rajat: check the blocker for concurrency effort - talk to Luigi as he was working on it some time ago
- Supporting AND operation on time comparison filters
- Several patches to the StorPool Cinder driver