Jump to: navigation, search

Difference between revisions of "CinderXenaPTGSummary"

m (added topic outline)
m (add "Greetings and some Cinder project business")
Line 15: Line 15:
 
* https://www.youtube.com/watch?v=cL5y_erpaDc
 
* https://www.youtube.com/watch?v=cL5y_erpaDc
 
===Greetings and some Cinder project business===
 
===Greetings and some Cinder project business===
 +
Business in no particular order:
 +
 +
* The final release from stable/train for all deliverables is 12 May 2021, so check for any critical bugs that should be backported and get those moving along right away.
 +
* We need to do a release from the rbd-iscsi-client to verify that all the tooling is working.  Want to do this before any critical bug is discovered that will require a release.  The patch formatting rbd-iscsi-client as an OpenStack project still needs reviews: https://review.opendev.org/c/openstack/rbd-iscsi-client/+/774748/
 +
* There's a patch up placing cinder-specific dates on the OpenStack release schedule.  The only notable change from the usual dates is to move the spec freeze to 2 weeks after the R-18 midcycle.  (One week didn't give people enough time to revise and resubmit, which required a bunch of spec freeze exceptions.  Hopefully we can avoid that this time.)  Please check over the dates and leave comments if you see any problems: https://review.opendev.org/c/openstack/releases/+/786951
 +
* The two midcycles at weeks R-18 and R-9 have been working well, so let's do that again.  Format will be 2 hours.  I propose holding them in the place of the cinder weekly meeting that week; that way, everyone should be able to attend for at least the one hour they have set aside for the cinder meeting.  Time would probably be 1300-1500 UTC.  Please check for conflicts:
 +
** R-18 midcycle: 2 June
 +
** R-9 midcycle: 4 August
 +
* Some quick links to be aware of
 +
** general info on cinder project: '''tiny.cc/cinder-info'''
 +
** cinder group info: '''tiny.cc/cinder-groups'''
 +
* We've got someone interested in helping with documentation.  I've asked her to start by reviewing release notes on patches for clarity, grammar, etc.  These are user-facing documents so it's helpful to get them correct.
 +
* We didn't schedule time for a Wallaby Release Cycle Retrospective, so maybe we can do that during happy hour today.
  
 
===Not possible for a non-admin user to determine via API if a volume will be multi-attach===
 
===Not possible for a non-admin user to determine via API if a volume will be multi-attach===

Revision as of 11:27, 27 April 2021

Contents

Introduction

This page contains a summary of the subjects covered during the Cinder project sessions at the Project Team Gathering for the Xena development cycle, held virtually April 19-23, 2021. The Cinder project team met from Tuesday 20 April to Friday 23 April, for 3 hours each day (1300-1600 UTC), with Friday's sessions stretching to 4 hours.

The Cinder Team at the Xena (Virtual) PTG, April 2021.


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


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 20 April

recording

Greetings and some Cinder project business

Business in no particular order:

  • The final release from stable/train for all deliverables is 12 May 2021, so check for any critical bugs that should be backported and get those moving along right away.
  • We need to do a release from the rbd-iscsi-client to verify that all the tooling is working. Want to do this before any critical bug is discovered that will require a release. The patch formatting rbd-iscsi-client as an OpenStack project still needs reviews: https://review.opendev.org/c/openstack/rbd-iscsi-client/+/774748/
  • There's a patch up placing cinder-specific dates on the OpenStack release schedule. The only notable change from the usual dates is to move the spec freeze to 2 weeks after the R-18 midcycle. (One week didn't give people enough time to revise and resubmit, which required a bunch of spec freeze exceptions. Hopefully we can avoid that this time.) Please check over the dates and leave comments if you see any problems: https://review.opendev.org/c/openstack/releases/+/786951
  • The two midcycles at weeks R-18 and R-9 have been working well, so let's do that again. Format will be 2 hours. I propose holding them in the place of the cinder weekly meeting that week; that way, everyone should be able to attend for at least the one hour they have set aside for the cinder meeting. Time would probably be 1300-1500 UTC. Please check for conflicts:
    • R-18 midcycle: 2 June
    • R-9 midcycle: 4 August
  • Some quick links to be aware of
    • general info on cinder project: tiny.cc/cinder-info
    • cinder group info: tiny.cc/cinder-groups
  • We've got someone interested in helping with documentation. I've asked her to start by reviewing release notes on patches for clarity, grammar, etc. These are user-facing documents so it's helpful to get them correct.
  • We didn't schedule time for a Wallaby Release Cycle Retrospective, so maybe we can do that during happy hour today.

Not possible for a non-admin user to determine via API if a volume will be multi-attach

Conclusions

The Interoperability Working Group

Conclusions

Wallaby cycle retrospective

Conclusions

Wednesday 21 April

recordings

Removing the Block Storage API v2

Conclusions

mypy status and next steps

Conclusions

Quotas testing

Conclusions

Fix up volume driver classes

Conclusions

Cinder throttle and cgroup v2

Conclusions

Cross-project meeting with Nova

Conclusions

Thursday 22 April (Drivers' Day)

recordings

Using Software Factory for Cinder Third Party CI

Conclusions

NVMe-oF and MDRAID replication approach - next steps for connector and agent

Conclusions

How to handle retyping/migrating nonencrypted volumes to encrypted volumes of the same size

Conclusions

Small topics

What gate tests need to be done for A/A coverage of a driver?

Using cinder oslo-versioned-objects (OVOs) in tests instead of dicts

Friday 23 April

recordings

Market trends and new cinder features

Conclusions

Snapshotting attached volumes

Conclusions

Multiple volumes goes to a same backend/pool as scheduler intances (HA) use only its internal state to balance the volumes among pools

Conclusions

Making the backup process asynchronous

Conclusions

Several small topics

Volume list queried by error state should contain error_managing state

Support revert any snapshot to the volume

Update volume az after service restart when the volume backend az was changed

OpenStack client still doesn't support cinder microversions

Conclusions

Consistent and Secure RBAC

Conclusions