Jump to: navigation, search

Difference between revisions of "CinderWallabyPTGSummary"

m (added Friday 30 October headings)
m (updated Summit Follow-up: divisive language)
Line 17: Line 17:
 
===Summit Follow-up===
 
===Summit Follow-up===
 
====Divisive language in code/docs/infrastructure====
 
====Divisive language in code/docs/infrastructure====
 +
Basic idea (from [0]): "The OpenInfra Foundation (OIF) Board of Directors supports removal of wording identified as oppressive, racist and sexist by members of our communities from the software and documentation they produce. While we know there will be challenges, both technical and non-technical, this is an action we feel is important."
 +
 +
The working group driving this effort had a Forum session last week, and met at the PTG yesterday:
 +
* Forum discussion: https://etherpad.opendev.org/p/vSummit2020__DivisiveLanguage
 +
* PTG discussion: https://etherpad.opendev.org/p/wallaby-ptg-diversity
 +
 +
 +
Rosmaita reported on a quick grep of the cinder codebase for the obvious offensive usages of master/slave and blacklist/whitelist 
 +
* in the main cinder code, 'slave' shows up as a parameter to some oslo.db library calls, so we can't change this until they fix it
 +
* there is usage of master/slave in some of the drivers
 +
* also, blacklist/whitelist occurs in some drivers
 +
 +
 +
Amy Marrich (spotz), who's on the working group driving the effort, attended the session and emphasized some points to the team:
 +
* the working group is proposing "The Stance" to the TC.  When approved, it will give the individual project teams some guidance
 +
* we're not the only open source community doing this; there's a list on the etherpad of other open source projects and what changes they've made/are making
 +
* don't need to go back and change everything in our history, but projects should follow the guidance in new code/docs
 +
* projects can make the documentation more inclusive regardless of what happens in the code
 +
* the idea is to leave it to the projects to make appropriate changes; no plans to introduce churn by generated patches changing 'master' to something else for all projects
 +
* waiting to see what upstream git does about 'master' being the default trunk branch name.  Github has changed it to 'main' for new projects created on github
 +
 +
The current Cinder PTL is personally on board with this effort because it's being done in a thoughtful way and all changes will go through the normal code review process [1].  Additionally, some employers (for example, Red Hat [2]) are encouraging this effort in open source projects in which they are involved.
 +
 +
[0] https://etherpad.opendev.org/p/vSummit2020__DivisiveLanguage <br />
 +
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-October/018181.html <br />
 +
[2] https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language
 +
 +
=====Conclusions=====
 +
* My sense of the cinder PTG session was that the cinder team is generally supportive of the effort (or, at least not opposed to it).  What this means in practice is not allowing non-inclusive terms into new docs/code
 +
* Changes to existing code will be fought out in Gerrit as usual
 +
* '''ACTION''' - rosmaita - update the cinder code review guide to mention this once the TC proposal has been accepted
 +
 
====The openstackclient situation====
 
====The openstackclient situation====
 
====Community Goal for Wallaby====
 
====Community Goal for Wallaby====
 
===="consistent and secure policies" update====
 
===="consistent and secure policies" update====
 +
 
===Removal of nested quota drivers===
 
===Removal of nested quota drivers===
 
===Cleanup improvements ===
 
===Cleanup improvements ===

Revision as of 15:35, 2 November 2020

Contents

Introduction

This page contains a summary of the subjects covered during the Cinder project sessions at the Wallaby PTG, held virtually October 26-30, 2020. The Cinder project team met from Tuesday 27 October to Friday 30 October, for 3 hours (1300-1600 UTC) with an extra hour scheduled for "hallway time", though Wednesday and Thursday's hallway time was spent in cross-project meetings with the Glance team.

The Cinder Team at the Wallaby (Virtual) PTG, October 2020.


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 27 October

recordings

Summit Follow-up

Divisive language in code/docs/infrastructure

Basic idea (from [0]): "The OpenInfra Foundation (OIF) Board of Directors supports removal of wording identified as oppressive, racist and sexist by members of our communities from the software and documentation they produce. While we know there will be challenges, both technical and non-technical, this is an action we feel is important."

The working group driving this effort had a Forum session last week, and met at the PTG yesterday:


Rosmaita reported on a quick grep of the cinder codebase for the obvious offensive usages of master/slave and blacklist/whitelist

  • in the main cinder code, 'slave' shows up as a parameter to some oslo.db library calls, so we can't change this until they fix it
  • there is usage of master/slave in some of the drivers
  • also, blacklist/whitelist occurs in some drivers


Amy Marrich (spotz), who's on the working group driving the effort, attended the session and emphasized some points to the team:

  • the working group is proposing "The Stance" to the TC. When approved, it will give the individual project teams some guidance
  • we're not the only open source community doing this; there's a list on the etherpad of other open source projects and what changes they've made/are making
  • don't need to go back and change everything in our history, but projects should follow the guidance in new code/docs
  • projects can make the documentation more inclusive regardless of what happens in the code
  • the idea is to leave it to the projects to make appropriate changes; no plans to introduce churn by generated patches changing 'master' to something else for all projects
  • waiting to see what upstream git does about 'master' being the default trunk branch name. Github has changed it to 'main' for new projects created on github

The current Cinder PTL is personally on board with this effort because it's being done in a thoughtful way and all changes will go through the normal code review process [1]. Additionally, some employers (for example, Red Hat [2]) are encouraging this effort in open source projects in which they are involved.

[0] https://etherpad.opendev.org/p/vSummit2020__DivisiveLanguage
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-October/018181.html
[2] https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language

Conclusions
  • My sense of the cinder PTG session was that the cinder team is generally supportive of the effort (or, at least not opposed to it). What this means in practice is not allowing non-inclusive terms into new docs/code
  • Changes to existing code will be fought out in Gerrit as usual
  • ACTION - rosmaita - update the cinder code review guide to mention this once the TC proposal has been accepted

The openstackclient situation

Community Goal for Wallaby

"consistent and secure policies" update

Removal of nested quota drivers

Cleanup improvements

Quotas: "Remove quota usage cache"

Robustifying the volume driver interface

Vocabulary Minute

The team then adjourned to meetpad for Happy Hour.

Wednesday 28 October

recordings

Updates from TC Meeting

Kioxia: Add new driver

Update on Image Encryption Efforts

Sizing encrypted volumes (continued)

Cross-project meeting with Glance team

Thursday 29 October (Gorka's Day)

We declared this to be "Gorka's Day" because he contributed so many topics to be discussed.

recordings

Reset state robustification

Ceph: Minimum supported version

Ceph: Should we change rbd_exclusive_cinder_pool default?

Replication

Availability zone and volume type for backup restore

Cross-project meeting with Glance team

Friday 30 October

recordings

Cinder/PTG business

Removing deprecated encryptors from os-brick

Improvements to service down

new specs (and other stuff that has been sitting around)

"volume list query optimization"

Two proposed specs on the same topic (mutually assured destruction)

digression: deprecate thick-provisioned LVM?

Support revert any snapshot to the volume

Backend Capabilities

Replace md5 with oslo version

how to test the optimized glance-cinder image-volume workflow?

Team roles & business

current roles

proposed

tactical (short term)

Late Topics

attachments API - exposing connection info

keeping connection info up to date

cinder attach/detach service

autospeccing mocks