If you're interested in Cinder or Block Storage in general for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, on Wednesdays at 16:00 UTC. Please feel free to add items to the agenda below. NOTE: When adding topics please include your IRC name so we know who's topic it is and how to get more info.

+

If you're interested in Cinder or Block Storage in general for OpenStack, we have weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, on Wednesdays at 16:00 UTC. Please feel free to add items to the agenda in the etherpad link below. NOTE: When adding topics please include your IRC name so we know who's topic it is and how to get more info.

−

== Next meeting ==

+

Previous meeting logs can be found here: http://eavesdrop.openstack.org/meetings/cinder/

−

'''NOTE:''' ''Include your IRC nickname with your agenda items so that you can be called upon in the meeting and arrive at the meeting promptly if placing items in agenda. Please have any supporting links ready. You might want to put this on your calendar if you are adding items.''

** Currently it assumes the capacity of a new thinly provisioned volume will be consumed right away (the conservative approach).

−

** The proposed patch added a flag to allow user to decide whether to assume the new thinly provisioned lun will be consumed. If True, we deduct the capacity (existing behavior); If False, we don't deduct the capacity.

−

** There were many requests (after the patch was merged) not to deduct the capacity. So we need to take care of this.

−

** Any one is interested in preserving the existing behavior?

−

* Downgrades in new db migrations (DuncanT)

−

** Several new reviews seem to be missing them - intentional or not?

−

** Are we requiring make_compatible cinder-object methods for all migrations yet?

−

== Previous meetings ==

+

Agendas and notes from earlier meetings in the release can be seen further down in the etherpad.

−

'''May 13th, 2015 16:00 UTC'''

−

* Discuss date and location of Liberty mid-cycle meetup

+

'''NOTE:''' ''Include your IRC nickname with your agenda items so that you can be called upon in the meeting and arrive at the meeting promptly if placing items in agenda. Please have any supporting links ready. You might want to put this on your calendar if you are adding items.''

** There are 135 bugs with 'new' status and with 'undecided' importance

−

*** There isn't much consistency around how to determine importance of bugs even just looking at https://launchpad.net/cinder/+milestone/kilo-3 . How should people be categorizing these? Driver bugs especially are scattered randomly between Low and Critical.

−

** Should we announce Bugs Triage Day in openstack-dev?

−

−

'''March 11th, 2015 16:00 UTC'''

−

* Cinder supports several target objects now for the lvm driver. Where are those different targets getting CI'd ?

−

** '''Submitted by:''' Walt (hemna)

−

** Interested Parties<code>anish</code>

−

** when new targets get submitted, how can we ensure that they actually work. We need to think about integrating the different target objects with lvm for tempest tests

−

*** https://review.openstack.org/#/c/158829/

−

−

*Make public Volume Snapshots

−

** Create public snapshots.

−

** Modify snapshot permission (make it private or public) by owner only

−

** Other users can create volume with the public snapshot but can't reset the permission

−

** Interested Parties<code>Rakesh_Mishra</code> <code> Rushi </code>

−

*** BluePrint :https://review.openstack.org/#/c/125045/

−

****Patch : https://review.openstack.org/#/c/159372/

−

−

* FFE request for NFS backup

−

**'''Submitted by:''' Tom Barron (tbarron)

−

** Blueprint spec merged Jan. 19.

−

*** https://review.openstack.org/#/c/130858

−

** The review in question has two core +2s but awaited a dependent change.

−

*** https://review.openstack.org/#/c/149726 (the review in question)

−

*** https://review.openstack.org/#/c/149725 (the dependent review)

−

** Formal email request has been sent to the dev list, this is just a heads up and opportunity for Q&A.

** I attended this week's meeting and gave a high level status. They are looking for more participation.

−

* ProphetStor Cinder drivers (stevetan)

−

** Get feedback on progress of our DPL driver and documentation required https://review.openstack.org/#/c/95829/

−

** Get direction from community for our Federator SDS driver https://review.openstack.org/#/c/99616/

−

* Volume replication - work in progress (ronenkat)

−

** https://review.openstack.org/#/c/106718/2

−

* NFS Security, if there's time.

−

** https://blueprints.launchpad.net/cinder/+spec/secure-nfs

−

−

'''July 16th, 2014 16:00 UTC'''

−

* Putting the fun back into cinder development.

−

** There's been a mailing list thread recently about how nit-picky reviews are getting about typos, white space and the like, and how it is a motivation killer. I'm inclinded to agree - the formatting of the doc strings, fullstops at the end of comments etc doesn't actually improve the code much at all, and getting a -1 for it is a buzz kill of the highest order. Should we leave that sort of thing to the gate, and say that if there is no hacking check for it then it isn't important in general? (DuncanT)

−

−

* How to proceed with cinder/openstack requirements? python-dbus for https://review.openstack.org/99013, see mailing list conclusion http://lists.openstack.org/pipermail/openstack-dev/2014-July/040182.html (flip214)

** The GlusterFS snapshot code using qcow2 snapshots is useful for all file based storage systems. I would volunteer to move the GlusterFS snapshot code into the general RemoteFs driver - making it easier to get [https://review.openstack.org/#/c/94186/ our driver] accepted ;-)

−

** Eric Harney is fine with this and planned to do this for Juno anyway ([https://blueprints.launchpad.net/cinder/+spec/remotefs-snaps see his blueprint]). I've put it on the agenda to make sure others also agree with this approach.

Latest revision as of 15:24, 19 August 2019

Contents

Weekly Cinder team meeting

NOTE MEETING TIME: Wed's at 16:00 UTC

If you're interested in Cinder or Block Storage in general for OpenStack, we have weekly meetings in #openstack-meeting, on Wednesdays at 16:00 UTC. Please feel free to add items to the agenda in the etherpad link below. NOTE: When adding topics please include your IRC name so we know who's topic it is and how to get more info.

Next Cinder Team meeting

To add topics to our next weekly meeting follow the link to this release's etherpad below. There will be a section for the next team meeting at the end of the etherpad.

Agendas and notes from earlier meetings in the release can be seen further down in the etherpad.

NOTE:Include your IRC nickname with your agenda items so that you can be called upon in the meeting and arrive at the meeting promptly if placing items in agenda. Please have any supporting links ready. You might want to put this on your calendar if you are adding items.