Jump to: navigation, search

Difference between revisions of "Manila/Meetings"

(Next meeting)
(Next meeting)
Line 11: Line 11:
# Hierarchical port binding support (mkoderer)
# Hierarchical port binding support (mkoderer)
# Next meetup (mkoderer)
# Open Discussion
# Open Discussion

Revision as of 14:43, 11 February 2016

Weekly Manila team meeting

NOTE MEETING TIME: Thursday at 15:00 UTC

If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in #openstack-meeting-alt, on Thursdays at 15: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.

Next meeting

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

Scheduled for 11 Feb, 2016, 15:00 UTC

  1. Hierarchical port binding support (mkoderer)
  2. Next meetup (mkoderer)
  3. Open Discussion

Previous meetings

Scheduled for 4 Feb, 2016, 15:00 UTC

  1. Data service handling protocol mount commands (ganso)
  2. Separate process for copy on data service (tpsilva)
  3. ZFS driver (bswartz)
  4. First party drivers share migration support cooperation (ganso)

Scheduled for 28 Jan, 2016, 15:00 UTC

  1. Hierarchical port binding support (mkoderer)
  2. Core reviewer team and other manila-related projects (bswartz)
  3. Replication status (bswartz)

Scheduled for 21 Jan, 2016, 15:00 UTC

  1. Update_access backwards compatibility approach discussion. (ganso)
  2. Exposing the Data Service to drivers. (ganso)
  3. Snapshot manage/unmanage (bswartz)

Scheduled for 17 Dec, 2015, 15:00 UTC

  1. Proposal for share groups (cknight)
  2. Liberty.1 stable release (bswartz)

Scheduled for 10 Dec, 2015, 15:00 UTC

  1. The most of the driver already report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as Qos support flat? and write 'QoS_support' to capabilities_and_extra_specs.rst?(zhongjun)
    1. https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391
    2. https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354
    3. https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257
    4. https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111
    5. https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst
  2. Architectural concerns and interoperability of new features (cknight)

Scheduled for 3 Dec, 2015, 15:00 UTC

  1. Midcycle meetup
  2. Add "data loss" flag in DB migrations which lead to losing of existing data and update "manila-manage db sync" command to forbid applying such migrations without "--force" flag (u_glide)
  3. Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)
    1. https://review.openstack.org/#/c/252060/
    2. Mostly for awareness, this is now merged and should be backwards compatible.
    3. Cinder could benefit from a similar treatment. And with the incubator gone, we could explore a common library with the Cinder team, since the heretofore shared components are certain to diverge over time, but I'm not sure how receptive they would be. Xing?
  4. CI reliability
    1. Why should we merge patches for drivers whose CI systems consistently fail? This negates the value of CI. I think that accepting patches that aren't proven by CI does a disservice to everyone, most of all to the driver owners themselves. Refusing to merge driver patches without a good CI result for that driver seems like a gentler and more uniform-over-time approach than threatening to throw out a driver near the end of a release. And why make our illustrious and overworked PTL be the CI policeman when all core reviewers could simply glance at the corresponding CI result before giving +A? (cknight)
    2. http://ci-watch.tintri.com/project?project=manila
    3. https://review.openstack.org/#/c/232293/
    4. https://review.openstack.org/#/c/235522/
    5. https://review.openstack.org/#/c/235726/
    6. https://review.openstack.org/#/c/249999/
    7. https://review.openstack.org/#/c/237454/

Scheduled for 19 Nov, 2015, 15:00 UTC

  1. GB --> GiB (markstur)
  2. OpenStack Manuals and Devref (markstur)
    • Config Ref (and others) are moving to .RST!
    • How should we document prior releases in devref?
  3. Midcycle Meetup Date (bswartz)
  4. Deadlines for features (bswartz)
    • Feature proposal freeze vs Big Features
    • New drivers
  5. Data Copy Service network approach discussion (ganso)

Scheduled for 12 Nov, 2015, 15:00 UTC

  1. Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)
  2. Manila DR update (ameade)
    • Still no reviews on https://review.openstack.org/#/c/238572/
    • First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?
    • Replication_change share state - This is the state of the share when any of it's replicas are being promoted. Is 'replication_change' good or is there a better phrase?
  3. Manila Driver minimum requirements document update (ganso)
  4. Manila Data Copy service name (bswartz)
  5. Upcoming change for Manila CI hooks (vponomaryov)
  6. Manilaclient enhancement to provide request_id when set http_log_debug is True. It will co-ordinate the request and its id, so it will be helpful to filter the log and the failed request. (Jay Xu)

Scheduled for 5 Nov, 2015, 15:00 UTC

  1. Decide on read-only access rules as a required feature
  2. Manila DR - Design/Code feedback (gouthamr)

Scheduled for 1 Oct, 2015, 15:00 UTC

  1. Liberty RC2 status
  2. Mitaka Design Summit
  3. Vendor driver docs
  4. Manila Client Nova Style Microversion Support (cfouts)

Scheduled for 24 Sep, 2015, 15:00 UTC

  1. 3rd-party CI status
  2. Liberty RC status
  3. Support for QoS in Manila (zhongjun2)
  4. Reminder for backend driver maintainers to update feature support table (toabctl)
  5. Regression when using NetApp - license issue with netapp_lib (toabctl)
  6. Mitaka Design Summit
  7. Vendor driver docs
  8. Open Discussion