Jump to: navigation, search

Difference between revisions of "CinderWallabyMidCycleSummary"

m (upcoming deadlines)
m (added headings)
Line 31: Line 31:
 
* rosmaita - look into what exactly is the function of lower-constraints; it was supposed to be a guideline for packagers, but we need to keep a balance between what's claimed and what's actually being tested
 
* rosmaita - look into what exactly is the function of lower-constraints; it was supposed to be a guideline for packagers, but we need to keep a balance between what's claimed and what's actually being tested
 
* driver maintainers - check the values in setup.cfg for dependencies used by your driver and make sure that the minimum isn't too low; also make sure the values in driver-requirements.txt are consistent with setup.cfg (setup.cfg is what's actually used; the driver-requirements.txt is a legacy convenience file for packagers)
 
* driver maintainers - check the values in setup.cfg for dependencies used by your driver and make sure that the minimum isn't too low; also make sure the values in driver-requirements.txt are consistent with setup.cfg (setup.cfg is what's actually used; the driver-requirements.txt is a legacy convenience file for packagers)
 +
 +
===Block Storage API v2 removal===
 +
 +
===consistent and secure policies===
 +
 +
===Windows RBD os-brick connector===
 +
 +
===review of proposed specs===

Revision as of 02:00, 10 December 2020

Introduction

At the Wallaby Virtual PTG we decided to hold two mid-cycle meetings, each two hours long. The first meeting would be before the Cinder Spec Freeze, and the second would be around the New Feature Status Checkpoint. So the mid-cycle meetings will be the week of R-18 and the week of R-9.

Session One: R-18: 9 December 2020

We met in BlueJeans from 1400 to 1600 UTC.
etherpad: https://etherpad.openstack.org/p/cinder-wallaby-mid-cycles
recording: https://www.youtube.com/watch?v=rKmlpBTIDGA

Cinder Project Updates

upcoming deadlines

  • 18 December - spec freeze
  • 21 January - Wallaby Milestone-2 and new driver merge deadline
  • 1 March - os-brick wallaby release
  • 8 March - python-cinderclient wallaby release

stable releases

Our current release cadence on the stable branches is (roughly) every two months. We've recently released:

  • os-brick: 4.1.0 (wallaby), 3.0.4 (ussuri)
  • cinder: 17.0.1 (victoria), 16.2.1 (ussuri), 15.4.1 (train)

We managed to slip a critical fix past the Train gate, but three or four other patches that had been approved and targeted for 15.4.1 are stuck in the gate. Once we get the Train gate sorted out, we'll most likely do an extra release from stable/train out of cadence.

end of year meetings

The last meeting of the year will be 23 December. Being also the last meeting of the month, it will be held in videoconference. We won't meet on 30 December.

requirements/lower-constraints update

The lower-constraints job was broken recently by a pip update that included a new dependencies resolver that is apparently more strict than the old one, and as a result, it was detecting incompatible constraints from cinder specifying a lower constraint for some libraries than its dependencies allowed as a minimum. We started to change the values in lower-constraints.txt one by one, and it became pretty obvious that a larger change was needed. So we merged this patch yesterday: https://review.opendev.org/c/openstack/cinder/+/766085

That patch raised the minimums in requirements.txt to the versions in a pip freeze of a recent py38 testenv and raised the values in lower-constraints.txt accordingly. This included some big jumps in major versions for some libraries, but it does bring our lower-constraints.txt much closer to reality. The lower-constraints job just uses the lower-constraints.txt as constraints and basically checks to make sure the requirements can be satisfied and runs unit tests. Since functional and tempest tests and the third party CIs are using versions of libraries much closer to the openstack upper-constraints, that left a big gap between what we were claiming as lower constraints and what was actually being tested.

actions
  • rosmaita - look into what exactly is the function of lower-constraints; it was supposed to be a guideline for packagers, but we need to keep a balance between what's claimed and what's actually being tested
  • driver maintainers - check the values in setup.cfg for dependencies used by your driver and make sure that the minimum isn't too low; also make sure the values in driver-requirements.txt are consistent with setup.cfg (setup.cfg is what's actually used; the driver-requirements.txt is a legacy convenience file for packagers)

Block Storage API v2 removal

consistent and secure policies

Windows RBD os-brick connector

review of proposed specs