https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Zhongjun2&feedformat=atomOpenStack - User contributions [en]2024-03-19T09:53:04ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=160782Manila/Meetings2018-04-12T11:35:16Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 12 April 2018, 15:00 UTC'''<br />
# priority for access rule spec review<br />
#* Do we require a limitation for value of the access rule priority (1~100).<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 5 April 2018, 15:00 UTC'''<br />
# Stable policy changes<br />
#* https://review.openstack.org/#/c/548916<br />
#* https://review.openstack.org/#/c/552733/<br />
# Failing jobs in gate<br />
#* https://review.openstack.org/#/c/557062/<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 29 Mar 2018, 15:00 UTC'''<br />
# Spec Reviews again<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Failing jobs in gate<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.org/p/manila-bug-triage-pad<br />
<br />
<br />
''Scheduled for 22 Mar 2018, 15:00 UTC'''<br />
# Summit<br />
#* Forum: https://etherpad.openstack.org/p/YVR-manila-brainstorming<br />
#* Project Update and Onboarding sessions<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
#* Spec review day like nova? http://lists.openstack.org/pipermail/openstack-dev/2018-March/128575.html<br />
# Fostering contribution to upstream manila<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 15 Mar 2018, 15:00 UTC'''<br />
# StoryBoard Progress Report (diablorojo)<br />
# How to update the content that's in the tempest scenario tests spec? (vkmc)<br />
#* https://github.com/openstack/manila-specs/blob/master/specs/ocata/scenario-tests.rst<br />
#* Make spec not tied to particular release?<br />
#* Use a different doc type?<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 15 Feb 2018, 15:00 UTC'''<br />
# PTG Planning<br />
<br />
<br />
'''Scheduled for 8 Feb 2018, 15:00 UTC'''<br />
# Rocky PTL<br />
# RC1<br />
#* https://launchpad.net/manila/+milestone/queens-rc1<br />
<br />
<br />
'''Scheduled for 1 Feb 2018, 15:00 UTC'''<br />
# Rocky PTL<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2018-January/126767.html<br />
<br />
<br />
'''Scheduled for 25 Jan 2018, 15:00 UTC'''<br />
# Feature Freeze / Queens milestone-3 (bswartz)<br />
<br />
<br />
'''Scheduled for 11 Jan 2018, 15:00 UTC'''<br />
# Let's go over new bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
'''Scheduled for 4 Jan 2018, 15:00 UTC'''<br />
# Generic driver attach problems (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Dec 2017, 15:00 UTC'''<br />
# How should we fix "shares cannot be found by name in admin context" (zhongjun)<br />
#* https://bugs.launchpad.net/manila/+bug/1721787<br />
#* https://review.openstack.org/#/c/522607/<br />
#* https://review.openstack.org/#/c/522452/<br />
# Outstanding driver work? (tbarron)<br />
#* infinidat https://review.openstack.org/#/c/515432/<br />
#* cephfs-nfs HA https://review.openstack.org/#/c/510547/<br />
# Tag M2? (tbarron)<br />
<br />
<br />
'''Scheduled for 30 Nov 2017, 15:00 UTC'''<br />
# Report from Wuhan Bug Smash<br />
## https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Queens-Wuhan-Bugs-List<br />
# Use v3 cinder client instead of v2 cinder client (zhongjun)<br />
## https://review.openstack.org/#/c/522478/<br />
<br />
<br />
'''Scheduled for 16 Nov 2017, 15:00 UTC'''<br />
# The Manila community was not very active. (junboli)<br />
## - patches cost long time to review and merge.<br />
## - less response for questions in IRC channel.<br />
## - more core members are required.<br />
# Bug smash in China (zhongjun)<br />
# IPv6 driver capabilities required variables (ganso)<br />
# 3rd Party CIs may have to change to use Manila Tempest Plugin repo (raissa)<br />
## https://review.openstack.org/#/c/512300/<br />
<br />
<br />
'''Scheduled for 26 Oct 2017, 15:00 UTC'''<br />
# Manila test image (bswartz)<br />
## https://review.openstack.org/#/q/status:open+project:openstack/manila-test-image<br />
<br />
<br />
'''Scheduled for 19 Oct 2017, 15:00 UTC'''<br />
# Spec freeze / milestone 1 (bswartz)<br />
# py2 -> py3 (vkmc)<br />
## https://bugs.launchpad.net/manila/+bug/1482633 && https://review.openstack.org/#/c/289382/<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Zuul V3 migration status (raissa)<br />
## https://review.openstack.org/#/c/512559/ https://review.openstack.org/#/c/513075/ https://review.openstack.org/#/c/513076/<br />
## https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details<br />
<br />
<br />
'''Scheduled for 12 Oct 2017, 15:00 UTC'''<br />
# Manila Driver Maintainers and the DriverLog (dustins)<br />
# Important Manila Bugs (dustins)<br />
<br />
<br />
'''Scheduled for 5 Oct, 2017, 15:00 UTC'''<br />
# Gate issues<br />
# drivers_private_storage hard-delete vs soft-delete (ganso)<br />
# Bug Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 28 Sep, 2017, 15:00 UTC'''<br />
# Discuss and elicit Feedback for PTG<br />
# Bug Tsar/Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
# Dynamic Log Level (zhongjun)<br />
# Install guide tesing (bswartz)<br />
# Automatic generation of docs for configuration options (bswartz)<br />
# Timeouts (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=160781Manila/Meetings2018-04-12T11:34:14Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 12 April 2018, 15:00 UTC'''<br />
# priority for access rule spec review<br />
## Do we require a limitation for value of the priority (1~100).<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 5 April 2018, 15:00 UTC'''<br />
# Stable policy changes<br />
#* https://review.openstack.org/#/c/548916<br />
#* https://review.openstack.org/#/c/552733/<br />
# Failing jobs in gate<br />
#* https://review.openstack.org/#/c/557062/<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 29 Mar 2018, 15:00 UTC'''<br />
# Spec Reviews again<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Failing jobs in gate<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.org/p/manila-bug-triage-pad<br />
<br />
<br />
''Scheduled for 22 Mar 2018, 15:00 UTC'''<br />
# Summit<br />
#* Forum: https://etherpad.openstack.org/p/YVR-manila-brainstorming<br />
#* Project Update and Onboarding sessions<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
#* Spec review day like nova? http://lists.openstack.org/pipermail/openstack-dev/2018-March/128575.html<br />
# Fostering contribution to upstream manila<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 15 Mar 2018, 15:00 UTC'''<br />
# StoryBoard Progress Report (diablorojo)<br />
# How to update the content that's in the tempest scenario tests spec? (vkmc)<br />
#* https://github.com/openstack/manila-specs/blob/master/specs/ocata/scenario-tests.rst<br />
#* Make spec not tied to particular release?<br />
#* Use a different doc type?<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 15 Feb 2018, 15:00 UTC'''<br />
# PTG Planning<br />
<br />
<br />
'''Scheduled for 8 Feb 2018, 15:00 UTC'''<br />
# Rocky PTL<br />
# RC1<br />
#* https://launchpad.net/manila/+milestone/queens-rc1<br />
<br />
<br />
'''Scheduled for 1 Feb 2018, 15:00 UTC'''<br />
# Rocky PTL<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2018-January/126767.html<br />
<br />
<br />
'''Scheduled for 25 Jan 2018, 15:00 UTC'''<br />
# Feature Freeze / Queens milestone-3 (bswartz)<br />
<br />
<br />
'''Scheduled for 11 Jan 2018, 15:00 UTC'''<br />
# Let's go over new bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
'''Scheduled for 4 Jan 2018, 15:00 UTC'''<br />
# Generic driver attach problems (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Dec 2017, 15:00 UTC'''<br />
# How should we fix "shares cannot be found by name in admin context" (zhongjun)<br />
#* https://bugs.launchpad.net/manila/+bug/1721787<br />
#* https://review.openstack.org/#/c/522607/<br />
#* https://review.openstack.org/#/c/522452/<br />
# Outstanding driver work? (tbarron)<br />
#* infinidat https://review.openstack.org/#/c/515432/<br />
#* cephfs-nfs HA https://review.openstack.org/#/c/510547/<br />
# Tag M2? (tbarron)<br />
<br />
<br />
'''Scheduled for 30 Nov 2017, 15:00 UTC'''<br />
# Report from Wuhan Bug Smash<br />
## https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Queens-Wuhan-Bugs-List<br />
# Use v3 cinder client instead of v2 cinder client (zhongjun)<br />
## https://review.openstack.org/#/c/522478/<br />
<br />
<br />
'''Scheduled for 16 Nov 2017, 15:00 UTC'''<br />
# The Manila community was not very active. (junboli)<br />
## - patches cost long time to review and merge.<br />
## - less response for questions in IRC channel.<br />
## - more core members are required.<br />
# Bug smash in China (zhongjun)<br />
# IPv6 driver capabilities required variables (ganso)<br />
# 3rd Party CIs may have to change to use Manila Tempest Plugin repo (raissa)<br />
## https://review.openstack.org/#/c/512300/<br />
<br />
<br />
'''Scheduled for 26 Oct 2017, 15:00 UTC'''<br />
# Manila test image (bswartz)<br />
## https://review.openstack.org/#/q/status:open+project:openstack/manila-test-image<br />
<br />
<br />
'''Scheduled for 19 Oct 2017, 15:00 UTC'''<br />
# Spec freeze / milestone 1 (bswartz)<br />
# py2 -> py3 (vkmc)<br />
## https://bugs.launchpad.net/manila/+bug/1482633 && https://review.openstack.org/#/c/289382/<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Zuul V3 migration status (raissa)<br />
## https://review.openstack.org/#/c/512559/ https://review.openstack.org/#/c/513075/ https://review.openstack.org/#/c/513076/<br />
## https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details<br />
<br />
<br />
'''Scheduled for 12 Oct 2017, 15:00 UTC'''<br />
# Manila Driver Maintainers and the DriverLog (dustins)<br />
# Important Manila Bugs (dustins)<br />
<br />
<br />
'''Scheduled for 5 Oct, 2017, 15:00 UTC'''<br />
# Gate issues<br />
# drivers_private_storage hard-delete vs soft-delete (ganso)<br />
# Bug Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 28 Sep, 2017, 15:00 UTC'''<br />
# Discuss and elicit Feedback for PTG<br />
# Bug Tsar/Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
# Dynamic Log Level (zhongjun)<br />
# Install guide tesing (bswartz)<br />
# Automatic generation of docs for configuration options (bswartz)<br />
# Timeouts (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=160776Manila/Meetings2018-04-12T03:22:03Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 12 April 2018, 15:00 UTC'''<br />
# priority for access rule spec review<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 5 April 2018, 15:00 UTC'''<br />
# Stable policy changes<br />
#* https://review.openstack.org/#/c/548916<br />
#* https://review.openstack.org/#/c/552733/<br />
# Failing jobs in gate<br />
#* https://review.openstack.org/#/c/557062/<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 29 Mar 2018, 15:00 UTC'''<br />
# Spec Reviews again<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Failing jobs in gate<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.org/p/manila-bug-triage-pad<br />
<br />
<br />
''Scheduled for 22 Mar 2018, 15:00 UTC'''<br />
# Summit<br />
#* Forum: https://etherpad.openstack.org/p/YVR-manila-brainstorming<br />
#* Project Update and Onboarding sessions<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
#* Spec review day like nova? http://lists.openstack.org/pipermail/openstack-dev/2018-March/128575.html<br />
# Fostering contribution to upstream manila<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 15 Mar 2018, 15:00 UTC'''<br />
# StoryBoard Progress Report (diablorojo)<br />
# How to update the content that's in the tempest scenario tests spec? (vkmc)<br />
#* https://github.com/openstack/manila-specs/blob/master/specs/ocata/scenario-tests.rst<br />
#* Make spec not tied to particular release?<br />
#* Use a different doc type?<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 15 Feb 2018, 15:00 UTC'''<br />
# PTG Planning<br />
<br />
<br />
'''Scheduled for 8 Feb 2018, 15:00 UTC'''<br />
# Rocky PTL<br />
# RC1<br />
#* https://launchpad.net/manila/+milestone/queens-rc1<br />
<br />
<br />
'''Scheduled for 1 Feb 2018, 15:00 UTC'''<br />
# Rocky PTL<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2018-January/126767.html<br />
<br />
<br />
'''Scheduled for 25 Jan 2018, 15:00 UTC'''<br />
# Feature Freeze / Queens milestone-3 (bswartz)<br />
<br />
<br />
'''Scheduled for 11 Jan 2018, 15:00 UTC'''<br />
# Let's go over new bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
'''Scheduled for 4 Jan 2018, 15:00 UTC'''<br />
# Generic driver attach problems (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Dec 2017, 15:00 UTC'''<br />
# How should we fix "shares cannot be found by name in admin context" (zhongjun)<br />
#* https://bugs.launchpad.net/manila/+bug/1721787<br />
#* https://review.openstack.org/#/c/522607/<br />
#* https://review.openstack.org/#/c/522452/<br />
# Outstanding driver work? (tbarron)<br />
#* infinidat https://review.openstack.org/#/c/515432/<br />
#* cephfs-nfs HA https://review.openstack.org/#/c/510547/<br />
# Tag M2? (tbarron)<br />
<br />
<br />
'''Scheduled for 30 Nov 2017, 15:00 UTC'''<br />
# Report from Wuhan Bug Smash<br />
## https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Queens-Wuhan-Bugs-List<br />
# Use v3 cinder client instead of v2 cinder client (zhongjun)<br />
## https://review.openstack.org/#/c/522478/<br />
<br />
<br />
'''Scheduled for 16 Nov 2017, 15:00 UTC'''<br />
# The Manila community was not very active. (junboli)<br />
## - patches cost long time to review and merge.<br />
## - less response for questions in IRC channel.<br />
## - more core members are required.<br />
# Bug smash in China (zhongjun)<br />
# IPv6 driver capabilities required variables (ganso)<br />
# 3rd Party CIs may have to change to use Manila Tempest Plugin repo (raissa)<br />
## https://review.openstack.org/#/c/512300/<br />
<br />
<br />
'''Scheduled for 26 Oct 2017, 15:00 UTC'''<br />
# Manila test image (bswartz)<br />
## https://review.openstack.org/#/q/status:open+project:openstack/manila-test-image<br />
<br />
<br />
'''Scheduled for 19 Oct 2017, 15:00 UTC'''<br />
# Spec freeze / milestone 1 (bswartz)<br />
# py2 -> py3 (vkmc)<br />
## https://bugs.launchpad.net/manila/+bug/1482633 && https://review.openstack.org/#/c/289382/<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Zuul V3 migration status (raissa)<br />
## https://review.openstack.org/#/c/512559/ https://review.openstack.org/#/c/513075/ https://review.openstack.org/#/c/513076/<br />
## https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details<br />
<br />
<br />
'''Scheduled for 12 Oct 2017, 15:00 UTC'''<br />
# Manila Driver Maintainers and the DriverLog (dustins)<br />
# Important Manila Bugs (dustins)<br />
<br />
<br />
'''Scheduled for 5 Oct, 2017, 15:00 UTC'''<br />
# Gate issues<br />
# drivers_private_storage hard-delete vs soft-delete (ganso)<br />
# Bug Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 28 Sep, 2017, 15:00 UTC'''<br />
# Discuss and elicit Feedback for PTG<br />
# Bug Tsar/Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
# Dynamic Log Level (zhongjun)<br />
# Install guide tesing (bswartz)<br />
# Automatic generation of docs for configuration options (bswartz)<br />
# Timeouts (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=160775Manila/Meetings2018-04-12T03:20:36Z<p>Zhongjun2: /* Previous meetings */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 5 April 2018, 15:00 UTC'''<br />
# Stable policy changes<br />
#* https://review.openstack.org/#/c/548916<br />
#* https://review.openstack.org/#/c/552733/<br />
# Failing jobs in gate<br />
#* https://review.openstack.org/#/c/557062/<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 5 April 2018, 15:00 UTC'''<br />
# Stable policy changes<br />
#* https://review.openstack.org/#/c/548916<br />
#* https://review.openstack.org/#/c/552733/<br />
# Failing jobs in gate<br />
#* https://review.openstack.org/#/c/557062/<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 29 Mar 2018, 15:00 UTC'''<br />
# Spec Reviews again<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
# Failing jobs in gate<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.org/p/manila-bug-triage-pad<br />
<br />
<br />
''Scheduled for 22 Mar 2018, 15:00 UTC'''<br />
# Summit<br />
#* Forum: https://etherpad.openstack.org/p/YVR-manila-brainstorming<br />
#* Project Update and Onboarding sessions<br />
# Spec Reviews<br />
#* https://etherpad.openstack.org/p/manila-rocky-specs<br />
#* Spec review day like nova? http://lists.openstack.org/pipermail/openstack-dev/2018-March/128575.html<br />
# Fostering contribution to upstream manila<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 15 Mar 2018, 15:00 UTC'''<br />
# StoryBoard Progress Report (diablorojo)<br />
# How to update the content that's in the tempest scenario tests spec? (vkmc)<br />
#* https://github.com/openstack/manila-specs/blob/master/specs/ocata/scenario-tests.rst<br />
#* Make spec not tied to particular release?<br />
#* Use a different doc type?<br />
# Let's Go Over New Bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 15 Feb 2018, 15:00 UTC'''<br />
# PTG Planning<br />
<br />
<br />
'''Scheduled for 8 Feb 2018, 15:00 UTC'''<br />
# Rocky PTL<br />
# RC1<br />
#* https://launchpad.net/manila/+milestone/queens-rc1<br />
<br />
<br />
'''Scheduled for 1 Feb 2018, 15:00 UTC'''<br />
# Rocky PTL<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2018-January/126767.html<br />
<br />
<br />
'''Scheduled for 25 Jan 2018, 15:00 UTC'''<br />
# Feature Freeze / Queens milestone-3 (bswartz)<br />
<br />
<br />
'''Scheduled for 11 Jan 2018, 15:00 UTC'''<br />
# Let's go over new bugs (dustins)<br />
#* https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
'''Scheduled for 4 Jan 2018, 15:00 UTC'''<br />
# Generic driver attach problems (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Dec 2017, 15:00 UTC'''<br />
# How should we fix "shares cannot be found by name in admin context" (zhongjun)<br />
#* https://bugs.launchpad.net/manila/+bug/1721787<br />
#* https://review.openstack.org/#/c/522607/<br />
#* https://review.openstack.org/#/c/522452/<br />
# Outstanding driver work? (tbarron)<br />
#* infinidat https://review.openstack.org/#/c/515432/<br />
#* cephfs-nfs HA https://review.openstack.org/#/c/510547/<br />
# Tag M2? (tbarron)<br />
<br />
<br />
'''Scheduled for 30 Nov 2017, 15:00 UTC'''<br />
# Report from Wuhan Bug Smash<br />
## https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Queens-Wuhan-Bugs-List<br />
# Use v3 cinder client instead of v2 cinder client (zhongjun)<br />
## https://review.openstack.org/#/c/522478/<br />
<br />
<br />
'''Scheduled for 16 Nov 2017, 15:00 UTC'''<br />
# The Manila community was not very active. (junboli)<br />
## - patches cost long time to review and merge.<br />
## - less response for questions in IRC channel.<br />
## - more core members are required.<br />
# Bug smash in China (zhongjun)<br />
# IPv6 driver capabilities required variables (ganso)<br />
# 3rd Party CIs may have to change to use Manila Tempest Plugin repo (raissa)<br />
## https://review.openstack.org/#/c/512300/<br />
<br />
<br />
'''Scheduled for 26 Oct 2017, 15:00 UTC'''<br />
# Manila test image (bswartz)<br />
## https://review.openstack.org/#/q/status:open+project:openstack/manila-test-image<br />
<br />
<br />
'''Scheduled for 19 Oct 2017, 15:00 UTC'''<br />
# Spec freeze / milestone 1 (bswartz)<br />
# py2 -> py3 (vkmc)<br />
## https://bugs.launchpad.net/manila/+bug/1482633 && https://review.openstack.org/#/c/289382/<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Zuul V3 migration status (raissa)<br />
## https://review.openstack.org/#/c/512559/ https://review.openstack.org/#/c/513075/ https://review.openstack.org/#/c/513076/<br />
## https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details<br />
<br />
<br />
'''Scheduled for 12 Oct 2017, 15:00 UTC'''<br />
# Manila Driver Maintainers and the DriverLog (dustins)<br />
# Important Manila Bugs (dustins)<br />
<br />
<br />
'''Scheduled for 5 Oct, 2017, 15:00 UTC'''<br />
# Gate issues<br />
# drivers_private_storage hard-delete vs soft-delete (ganso)<br />
# Bug Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 28 Sep, 2017, 15:00 UTC'''<br />
# Discuss and elicit Feedback for PTG<br />
# Bug Tsar/Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
# Dynamic Log Level (zhongjun)<br />
# Install guide tesing (bswartz)<br />
# Automatic generation of docs for configuration options (bswartz)<br />
# Timeouts (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=158423Manila/Meetings2017-12-06T06:36:34Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 7 Dec 2017, 15:00 UTC'''<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# How should we fix "shares cannot be found by name in admin context" (zhongjun)<br />
## https://bugs.launchpad.net/manila/+bug/1721787<br />
## https://review.openstack.org/#/c/522607/<br />
## https://review.openstack.org/#/c/522452/<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 30 Nov 2017, 15:00 UTC'''<br />
# Report from Wuhan Bug Smash<br />
## https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Queens-Wuhan-Bugs-List<br />
# Use v3 cinder client instead of v2 cinder client (zhongjun)<br />
## https://review.openstack.org/#/c/522478/<br />
<br />
<br />
'''Scheduled for 16 Nov 2017, 15:00 UTC'''<br />
# The Manila community was not very active. (junboli)<br />
## - patches cost long time to review and merge.<br />
## - less response for questions in IRC channel.<br />
## - more core members are required.<br />
# Bug smash in China (zhongjun)<br />
# IPv6 driver capabilities required variables (ganso)<br />
# 3rd Party CIs may have to change to use Manila Tempest Plugin repo (raissa)<br />
## https://review.openstack.org/#/c/512300/<br />
<br />
<br />
'''Scheduled for 26 Oct 2017, 15:00 UTC'''<br />
# Manila test image (bswartz)<br />
## https://review.openstack.org/#/q/status:open+project:openstack/manila-test-image<br />
<br />
<br />
'''Scheduled for 19 Oct 2017, 15:00 UTC'''<br />
# Spec freeze / milestone 1 (bswartz)<br />
# py2 -> py3 (vkmc)<br />
## https://bugs.launchpad.net/manila/+bug/1482633 && https://review.openstack.org/#/c/289382/<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Zuul V3 migration status (raissa)<br />
## https://review.openstack.org/#/c/512559/ https://review.openstack.org/#/c/513075/ https://review.openstack.org/#/c/513076/<br />
## https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details<br />
<br />
<br />
'''Scheduled for 12 Oct 2017, 15:00 UTC'''<br />
# Manila Driver Maintainers and the DriverLog (dustins)<br />
# Important Manila Bugs (dustins)<br />
<br />
<br />
'''Scheduled for 5 Oct, 2017, 15:00 UTC'''<br />
# Gate issues<br />
# drivers_private_storage hard-delete vs soft-delete (ganso)<br />
# Bug Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 28 Sep, 2017, 15:00 UTC'''<br />
# Discuss and elicit Feedback for PTG<br />
# Bug Tsar/Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
# Dynamic Log Level (zhongjun)<br />
# Install guide tesing (bswartz)<br />
# Automatic generation of docs for configuration options (bswartz)<br />
# Timeouts (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=ThirdPartySystems/INFINIDAT_CI&diff=158361ThirdPartySystems/INFINIDAT CI2017-12-04T06:40:16Z<p>Zhongjun2: Created page with "{{ThirdPartySystemInfo|name=INFINIDAT CI |account=infinidat-openstack |contact=support@infinidat.com, IRC: amito, wiggin15 |intent=Continuous Integration for the INFINIDAT Cin..."</p>
<hr />
<div>{{ThirdPartySystemInfo|name=INFINIDAT CI<br />
|account=infinidat-openstack<br />
|contact=support@infinidat.com, IRC: amito, wiggin15<br />
|intent=Continuous Integration for the INFINIDAT Cinder Volume Driver and the INFINIDAT Manila Share Driver<br />
|structure=Zuul and Jenkins (installed with ansible), modified with local configuration<br />
|method=Using Zuul to connect to Gerrit<br />
|programs=Cinder, Manila<br />
|status=non-voting}}<br />
<br />
'''Recheck trigger''': "infinidat-openstack: recheck"</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=ThirdPartySystems&diff=158360ThirdPartySystems2017-12-04T06:38:44Z<p>Zhongjun2: /* Third Party CI Systems */</p>
<hr />
<div>== Third Party CI Systems ==<br />
<br />
{| border="1" cellpadding="2" cellspacing="0" class="wikitable"<br />
|+<br />
!colspan="3"|3rd Party CI Systems<br />
|-<br />
!Name<br />
!Link<br />
!Comments<br />
|-<br />
{{ThirdPartySystemTableEntry|6WIND Networking CI}}|<br />
{{ThirdPartySystemTableEntry|A10 Networks CI |}}|<br />
{{ThirdPartySystemTableEntry|Arista-CI}}|<br />
{{ThirdPartySystemTableEntryDown|Blockbridge EPS CI}}|<br />
{{ThirdPartySystemTableEntryDown|Brocade OpenStack CI}}|<br />
{{ThirdPartySystemTableEntry|Big Switch CI}}|<br />
{{ThirdPartySystemTableEntry|Canonical Charm CI}}|<br />
{{ThirdPartySystemTableEntry|Cisco Ironic CI}}|<br />
{{ThirdPartySystemTableEntry|Cisco ml2 CI}}|<br />
{{ThirdPartySystemTableEntry|Cisco N1kV CI}}|<br />
{{ThirdPartySystemTableEntry|Cisco UCSm CI}}|<br />
{{ThirdPartySystemTableEntry|cisco_pnr_ci}}|<br />
{{ThirdPartySystemTableEntry|Cisco Tail-f CI}}|<br />
{{ThirdPartySystemTableEntry|Cisco ZM CI}}|<br />
{{ThirdPartySystemTableEntry|Citrix NetScaler CI}}|<br />
{{ThirdPartySystemTableEntry|cloudbau Chef CI}}|<br />
{{ThirdPartySystemTableEntry|Cloudbase Cinder SMB3 CI}}|<br />
{{ThirdPartySystemTableEntryDown|Cloudbase Compute Hyper-V CI}}|<br />
{{ThirdPartySystemTableEntryDown|Cloudbase Manila SMB3 CI}}|<br />
{{ThirdPartySystemTableEntryDown|Cloudbase Neutron Hyper-V CI}}|<br />
{{ThirdPartySystemTableEntry|Cloudbase Nova Hyper-V CI}}|<br />
{{ThirdPartySystemTableEntry|CloudByte CI}}|<br />
{{ThirdPartySystemTableEntryDown|CloudFounders OpenvStorage CI}}|<br />
{{ThirdPartySystemTableEntry|Coho Data CI}}|<br />
{{ThirdPartySystemTableEntry|Coraid CI}}|<br />
{{ThirdPartySystemTableEntry|DataCore CI}}|<br />
{{ThirdPartySystemTableEntry|datera-ci}}|<br />
{{ThirdPartySystemTableEntry|DB Datasets CI}}|<br />
{{ThirdPartySystemTableEntryDown|Designate CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC Ironic CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC PS Series CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC SC Series CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC VMAX CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC VNX CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC XtremIO CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC ScaleIO CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC CoprHD CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC Unity CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC Unity Manila CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC VMAX Manila CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC VNX Manila CI}}|<br />
{{ThirdPartySystemTableEntry|Dell EMC Isilon CI}}|<br />
{{ThirdPartySystemTableEntry|FalconStor CI}}|<br />
{{ThirdPartySystemTableEntry|Freescale CI}}|<br />
{{ThirdPartySystemTableEntry|Fuel CI}}|<br />
{{ThirdPartySystemTableEntry|Fuel Packaging CI}}|<br />
{{ThirdPartySystemTableEntry|Fujitsu C-Fabric CI}}|<br />
{{ThirdPartySystemTableEntry|Fujitsu ETERNUS CI}}|<br />
{{ThirdPartySystemTableEntry|Fujitsu iRMC CI}}|<br />
{{ThirdPartySystemTableEntry|Fujitsu ISM CI}}|<br />
{{ThirdPartySystemTableEntry|Hedvig CI}}|<br />
{{ThirdPartySystemTableEntry|HGST Solutions CI}}|<br />
{{ThirdPartySystemTableEntry|Hitachi HBSD CI}}|<br />
{{ThirdPartySystemTableEntry|Hitachi HBSD2 CI}}|<br />
{{ThirdPartySystemTableEntry|Hitachi HNAS CI}}|<br />
{{ThirdPartySystemTableEntry|Hitachi Manila HNAS CI}}|<br />
{{ThirdPartySystemTableEntry|Hitachi Manila HSP CI}}|<br />
{{ThirdPartySystemTableEntry|Vedams-HPMSA FCISCSIDriver CI}}|<br />
{{ThirdPartySystemTableEntry|HP Octavia Sonar CI}}|<br />
{{ThirdPartySystemTableEntry|HPE Storage CI}}|<br />
{{ThirdPartySystemTableEntry|HP Networking CI}}|<br />
{{ThirdPartySystemTableEntry|HPE Proliant iLO drivers CI}}|<br />
{{ThirdPartySystemTableEntry|Huawei FusionCompute CI}}|<br />
{{ThirdPartySystemTableEntry|Huawei FusionStorage CI}}|<br />
{{ThirdPartySystemTableEntry|Huawei Manila CI}}|<br />
{{ThirdPartySystemTableEntry|Huawei ML2 CI}}|<br />
{{ThirdPartySystemTableEntry|Huawei volume CI}}|<br />
{{ThirdPartySystemTableEntry|IBMPowerKVMCI}}|<br />
{{ThirdPartySystemTableEntryDown|IBM FlashSystem CI}}| See [[ThirdPartySystems/IBM Storage CI|IBM Storage CI]]<br />
{{ThirdPartySystemTableEntry|IBM GPFS CI}}|<br />
{{ThirdPartySystemTableEntry|IBM GPFS REMOTE CI}}|<br />
{{ThirdPartySystemTableEntry|IBM GPFS NFS CI}}|<br />
{{ThirdPartySystemTableEntry|IBM PowerVM CI}}|<br />
{{ThirdPartySystemTableEntry|IBM NAS CI}}|<br />
{{ThirdPartySystemTableEntry|IBM SDN-VE CI}}|<br />
{{ThirdPartySystemTableEntry|IBM Storage CI}}|<br />
{{ThirdPartySystemTableEntryDown|IBM STORWIZE CI}}| See [[ThirdPartySystems/IBM Storage CI|IBM Storage CI]]<br />
{{ThirdPartySystemTableEntryDown|IBM XIV-DS8K CI}}| See [[ThirdPartySystems/IBM Storage CI|IBM Storage CI]]<br />
{{ThirdPartySystemTableEntry|IBM xCAT CI}}|<br />
{{ThirdPartySystemTableEntryDown|IBM zKVM CI}}|<br />
{{ThirdPartySystemTableEntryDown|IBM z/VM CI}}|<br />
{{ThirdPartySystemTableEntry|Inspur CI}}|<br />
{{ThirdPartySystemTableEntry|Intel NFV CI}}|<br />
{{ThirdPartySystemTableEntryDown|Intel_NGFW_CI}}|<br />
{{ThirdPartySystemTableEntryDown|Intel-PCI-CI}}|<br />
{{ThirdPartySystemTableEntryDown|Intel-SRIOV-CI}}|<br />
{{ThirdPartySystemTableEntryDown|Intel-IPMI-CI}}|<br />
{{ThirdPartySystemTableEntry|INFINIDAT CI}}|<br />
{{ThirdPartySystemTableEntry|Infortrend Storage CI}}|<br />
{{ThirdPartySystemTableEntryDown|ITRI DISCO CI}}|<br />
{{ThirdPartySystemTableEntryDown|ITRI Peregrine CI}}|<br />
{{ThirdPartySystemTableEntry|Kaminario K2 CI}}|<br />
{{ThirdPartySystemTableEntry|KEMPtechnologies CI}}|<br />
{{ThirdPartySystemTableEntryDown|Linaro CI}}|<br />
{{ThirdPartySystemTableEntry|Lenovo Storage CI}}|<br />
{{ThirdPartySystemTableEntry|Limestone Networks CI}}|<br />
{{ThirdPartySystemTableEntry|Maxta CI}}|<br />
{{ThirdPartySystemTableEntry|Mellanox CI}}|<br />
{{ThirdPartySystemTableEntry|Metaplugin CI}}|<br />
{{ThirdPartySystemTableEntryDown|Midokura CI}}|<br />
{{ThirdPartySystemTableEntry|MapR-FS Manila CI}}|<br />
{{ThirdPartySystemTableEntry|Mirantis Rally CI}}|<br />
{{ThirdPartySystemTableEntry|murano-ci}}|<br />
{{ThirdPartySystemTableEntryDown|NEC CI}}|<br />
{{ThirdPartySystemTableEntry|NEC Cinder CI}}|<br />
{{ThirdPartySystemTableEntry|NetApp CI}}|<br />
{{ThirdPartySystemTableEntry|NetApp Eseries CI}}|<br />
{{ThirdPartySystemTableEntry|NetApp SolidFire CI}}|<br />
{{ThirdPartySystemTableEntry|Nexenta CI}}|<br />
{{ThirdPartySystemTableEntry|Nexenta Edge CI}}|<br />
{{ThirdPartySystemTableEntry|Nexenta Manila CI}}|<br />
{{ThirdPartySystemTableEntry|Nimble Storage CI}}|<br />
{{ThirdPartySystemTableEntry|NTT SystemFault MasakariIntegration CI}}|<br />
{{ThirdPartySystemTableEntry|Nuage CI}}|<br />
{{ThirdPartySystemTableEntryDown|OpenDaylight CI}}|<br />
{{ThirdPartySystemTableEntry|Open-E JovianDSS CI}}|<br />
{{ThirdPartySystemTableEntryDown|OPNFV CI}}|<br />
{{ThirdPartySystemTableEntry|Oracle ZFSSA CI}}|<br />
{{ThirdPartySystemTableEntryDown|PLUMgrid CI}}|<br />
{{ThirdPartySystemTableEntry|ProphetStor CI}}|<br />
{{ThirdPartySystemTableEntry|PhazrIO CI}}|<br />
{{ThirdPartySystemTableEntry|Pure Storage CI}}|<br />
{{ThirdPartySystemTableEntry|QNAP CI}}|<br />
{{ThirdPartySystemTableEntry|Quobyte CI}}|<br />
{{ThirdPartySystemTableEntry|Rackspace CloudDNS CI}}|<br />
{{ThirdPartySystemTableEntry|Rackspace GolangSwift CI}}|<br />
{{ThirdPartySystemTableEntry|Radware CI}}|<br />
{{ThirdPartySystemTableEntry|RDO Third Party CI}}|<br />
{{ThirdPartySystemTableEntry|RedHat CI}}|<br />
{{ThirdPartySystemTableEntry|RedHat GlusterFS CI}}|<br />
{{ThirdPartySystemTableEntryDown|RedHat̞ NFVPE CI}}|<br />
{{ThirdPartySystemTableEntry|RedHat RDO CI}}|<br />
{{ThirdPartySystemTableEntry|Reduxio HX550 CI}}|<br />
{{ThirdPartySystemTableEntry|Scality CI}}|<br />
{{ThirdPartySystemTableEntry|Snabb-NFV CI}}|<br />
{{ThirdPartySystemTableEntry|Software Factory CI}}|ZuulV3|<br />
{{ThirdPartySystemTableEntry|SolidFire CI}}|<br />
{{ThirdPartySystemTableEntry|StorPool CI}}|<br />
{{ThirdPartySystemTableEntry|SUSE Cloud CI}}|<br />
{{ThirdPartySystemTableEntry|SwiftStack Cluster CI}}|<br />
{{ThirdPartySystemTableEntry|Synology DSM CI}}|<br />
{{ThirdPartySystemTableEntry|Tail-f NCS CI}}|<br />
{{ThirdPartySystemTableEntry|Tegile Storage CI}}|<br />
{{ThirdPartySystemTableEntry|Tintri CI}}|<br />
{{ThirdPartySystemTableEntry|UFCG OneView CI}}|<br />
{{ThirdPartySystemTableEntry|Vanilla Stack CI}}|<br />
{{ThirdPartySystemTableEntry|vArmour CI}}|<br />
{{ThirdPartySystemTableEntry|Vedams SCST CI}}|<br />
{{ThirdPartySystemTableEntry|Veritas HyperScale CI}}|<br />
{{ThirdPartySystemTableEntry|Veritas Access CI}}|<br />
{{ThirdPartySystemTableEntry|Violin Memory CI}}|<br />
{{ThirdPartySystemTableEntry|Virtuozzo CI}}|<br />
{{ThirdPartySystemTableEntryDown|Virtuozzo Storage CI}}|<br />
{{ThirdPartySystemTableEntry|VMware CI}}|<br />
{{ThirdPartySystemTableEntry|Wherenow.org CI}}|<br />
{{ThirdPartySystemTableEntry|XenProject CI}}|<br />
{{ThirdPartySystemTableEntry|XenServer CI}}|<br />
{{ThirdPartySystemTableEntry|X-IO technologies CI}}|<br />
{{ThirdPartySystemTableEntryDown|XP Storage CI}}|<br />
{{ThirdPartySystemTableEntry|ZadaraStorage VPSA CI}}|<br />
{{ThirdPartySystemTableEntry|ZTE cinder2 CI}}|<br />
{{ThirdPartySystemTableEntryDown|Example}}|<br />
|-<br />
|}<br />
<br />
<br />
Instructions on how to add a new system to the above table:<br />
* Add an '''alphabetical''' entry in the above table: <code><nowiki>{{ThirdPartySystemTableEntry|Example}}|Comment</nowiki></code> where Example is the name of your system and Comment (optional) is a free text comment about your system <br />
* Save the page and click on the link to the new page<br />
* Select the "edit the page" option and paste <code><nowiki>{{subst:ThirdPartySystemInfoSubst}}</nowiki></code> into your new page and then save it. This will expand to a table. Edit the table replacing the placeholder values with the correct values for your system<br />
* If your system is going down or having problems, change the entry to <code><nowiki>{{ThirdPartySystemTableEntryDown|<your ci system name>}}</nowiki></code><br />
----<br />
<br />
Do you have a Gerrit CI account created for you by the Infrastructure team and you want to update it? [https://wiki.openstack.org/wiki/OldtoNewGerritCIAccount Read how here].<br />
<br />
[[Category:ThirdPartySystems]]</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=158181Manila/Meetings2017-11-25T09:58:48Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''NOTE: No meeting 23 Nov due to American Thanksgiving'''<br />
<br />
'''Scheduled for 30 Nov 2017, 15:00 UTC'''<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Use v3 cinder client instead of v2 cinder client (zhongjun)<br />
## https://review.openstack.org/#/c/522478/<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 16 Nov 2017, 15:00 UTC'''<br />
# The Manila community was not very active. (junboli)<br />
## - patches cost long time to review and merge.<br />
## - less response for questions in IRC channel.<br />
## - more core members are required.<br />
# Bug smash in China (zhongjun)<br />
# IPv6 driver capabilities required variables (ganso)<br />
# 3rd Party CIs may have to change to use Manila Tempest Plugin repo (raissa)<br />
## https://review.openstack.org/#/c/512300/<br />
<br />
<br />
'''Scheduled for 26 Oct 2017, 15:00 UTC'''<br />
# Manila test image (bswartz)<br />
## https://review.openstack.org/#/q/status:open+project:openstack/manila-test-image<br />
<br />
<br />
'''Scheduled for 19 Oct 2017, 15:00 UTC'''<br />
# Spec freeze / milestone 1 (bswartz)<br />
# py2 -> py3 (vkmc)<br />
## https://bugs.launchpad.net/manila/+bug/1482633 && https://review.openstack.org/#/c/289382/<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Zuul V3 migration status (raissa)<br />
## https://review.openstack.org/#/c/512559/ https://review.openstack.org/#/c/513075/ https://review.openstack.org/#/c/513076/<br />
## https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details<br />
<br />
<br />
'''Scheduled for 12 Oct 2017, 15:00 UTC'''<br />
# Manila Driver Maintainers and the DriverLog (dustins)<br />
# Important Manila Bugs (dustins)<br />
<br />
<br />
'''Scheduled for 5 Oct, 2017, 15:00 UTC'''<br />
# Gate issues<br />
# drivers_private_storage hard-delete vs soft-delete (ganso)<br />
# Bug Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 28 Sep, 2017, 15:00 UTC'''<br />
# Discuss and elicit Feedback for PTG<br />
# Bug Tsar/Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
# Dynamic Log Level (zhongjun)<br />
# Install guide tesing (bswartz)<br />
# Automatic generation of docs for configuration options (bswartz)<br />
# Timeouts (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=157795Manila/Meetings2017-11-13T09:30:02Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 9 Nov 2017, 15:00 UTC'''<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 26 Oct 2017, 15:00 UTC'''<br />
<br />
# Manila test image (bswartz)<br />
## https://review.openstack.org/#/q/status:open+project:openstack/manila-test-image<br />
<br />
<br />
'''Scheduled for 19 Oct 2017, 15:00 UTC'''<br />
# Spec freeze / milestone 1 (bswartz)<br />
# py2 -> py3 (vkmc)<br />
## https://bugs.launchpad.net/manila/+bug/1482633 && https://review.openstack.org/#/c/289382/<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Zuul V3 migration status (raissa)<br />
## https://review.openstack.org/#/c/512559/ https://review.openstack.org/#/c/513075/ https://review.openstack.org/#/c/513076/<br />
## https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details<br />
<br />
<br />
'''Scheduled for 12 Oct 2017, 15:00 UTC'''<br />
# Manila Driver Maintainers and the DriverLog (dustins)<br />
# Important Manila Bugs (dustins)<br />
<br />
<br />
'''Scheduled for 5 Oct, 2017, 15:00 UTC'''<br />
# Gate issues<br />
# drivers_private_storage hard-delete vs soft-delete (ganso)<br />
# Bug Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 28 Sep, 2017, 15:00 UTC'''<br />
# Discuss and elicit Feedback for PTG<br />
# Bug Tsar/Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
# Dynamic Log Level (zhongjun)<br />
# Install guide tesing (bswartz)<br />
# Automatic generation of docs for configuration options (bswartz)<br />
# Timeouts (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=157794Manila/Meetings2017-11-13T09:26:12Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 9 Nov 2017, 15:00 UTC'''<br />
# Let's go over new bugs (dustins )<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 26 Oct 2017, 15:00 UTC'''<br />
<br />
# Manila test image (bswartz)<br />
## https://review.openstack.org/#/q/status:open+project:openstack/manila-test-image<br />
<br />
<br />
'''Scheduled for 19 Oct 2017, 15:00 UTC'''<br />
# Spec freeze / milestone 1 (bswartz)<br />
# py2 -> py3 (vkmc)<br />
## https://bugs.launchpad.net/manila/+bug/1482633 && https://review.openstack.org/#/c/289382/<br />
# Let's go over new bugs (dustins)<br />
## https://etherpad.openstack.org/p/manila-bug-triage-pad<br />
# Zuul V3 migration status (raissa)<br />
## https://review.openstack.org/#/c/512559/ https://review.openstack.org/#/c/513075/ https://review.openstack.org/#/c/513076/<br />
## https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details<br />
<br />
<br />
'''Scheduled for 12 Oct 2017, 15:00 UTC'''<br />
# Manila Driver Maintainers and the DriverLog (dustins)<br />
# Important Manila Bugs (dustins)<br />
<br />
<br />
'''Scheduled for 5 Oct, 2017, 15:00 UTC'''<br />
# Gate issues<br />
# drivers_private_storage hard-delete vs soft-delete (ganso)<br />
# Bug Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 28 Sep, 2017, 15:00 UTC'''<br />
# Discuss and elicit Feedback for PTG<br />
# Bug Tsar/Czar (dustins)<br />
# Open discussion<br />
<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
# Dynamic Log Level (zhongjun)<br />
# Install guide tesing (bswartz)<br />
# Automatic generation of docs for configuration options (bswartz)<br />
# Timeouts (bswartz)<br />
<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=156688Manila/Meetings2017-09-14T09:54:16Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
# Dynamic Log Level (zhongjun)<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=156687Manila/Meetings2017-09-14T08:58:31Z<p>Zhongjun2: /* Previous meetings */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 7 Sep, 2017, 15:00 UTC'''<br />
# Specs and deadlines<br />
# Open Discussion<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=156686Manila/Meetings2017-09-14T08:58:16Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 14 Sep, 2017, 15:00 UTC'''<br />
# Add total count information in our list APIs (zhongjun)<br />
# Register and Document Policy in Code (zhongjun)<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 31 Aug, 2017, 15:00 UTC'''<br />
# Docs for share groups (bswartz)<br />
#* API Ref<br />
#* Admin guide<br />
#* More?<br />
# Move manila_tempest_tests to a new repo (raissa)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 17 Aug, 2017, 15:00 UTC'''<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-ptg-queens<br />
<br />
<br />
'''Scheduled for 10 Aug, 2017, 15:00 UTC'''<br />
# Bugs / RC1 Status<br />
#* https://launchpad.net/manila/+milestone/pike-rc1<br />
#* Quotas<br />
#** https://bugs.launchpad.net/manila/+bug/1707379<br />
#** https://bugs.launchpad.net/manila/+bug/1707378<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
<br />
<br />
'''Scheduled for 27 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* https://launchpad.net/manila/+milestone/pike-3<br />
# Bug Squash Day<br />
#* https://etherpad.openstack.org/p/pike-manila-bug-squash<br />
# Python 3 in Queens<br />
<br />
<br />
'''Scheduled for 20 Jul, 2017, 15:00 UTC'''<br />
# FPF Exception request - ONTAP QoS (gouthamr)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html<br />
#* https://review.openstack.org/#/c/484933/<br />
# IPv6 access revisited (bswartz)<br />
# Milestone 3<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 13 Jul, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
# Driverfixes<br />
# Docs migration<br />
# Bug Squash Day<br />
# Per share type quotas<br />
<br />
<br />
'''Scheduled for 29 Jun, 2017, 15:00 UTC'''<br />
# Revisit priorities for Pike<br />
# Bug squash?<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 22 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Status<br />
# Driver fixes to branches beyond stable/R-1 (gouthamr)<br />
<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# IDs and instance IDs in the driver interface<br />
#* https://bugs.launchpad.net/manila/+bug/1697581<br />
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py<br />
#* https://review.openstack.org/#/c/473864/<br />
<br />
<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=154703Manila/Meetings2017-06-15T02:01:47Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 15 Jun, 2017, 15:00 UTC'''<br />
# How should support both IPv6 and IPv4 with DHSS=true<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=154702Manila/Meetings2017-06-15T01:56:32Z<p>Zhongjun2: /* Previous meetings */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# Milestone 2<br />
# IPv6 Testing<br />
# Open Discussion<br />
<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=154535Manila/Meetings2017-06-07T09:52:28Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 8 Jun, 2017, 15:00 UTC'''<br />
# IPv6 Test<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=154534Manila/Meetings2017-06-07T09:52:00Z<p>Zhongjun2: /* Previous meetings */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 1 Jun, 2017, 15:00 UTC'''<br />
# Share groups + UI<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
Scheduled for 1 Jun, 2017, 15:00 UTC<br />
<br />
Share groups + UI<br />
Open Discussion<br />
<br />
'''Scheduled for 18 May, 2017, 15:00 UTC'''<br />
# PTG involvement<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html<br />
<br />
<br />
'''Scheduled for 4 May, 2017, 15:00 UTC'''<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
# Summit/PTG<br />
# Open Discussion<br />
<br />
'''Scheduled for 27 Apr, 2017, 15:00 UTC'''<br />
<br />
# Notification about vponomaryov's stepping out of project<br />
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.<br />
# Share usage monitoring (zhongjun)<br />
#* https://review.openstack.org/#/c/459150/<br />
<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
<br />
# Ensure shares (zhongjun)<br />
#* https://review.openstack.org/#/c/446494/<br />
# Update shares (zhongjun)<br />
#* https://review.openstack.org/#/c/453553/<br />
# Infinite shares (zhongjun)<br />
#* https://review.openstack.org/#/c/452097/<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# API filtering (zhongjun)<br />
#* https://review.openstack.org/#/c/447775/<br />
<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=153420Manila/Meetings2017-04-20T03:52:43Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 20 Apr, 2017, 15:00 UTC'''<br />
# Deadline for 4 specs with extensions<br />
#* https://review.openstack.org/#/c/446494/<br />
#* https://review.openstack.org/#/c/453553/<br />
#* https://review.openstack.org/#/c/452097/<br />
#* https://review.openstack.org/#/c/447775/<br />
# Spec Validation: https://review.openstack.org/456398 (tbarron)<br />
# Add blockdiag diagram family capability to manila specs: https://review.openstack.org/456404 (tbarron)<br />
# Stop Translating Log messages: https://review.openstack.org/#/c/452189 (tbarron)<br />
# "infinite" share (zhongjun)<br />
#* What "infinite" shares ought to be?<br />
#* How should we collect actual share usage?<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 13 Apr, 2017, 15:00 UTC'''<br />
# Spec Freeze<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 6 Apr, 2017, 15:00 UTC'''<br />
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)<br />
# Pike Specs<br />
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus<br />
<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=152877Manila/Meetings2017-03-30T08:05:13Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
#*https://review.openstack.org/#/c/446494<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=152876Manila/Meetings2017-03-30T08:04:50Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
https://review.openstack.org/#/c/446494<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=152875Manila/Meetings2017-03-30T08:04:01Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 30 Mar, 2017, 15:00 UTC'''<br />
# ensure share(zhongjun_)<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=152874Manila/Meetings2017-03-30T08:03:21Z<p>Zhongjun2: /* Previous meetings */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
'''Scheduled for 23 Mar, 2017, 15:00 UTC'''<br />
# SSL certificate verification<br />
# Specs<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
# Open Discussion<br />
<br />
'''Scheduled for 9 Mar, 2017, 15:00 UTC'''<br />
# Specs Deadline (continued) (bswartz)<br />
# Community Goals (bswartz)<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst<br />
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst<br />
# Experimental APIs (bswartz)<br />
# Refactor of Tempest scenario base classes (bswartz)<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html<br />
<br />
'''Scheduled for 2 Mar, 2017, 15:00 UTC'''<br />
# Experimental Features (bswartz)<br />
# Specs Deadline (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 16 Feb, 2017, 15:00 UTC'''<br />
# i18n liason needed<br />
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n<br />
# PTG<br />
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
<br />
<br />
'''Scheduled for 2 Feb, 2017, 15:00 UTC'''<br />
# Microversions (rhagarty)<br />
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.<br />
# Share groups bugs<br />
#* https://bugs.launchpad.net/manila/+bug/1660321<br />
#* https://bugs.launchpad.net/manila/+bug/1660319<br />
#* https://bugs.launchpad.net/manila/+bug/1659023<br />
#* https://bugs.launchpad.net/manila/+bug/1661266<br />
#* https://bugs.launchpad.net/manila/+bug/1661268<br />
# LVM revert to snapshot<br />
<br />
<br />
'''Scheduled for 26 Jan, 2017, 15:00 UTC'''<br />
# Feature Freeze<br />
#* IPv6<br />
# Open Discussion<br />
<br />
<br />
'''Scheduled for 19 Jan, 2017, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus<br />
# Filterscheduler warning in logs (ravichandran)<br />
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "<br />
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)<br />
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)<br />
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Dec, 2016, 15:00 UTC'''<br />
# Specs implementation status (bswartz)<br />
# briefly clarify the "24 hour rule" (tbarron)<br />
# Manila CI Tempest Test Cases are Failing (ravichandran)<br />
<br />
<br />
<br />
'''Scheduled for 8 Dec, 2016, 15:00 UTC'''<br />
# PTG (bswartz)<br />
# Default share type (tbarron)<br />
# migration-start new command syntax (ganso)<br />
# remove access-update fallback to access_allow/deny? (tbarron)<br />
# decision of deadline for driver config docs in devref removal (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 1 Dec, 2016, 15:00 UTC'''<br />
# Discussion about driver docs in devref (ganso)<br />
# Specs implementation status (bswartz)<br />
<br />
<br />
'''Scheduled for 17 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization (bswartz)<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs<br />
<br />
<br />
'''Scheduled for 10 Nov, 2016, 15:00 UTC'''<br />
# Decide defaults for migration options (ganso)<br />
#* https://review.openstack.org/#/c/392291<br />
<br />
'''Scheduled for 3 Nov, 2016, 15:00 UTC'''<br />
# Spec review & prioritization<br />
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open<br />
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus<br />
#* List of open specs<br />
#** manila-ipv6<br />
#** add-db-manage-purge<br />
#** create-share-from-snapshot-extra-spec<br />
#** support-quota-usage-in-detail<br />
#** ocata-migration-improvements<br />
#** data-service-jobs-table<br />
#** add-share-type-filter-to-get-pools<br />
#** manila-share-revert-to-snapshot<br />
#** scenario-tests<br />
#** mountable_snapshots<br />
#** share-network-multiple-subnets<br />
#** share-retype<br />
#** multiple_protocol_share<br />
#** access-groups<br />
#** backup_share<br />
#** manila-share-groups<br />
#** data-service-api<br />
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit<br />
<br />
'''Scheduled for 20 Oct, 2016, 15:00 UTC'''<br />
# Specs and Deadlines (bswartz)<br />
#* https://review.openstack.org/#/c/374883/<br />
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)<br />
# Open Discussion<br />
<br />
'''Scheduled for 13 Oct, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A<br />
# PTG<br />
<br />
'''Scheduled for 6 Oct, 2016, 15:00 UTC'''<br />
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)<br />
#* https://review.openstack.org/#/c/369668/<br />
<br />
'''Scheduled for 29 Sep, 2016, 15:00 UTC'''<br />
# Ocata Design Summit<br />
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics<br />
# Open Discussion<br />
<br />
'''Scheduled for 22 Sep, 2016, 15:00 UTC'''<br />
# Specs process<br />
#* https://review.openstack.org/#/c/374883<br />
<br />
'''Scheduled for 8 Sep, 2016, 15:00 UTC'''<br />
# RC1 status<br />
#* https://launchpad.net/manila/+milestone/newton-rc1<br />
# Project Logo<br />
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79<br />
# Container Driver Security (aovchinnikov)<br />
#* https://review.openstack.org/#/c/353463/<br />
# Security "vulnerability-managed" tag for manila (tbarron)<br />
# Zanata translations for manila-client and manila-ui (tbarron)<br />
# Tempest direction (tbarron)<br />
<br />
'''Scheduled for 1 Sep, 2016, 15:00 UTC'''<br />
# Mascot (bswartz)<br />
# Vulnerability Management<br />
<br />
'''Scheduled for 25 Aug, 2016, 15:00 UTC'''<br />
# Huawei share replication and CI<br />
# IPv6 (cknight)<br />
# Open Discussion<br />
<br />
'''Scheduled for 18 Aug, 2016, 15:00 UTC'''<br />
# Driver private data admin API<br />
#* Disagreement abounds on how this API is to be designed, tested, and presented.<br />
#* https://review.openstack.org/#/c/315346/<br />
# Scenario tests are broken<br />
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html<br />
# Revert to snapshot<br />
#* https://review.openstack.org/#/c/340502/<br />
#* https://review.openstack.org/#/c/356682/<br />
<br />
"Scheduled for 11 Aug, 2016, 15:00 UTC"<br />
# None<br />
<br />
'''Scheduled for 4 Aug, 2016, 15:00 UTC'''<br />
# Migration APIs<br />
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html<br />
# Correct approach for avoiding races<br />
<br />
'''Scheduled for 28 Jul, 2016, 15:00 UTC'''<br />
# Stepping Down as Docs Liaison (dustins)<br />
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.<br />
# N-3 Review focus<br />
#* https://etherpad.openstack.org/p/manila-newton3-priorities<br />
<br />
'''Scheduled for 21 Jul, 2016, 15:00 UTC'''<br />
# Migrate API reference into tree (dgonzalez)<br />
#* https://review.openstack.org/#/c/313874/<br />
<br />
'''Scheduled for 14 Jul, 2016, 15:00 UTC'''<br />
# N-2 milestone<br />
# Managing initial security (of the root directory) for new shares<br />
# Mascot/Logo discussion<br />
# Tempest alternatives<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=127527Manila/Meetings2016-06-30T12:51:04Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
#* https://review.openstack.org/#/c/330306<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=127526Manila/Meetings2016-06-30T12:50:27Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 30 Jun, 2016, 15:00 UTC'''<br />
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)<br />
https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839<br />
# share backup spec discussion (zhongjun)<br />
* https://review.openstack.org/#/c/330306<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 23 Jun, 2016, 15:00 UTC'''<br />
# Implement extend and shrink features for glusterfs driver (DaiDV)<br />
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)<br />
# Creating a second share instance for driver-assisted migration (ganso)<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Drivers with minimum size for shares (tpsilva)<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=126722Manila/Meetings2016-06-14T11:48:26Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
#* https://review.openstack.org/#/c/329392/<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=126721Manila/Meetings2016-06-14T11:47:31Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
https://review.openstack.org/#/c/329392/<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=126625Manila/Meetings2016-06-13T03:22:01Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 16 Jun, 2016, 15:00 UTC'''<br />
# A share support multiple protocols (zhongjun)<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
<br />
'''Scheduled for 9 Jun, 2016, 15:00 UTC'''<br />
# HPB feature (mkoderer)<br />
# the fate of nova-network support in manila (gouthamr)<br />
# multi-AZ tests in the gate<br />
<br />
'''Scheduled for 2 Jun, 2016, 15:00 UTC'''<br />
# N-1 milestone (bswartz)<br />
# Decision on APIv1 removal for newton (bswartz)<br />
# Model updates from drivers (bswartz)<br />
# Midcycle meetup<br />
# Spec update<br />
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)<br />
<br />
'''Scheduled for 26 May, 2016, 15:00 UTC'''<br />
# N-1 milestone<br />
# Update access remaining work<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
# Share Backup(zhongjun)<br />
# Snapshot Restore (cknight)<br />
# Specs (ganso)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=125303Manila/Meetings2016-05-16T09:56:26Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
# Share Backup(zhongjun)<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=125302Manila/Meetings2016-05-16T09:56:05Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
# Share Backup(zhongjun)<br />
<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=125301Manila/Meetings2016-05-16T09:55:25Z<p>Zhongjun2: /* Weekly Manila team meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
<br />
# Share Backup(zhongjun)<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=125299Manila/Meetings2016-05-16T09:50:52Z<p>Zhongjun2: /* Weekly Manila team meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Share Backup(zhongjun)<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
# Open Discussion<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=125298Manila/Meetings2016-05-16T09:49:55Z<p>Zhongjun2: /* Weekly Manila team meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 19 May, 2016, 15:00 UTC'''<br />
# Share Backup(zhongjun)<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* UI Customization<br />
#* Nova-network removal<br />
#* APIv1 removal<br />
#* Model updates from the driver<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 12 May, 2016, 15:00 UTC'''<br />
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)<br />
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.<br />
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Py3 functional tests<br />
#* Replication with share networks<br />
#* Service-check<br />
#* Container driver<br />
<br />
'''Scheduled for 5 May, 2016, 15:00 UTC'''<br />
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup<br />
#* Documentation update (dustins/gouthamr)<br />
#* User messages<br />
#* Experimental features in UI<br />
#* Share/snapshot size mismatch<br />
# BP Specs (tbarron)<br />
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)<br />
<br />
'''Scheduled for 14 Apr, 2016, 15:00 UTC'''<br />
# Manage API retrying (gouthamr/nidhimittalhada)<br />
# Tempest test structuring - resource sharing and cleanup issues (akerr)<br />
# Snapshot support common capability in the documentation (gouthamr)<br />
<br />
'''Scheduled for 7 Apr, 2016, 15:00 UTC'''<br />
# Access rules (bswartz)<br />
# Design summit planning (bswartz)<br />
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Release notes, continued (gouthamr)<br />
#* Link: https://review.openstack.org/#/c/300656/<br />
# Midcycle meetup<br />
# Access Groups<br />
#* https://wiki.openstack.org/wiki/Manila/design/access_groups<br />
# Revert to snapshot<br />
<br />
'''Scheduled for 31 Mar, 2016, 15:00 UTC'''<br />
# Mitaka release status<br />
#* RC1 expected to be the Mitaka release build<br />
#* Last day for a re-spin is today<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html<br />
# Design summit planning<br />
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup<br />
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html<br />
#* Voting open now for summit topics<br />
#** https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Manila Documentation (gouthamr)<br />
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)<br />
#* Need a docs liaison<br />
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation<br />
#* Release Notes<br />
#** http://docs.openstack.org/developer/reno/usage.html<br />
# Managing/unmanaging replicated shares and snapshots (gouthamr)<br />
<br />
'''Scheduled for 24 Mar, 2016, 15:00 UTC'''<br />
# Design summit planning<br />
#* https://etherpad.openstack.org/p/manila-newton-summit-topics<br />
# Question about share servers (Jay.Xu)<br />
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.<br />
<br />
'''Scheduled for 10 Mar, 2016, 15:00 UTC'''<br />
# Common Capabilities Matrix (dustins)<br />
#* https://review.openstack.org/#/c/288504/<br />
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.<br />
#* I've got most drivers covered now.<br />
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!<br />
<br />
'''Scheduled for 25 Feb, 2016, 15:00 UTC'''<br />
<br />
# OpenStack bug smash event (toabctl, mkoderer)<br />
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka<br />
# Status of new drivers<br />
## M.3 deadline is a week away.<br />
## Only a few things have merged in the last couple days. At this rate, many things won't make it.<br />
## Zuul is busy and will only get worse until the deadline.<br />
## Multiple Manila gate breakages have occurred recently, and more are likely.<br />
## The Manila tests are very unreliable at concurrency > 1.<br />
## The generic driver is too slow to pass the gate at concurrency = 1.<br />
## The new drivers *are* fast enough to run at concurrency = 1.<br />
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.<br />
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.<br />
# Next Manila mid-cycle location<br />
## Proposal is to do it in Germany<br />
## Need to know who could attend at that location.<br />
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?<br />
<br />
'''Scheduled for 18 Feb, 2016, 15:00 UTC'''<br />
<br />
# Feature Proposal Freeze (bswartz)<br />
# Open Discussion<br />
<br />
'''Scheduled for 11 Feb, 2016, 15:00 UTC'''<br />
<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support<br />
#* https://review.openstack.org/#/c/277731/<br />
# Next Manila mid-cycle (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-n-release-midcycle<br />
# Replication + ZFS Driver (bswartz)<br />
#* https://review.openstack.org/#/c/238572<br />
# Driver FPF (bswartz)<br />
#* https://review.openstack.org/#/c/279090/<br />
#* https://review.openstack.org/#/c/278169/<br />
# HDFS CI (bswartz)<br />
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''<br />
# Data service handling protocol mount commands (ganso)<br />
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting<br />
# Separate process for copy on data service (tpsilva)<br />
# ZFS driver (bswartz)<br />
# First party drivers share migration support cooperation (ganso)<br />
<br />
'''Scheduled for 28 Jan, 2016, 15:00 UTC'''<br />
# Hierarchical port binding support (mkoderer)<br />
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding<br />
# Core reviewer team and other manila-related projects (bswartz)<br />
# Replication status (bswartz)<br />
<br />
'''Scheduled for 21 Jan, 2016, 15:00 UTC'''<br />
# Update_access backwards compatibility approach discussion. (ganso)<br />
# Exposing the Data Service to drivers. (ganso)<br />
# Snapshot manage/unmanage (bswartz)<br />
<br />
'''Scheduled for 17 Dec, 2015, 15:00 UTC'''<br />
# Proposal for share groups (cknight)<br />
# Liberty.1 stable release (bswartz)<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Architectural concerns and interoperability of new features (cknight)<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99359Manila/Meetings2015-12-10T13:12:29Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99358Manila/Meetings2015-12-10T13:11:48Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# 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 it to capabilities_and_extra_specs.rst?(zhongjun)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99357Manila/Meetings2015-12-10T13:07:13Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler, and Does we need to remove it or save it as Qos support flat?and write it to capabilities_and_extra_specs.rst?(zhongjun)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99348Manila/Meetings2015-12-10T12:14:13Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as Qos support flat?and write it to capabilities_and_extra_specs.rst?(zhongjun)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99345Manila/Meetings2015-12-10T12:13:25Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as common Qos support flat?and write it to capabilities_and_extra_specs.rst?(zhongjun)<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99344Manila/Meetings2015-12-10T12:11:51Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as common Qos support flat?and write it to capabilities_and_extra_specs.rst?<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99343Manila/Meetings2015-12-10T12:11:33Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler. <br />
Does we need to remove it or save it as common Qos support flat?and write it to capabilities_and_extra_specs?<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99341Manila/Meetings2015-12-10T12:11:01Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as common Qos support flat?<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99340Manila/Meetings2015-12-10T12:10:29Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as Qos support flat?<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99339Manila/Meetings2015-12-10T12:10:13Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as Qos support flat?<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99338Manila/Meetings2015-12-10T12:09:57Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as Qos support flat?<br />
## https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
## https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
## https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
## https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=99337Manila/Meetings2015-12-10T12:09:04Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''Scheduled for 10 Dec, 2015, 15:00 UTC'''<br />
# The most of the driver report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as Qos support flat?<br />
https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391<br />
https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354<br />
https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257<br />
https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 3 Dec, 2015, 15:00 UTC'''<br />
# Midcycle meetup<br />
# 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)<br />
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)<br />
## https://review.openstack.org/#/c/252060/<br />
## Mostly for awareness, this is now merged and should be backwards compatible.<br />
## 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?<br />
# CI reliability<br />
## 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)<br />
## http://ci-watch.tintri.com/project?project=manila<br />
## https://review.openstack.org/#/c/232293/<br />
## https://review.openstack.org/#/c/235522/<br />
## https://review.openstack.org/#/c/235726/<br />
## https://review.openstack.org/#/c/249999/<br />
## https://review.openstack.org/#/c/237454/<br />
<br />
'''Scheduled for 19 Nov, 2015, 15:00 UTC'''<br />
# GB --> GiB (markstur)<br />
# OpenStack Manuals and Devref (markstur)<br />
#* Config Ref (and others) are moving to .RST!<br />
#* How should we document prior releases in devref?<br />
# Midcycle Meetup Date (bswartz)<br />
# Deadlines for features (bswartz)<br />
#* Feature proposal freeze vs Big Features<br />
#* New drivers<br />
# Data Copy Service network approach discussion (ganso)<br />
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing<br />
<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities<br />
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
#** eg: share_type: qos_support='<is> True' or '<is> False' <br />
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
#** driver update: qos_support=true<br />
#** An alternative could be to have the driver report a range<br />
# Manila DR update (ameade)<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Manila Driver minimum requirements document update (ganso)<br />
# Manila Data Copy service name (bswartz)<br />
#*https://review.openstack.org/#/c/244286/<br />
# Upcoming change for Manila CI hooks (vponomaryov)<br />
#*https://review.openstack.org/#/c/243233/<br />
# 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)<br />
#*http://paste.openstack.org/show/478675/<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/QoS&diff=96978Manila/QoS2015-11-16T11:26:33Z<p>Zhongjun2: /* Method 1 */</p>
<hr />
<div>=Intro=<br />
<br />
<br />
https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
<br />
The goal is to add an interface so that Manila admins can use to set share QoS<br />
specification (IOPS, bandwidth, Latency, priority and other vendor specified attributes),<br />
which can be enforced in Manila back-end;<br />
<br />
The design for QoS isn't complete. We have a vision for the feature, and we're trying to define the details.<br />
<br />
=Problem description=<br />
<br />
The current implementation of QoS spec management process in<br />
Manila provides no validation of the specs key/value pair.<br />
Administrators have no way to get a response as to whether the QoS spec<br />
key/value pair they just created is valid or not. The validation of the<br />
key/value pair only happens during the share creation process which is far too<br />
late by that point. Having a validation of the key/value pair done immediately<br />
within the QoS spec creation or edit process will significantly improve the<br />
usability and user experience of this task.<br />
<br />
=Method 1=<br />
Use the extra-specs tables with vendor scoped keys.<br />
<br />
How to make sure the user need create a share with qos?<br />
<br />
1、Add qos_support in share type to make sure the user need create a share with qos.<br />
<br />
common qos:<br />
qos:max_iops<br />
qos:min_iops<br />
qos:max_bandwith<br />
qos:min_bandwith<br />
<br />
max: The prefix 'Max_' is means the max value can not be exceed.<br />
<br />
min: The prefix 'min_' is means the min value is a soft limit, that make the current value is larger than the minimum value as much as possible.<br />
<br />
eg: share_type: qos_support='<is> True' or '<is> False'<br />
qos:max_iops=100<br />
netapp:max_test=100<br />
driver update: qos_support=true<br />
<br />
Add qos_support in common capabilities.(https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)<br />
<br />
=Method 2=<br />
<br />
Add an interface so that admins can use to express QoS requirements for shares<br />
(of specific back-ends), which will be consumed by back-end drivers.<br />
<br />
- Add a new resource extension to 'types_extra_specs' API extension to allow list/create/update/delete of type QoS specs.<br />
- Modify 'type_manage' API extension to be able to accept QoS specification info.<br />
qos-associate Associates qos specs with specified share type.<br />
qos-create Creates a qos specs.<br />
qos-delete Deletes a specified qos specs.<br />
qos-disassociate Disassociates qos specs from specified share type.<br />
qos-disassociate-all Disassociates qos specs from all associations.<br />
qos-get-association Gets all associations for specified qos specs.<br />
qos-key Sets or unsets specifications for a qos spec.<br />
qos-list Lists qos specs.<br />
qos-show Shows a specified qos specs.<br />
- Modify share_types.create() to accept QoS specification info and do the checks.<br />
- Add 'qos_specs' to request_specs and filter properties for a share create request and pass to driver.<br />
- To enable the QoS for Manila driver, an qos spec needs to bind to a share type. All the following<br />
changes apply to the Manila driver code.<br />
Create share: If QoS is enabled and specs is available as the QoS key, set the qos spec of the share<br />
into the specified qos spec value.<br />
Create snapshot: The QoS attributes will be copied to the snapshot.<br />
Create share from snapshot: If QoS is enabled and IOThrottling is available as the QoS key, set the<br />
qos spec of the share into the specified qos spec value.<br />
<br />
Database schema changes:<br />
<br />
* A new qos_specs_id boolean column will be added to the share_types table.<br />
* A new quality_of_service_specs table will be created for a particular share types. There will be<br />
one entry in quality_of_service_specs table for every share_type_id and specs_id combination.<br />
It will be a one-to-one relationship.<br />
<br />
::<br />
<br />
mysql> DESC quality_of_service_specs;<br />
+------------+--------------+------+-----+---------+-------+<br />
| Field | Type | Null | Key | Default | Extra |<br />
+------------+--------------+------+-----+---------+-------+<br />
| created_at | datetime | YES | | NULL | |<br />
| updated_at | datetime | YES | | NULL | |<br />
| deleted_at | datetime | YES | | NULL | |<br />
| deleted | tinyint(1) | YES | | NULL | |<br />
| id | varchar(36) | NO | PRI | NULL | |<br />
| specs_id | varchar(36) | YES | MUL | NULL | |<br />
| key | varchar(255) | YES | | NULL | |<br />
| value | varchar(255) | YES | | NULL | |<br />
+------------+--------------+------+-----+---------+-------+<br />
8 rows in set (0.00 sec)<br />
<br />
mysql> DESC share_types;<br />
+--------------+--------------+------+-----+---------+-------+<br />
| Field | Type | Null | Key | Default | Extra |<br />
+--------------+--------------+------+-----+---------+-------+<br />
| created_at | datetime | YES | | NULL | |<br />
| updated_at | datetime | YES | | NULL | |<br />
| deleted_at | datetime | YES | | NULL | |<br />
| deleted | tinyint(1) | YES | | NULL | |<br />
| id | varchar(36) | NO | PRI | NULL | |<br />
| name | varchar(255) | YES | | NULL | |<br />
| qos_specs_id | varchar(36) | YES | MUL | NULL | |<br />
| is_public | tinyint(1) | YES | | NULL | |<br />
+--------------+--------------+------+-----+---------+-------+<br />
8 rows in set (0.00 sec)<br />
<br />
<br />
REST API impact:<br />
<br />
* Extend share type creation response to include qos_specs_id field<br />
* Extend share type list to include qos_specs_id field<br />
* Extend share type detail to include qos_specs_id field<br />
* Add ability to create/delete a qos specs<br />
* Add ability to associates/disassociate qos specs with specified share type<br />
* Add policy for the new extension<br />
<br />
Other end user impact:<br />
<br />
* Manila-ui should be updated to support this new extension.<br />
* python-manilaclient should be updated to allow the use of this new extension.<br />
<br />
Proposed python-manilaclient shell interface::<br />
<br />
manila qos-associate <qos_specs> <share_type_id><br />
Associates qos specs with specified share type.<br />
<br />
manila qos-create <name> [--max_kbps <max_kbps>] [--min_kbps <min_kbps>] [--max_iops <max_iops>] [--min_iops <min_iops>] <key=value> [<key=value> ...]<br />
Creates a qos specs.<br />
max: The prefix 'Max_' is means the max value can not be exceed.<br />
<br />
min: The prefix 'min_' is means the min value is a soft limit, that make the current value is larger than the minimum value as much as possible. <br />
<br />
manila qos-delete [--force <True|False>] <qos_specs><br />
Deletes a specified qos specs.<br />
<br />
manila qos-disassociate <qos_specs> <share_type_id><br />
Disassociates qos specs from specified share type.<br />
<br />
manila qos-disassociate-all <qos_specs><br />
Disassociates qos specs from all associations.<br />
<br />
manila qos-get-association <qos_specs><br />
Gets all associations for specified qos specs.<br />
<br />
manila qos-key <qos_specs> <action> key=value [key=value ...]<br />
Sets or unsets specifications for a qos spec.<br />
<br />
manila qos-list<br />
Lists qos specs.<br />
<br />
manila qos-show <qos_specs><br />
Shows a specified qos specs.<br />
<br />
=Question=<br />
1.Why QoS can not be used in the same way - extra specs with possibilities?<br />
<br />
Because the QoS is an independant resource and special feature. The QoS need a complete set of API.<br />
<br />
<br />
2.Why associate QoS only with share type? why not tenant? user? specific share?<br />
<br />
For user only need to see share_type. If user want to use QoS, then they will associate QoS with share type.<br />
If we provide more access(such as: add QoS as a parameter when we creating a share), User will feel more<br />
complicated.<br />
<br />
=Cinder QoS vs Manila QoS=<br />
*Manila QoS add a few common capabilities in qos-create command.<br />
*Cinder support both front-end QoS and back-end QoS, Manila only support back-end QoS.<br />
<br />
=Assignee(s)=<br />
-----------<br />
<br />
Primary assignee:<br />
zhongjun (jun.zhongjun@huawei.com)<br />
<br />
Other contributors:<br />
zhaohua (zhaohua.zhao@huawei.com)<br />
<br />
=Work Items=<br />
<br />
* Add logic to coordinate calling each driver's ``validate`` function<br />
* Add ``validate`` function to base manila driver<br />
* Add ``validate`` function to lvm driver<br />
<br />
=Dependencies=<br />
<br />
Unit tests for all changed files<br />
<br />
=Documentation Impact=<br />
<br />
* The manila API documentation will need to be updated to reflect the fact that the API may return a failure.<br />
<br />
==Sub Pages==<br />
<br />
<br />
{{Special:PrefixIndex/:Manila/QoS|hideredirects=1}}</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/QoS&diff=96977Manila/QoS2015-11-16T11:26:06Z<p>Zhongjun2: /* Method 1 */</p>
<hr />
<div>=Intro=<br />
<br />
<br />
https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
<br />
The goal is to add an interface so that Manila admins can use to set share QoS<br />
specification (IOPS, bandwidth, Latency, priority and other vendor specified attributes),<br />
which can be enforced in Manila back-end;<br />
<br />
The design for QoS isn't complete. We have a vision for the feature, and we're trying to define the details.<br />
<br />
=Problem description=<br />
<br />
The current implementation of QoS spec management process in<br />
Manila provides no validation of the specs key/value pair.<br />
Administrators have no way to get a response as to whether the QoS spec<br />
key/value pair they just created is valid or not. The validation of the<br />
key/value pair only happens during the share creation process which is far too<br />
late by that point. Having a validation of the key/value pair done immediately<br />
within the QoS spec creation or edit process will significantly improve the<br />
usability and user experience of this task.<br />
<br />
=Method 1=<br />
Use the extra-specs tables with vendor scoped keys.<br />
<br />
How to make sure the user need create a share with qos?<br />
<br />
1、Add qos_support in share type to make sure the user need create a share with qos.<br />
<br />
common qos:<br />
qos:max_iops<br />
qos:min_iops<br />
qos:max_bandwith<br />
qos:min_bandwith<br />
<br />
max: The prefix 'Max_' is means the max value can not be exceed.<br />
min: The prefix 'min_' is means the min value is a soft limit, that make the current value is larger than the minimum value as much as possible.<br />
<br />
eg: share_type: qos_support='<is> True' or '<is> False'<br />
qos:max_iops=100<br />
netapp:max_test=100<br />
driver update: qos_support=true<br />
<br />
Add qos_support in common capabilities.(https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)<br />
<br />
=Method 2=<br />
<br />
Add an interface so that admins can use to express QoS requirements for shares<br />
(of specific back-ends), which will be consumed by back-end drivers.<br />
<br />
- Add a new resource extension to 'types_extra_specs' API extension to allow list/create/update/delete of type QoS specs.<br />
- Modify 'type_manage' API extension to be able to accept QoS specification info.<br />
qos-associate Associates qos specs with specified share type.<br />
qos-create Creates a qos specs.<br />
qos-delete Deletes a specified qos specs.<br />
qos-disassociate Disassociates qos specs from specified share type.<br />
qos-disassociate-all Disassociates qos specs from all associations.<br />
qos-get-association Gets all associations for specified qos specs.<br />
qos-key Sets or unsets specifications for a qos spec.<br />
qos-list Lists qos specs.<br />
qos-show Shows a specified qos specs.<br />
- Modify share_types.create() to accept QoS specification info and do the checks.<br />
- Add 'qos_specs' to request_specs and filter properties for a share create request and pass to driver.<br />
- To enable the QoS for Manila driver, an qos spec needs to bind to a share type. All the following<br />
changes apply to the Manila driver code.<br />
Create share: If QoS is enabled and specs is available as the QoS key, set the qos spec of the share<br />
into the specified qos spec value.<br />
Create snapshot: The QoS attributes will be copied to the snapshot.<br />
Create share from snapshot: If QoS is enabled and IOThrottling is available as the QoS key, set the<br />
qos spec of the share into the specified qos spec value.<br />
<br />
Database schema changes:<br />
<br />
* A new qos_specs_id boolean column will be added to the share_types table.<br />
* A new quality_of_service_specs table will be created for a particular share types. There will be<br />
one entry in quality_of_service_specs table for every share_type_id and specs_id combination.<br />
It will be a one-to-one relationship.<br />
<br />
::<br />
<br />
mysql> DESC quality_of_service_specs;<br />
+------------+--------------+------+-----+---------+-------+<br />
| Field | Type | Null | Key | Default | Extra |<br />
+------------+--------------+------+-----+---------+-------+<br />
| created_at | datetime | YES | | NULL | |<br />
| updated_at | datetime | YES | | NULL | |<br />
| deleted_at | datetime | YES | | NULL | |<br />
| deleted | tinyint(1) | YES | | NULL | |<br />
| id | varchar(36) | NO | PRI | NULL | |<br />
| specs_id | varchar(36) | YES | MUL | NULL | |<br />
| key | varchar(255) | YES | | NULL | |<br />
| value | varchar(255) | YES | | NULL | |<br />
+------------+--------------+------+-----+---------+-------+<br />
8 rows in set (0.00 sec)<br />
<br />
mysql> DESC share_types;<br />
+--------------+--------------+------+-----+---------+-------+<br />
| Field | Type | Null | Key | Default | Extra |<br />
+--------------+--------------+------+-----+---------+-------+<br />
| created_at | datetime | YES | | NULL | |<br />
| updated_at | datetime | YES | | NULL | |<br />
| deleted_at | datetime | YES | | NULL | |<br />
| deleted | tinyint(1) | YES | | NULL | |<br />
| id | varchar(36) | NO | PRI | NULL | |<br />
| name | varchar(255) | YES | | NULL | |<br />
| qos_specs_id | varchar(36) | YES | MUL | NULL | |<br />
| is_public | tinyint(1) | YES | | NULL | |<br />
+--------------+--------------+------+-----+---------+-------+<br />
8 rows in set (0.00 sec)<br />
<br />
<br />
REST API impact:<br />
<br />
* Extend share type creation response to include qos_specs_id field<br />
* Extend share type list to include qos_specs_id field<br />
* Extend share type detail to include qos_specs_id field<br />
* Add ability to create/delete a qos specs<br />
* Add ability to associates/disassociate qos specs with specified share type<br />
* Add policy for the new extension<br />
<br />
Other end user impact:<br />
<br />
* Manila-ui should be updated to support this new extension.<br />
* python-manilaclient should be updated to allow the use of this new extension.<br />
<br />
Proposed python-manilaclient shell interface::<br />
<br />
manila qos-associate <qos_specs> <share_type_id><br />
Associates qos specs with specified share type.<br />
<br />
manila qos-create <name> [--max_kbps <max_kbps>] [--min_kbps <min_kbps>] [--max_iops <max_iops>] [--min_iops <min_iops>] <key=value> [<key=value> ...]<br />
Creates a qos specs.<br />
max: The prefix 'Max_' is means the max value can not be exceed.<br />
<br />
min: The prefix 'min_' is means the min value is a soft limit, that make the current value is larger than the minimum value as much as possible. <br />
<br />
manila qos-delete [--force <True|False>] <qos_specs><br />
Deletes a specified qos specs.<br />
<br />
manila qos-disassociate <qos_specs> <share_type_id><br />
Disassociates qos specs from specified share type.<br />
<br />
manila qos-disassociate-all <qos_specs><br />
Disassociates qos specs from all associations.<br />
<br />
manila qos-get-association <qos_specs><br />
Gets all associations for specified qos specs.<br />
<br />
manila qos-key <qos_specs> <action> key=value [key=value ...]<br />
Sets or unsets specifications for a qos spec.<br />
<br />
manila qos-list<br />
Lists qos specs.<br />
<br />
manila qos-show <qos_specs><br />
Shows a specified qos specs.<br />
<br />
=Question=<br />
1.Why QoS can not be used in the same way - extra specs with possibilities?<br />
<br />
Because the QoS is an independant resource and special feature. The QoS need a complete set of API.<br />
<br />
<br />
2.Why associate QoS only with share type? why not tenant? user? specific share?<br />
<br />
For user only need to see share_type. If user want to use QoS, then they will associate QoS with share type.<br />
If we provide more access(such as: add QoS as a parameter when we creating a share), User will feel more<br />
complicated.<br />
<br />
=Cinder QoS vs Manila QoS=<br />
*Manila QoS add a few common capabilities in qos-create command.<br />
*Cinder support both front-end QoS and back-end QoS, Manila only support back-end QoS.<br />
<br />
=Assignee(s)=<br />
-----------<br />
<br />
Primary assignee:<br />
zhongjun (jun.zhongjun@huawei.com)<br />
<br />
Other contributors:<br />
zhaohua (zhaohua.zhao@huawei.com)<br />
<br />
=Work Items=<br />
<br />
* Add logic to coordinate calling each driver's ``validate`` function<br />
* Add ``validate`` function to base manila driver<br />
* Add ``validate`` function to lvm driver<br />
<br />
=Dependencies=<br />
<br />
Unit tests for all changed files<br />
<br />
=Documentation Impact=<br />
<br />
* The manila API documentation will need to be updated to reflect the fact that the API may return a failure.<br />
<br />
==Sub Pages==<br />
<br />
<br />
{{Special:PrefixIndex/:Manila/QoS|hideredirects=1}}</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=96567Manila/Meetings2015-11-12T13:20:59Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''NOTE:''' USA-based attendees should remember to double check the meeting time as the end of daylight savings time will move the meeting earlier in your day.<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
<br />
# Which method is better for Manila QoS(independent way or just use extra specs )<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities(https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
eg: share_type: qos_support='<is> True' or '<is> False' <br />
netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
driver update: qos_support=true<br />
<br />
# Manila DR update<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/Meetings&diff=96566Manila/Meetings2015-11-12T13:20:31Z<p>Zhongjun2: /* Next meeting */</p>
<hr />
<div><br />
= Weekly Manila team meeting =<br />
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''<br />
<br />
If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, 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.<br />
<br />
== Next meeting ==<br />
'''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.''<br />
<br />
'''NOTE:''' USA-based attendees should remember to double check the meeting time as the end of daylight savings time will move the meeting earlier in your day.<br />
<br />
'''Scheduled for 12 Nov, 2015, 15:00 UTC'''<br />
<br />
# Which method is better for Manila QoS(independent way or just use extra specs )<br />
#* link:http://paste.openstack.org/show/477677/ <br />
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities(https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?<br />
eg: share_type: qos_support='<is> True' or '<is> False' netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100<br />
driver update: qos_support=true<br />
<br />
# Manila DR update<br />
#* Still no reviews on https://review.openstack.org/#/c/238572/<br />
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?<br />
#* 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?<br />
# Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
'''Scheduled for 5 Nov, 2015, 15:00 UTC'''<br />
# Decide on read-only access rules as a required feature<br />
# Manila DR - Design/Code feedback (gouthamr) <br />
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]<br />
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]<br />
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]<br />
<br />
'''Scheduled for 1 Oct, 2015, 15:00 UTC'''<br />
# Liberty RC2 status<br />
#* https://launchpad.net/manila/+milestone/liberty-rc2<br />
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z<br />
# Mitaka Design Summit<br />
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst<br />
# Manila Client Nova Style Microversion Support (cfouts)<br />
#* https://review.openstack.org/#/c/229142/<br />
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html<br />
<br />
<br />
'''Scheduled for 24 Sep, 2015, 15:00 UTC'''<br />
# 3rd-party CI status<br />
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500<br />
#* http://ci-watch.tintri.com/project?project=manila<br />
# Liberty RC status<br />
# Support for QoS in Manila (zhongjun2)<br />
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
#* https://wiki.openstack.org/wiki/Manila/QoS<br />
# Reminder for backend driver maintainers to update feature support table (toabctl)<br />
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html<br />
# Regression when using NetApp - license issue with netapp_lib (toabctl)<br />
#* https://bugs.launchpad.net/cinder/+bug/1499334<br />
# Mitaka Design Summit<br />
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics<br />
# Vendor driver docs<br />
# Open Discussion<br />
<br />
<br />
http://eavesdrop.openstack.org/meetings/manila/</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/QoS&diff=96564Manila/QoS2015-11-12T13:20:14Z<p>Zhongjun2: /* Method 1 */</p>
<hr />
<div>=Intro=<br />
<br />
<br />
https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
<br />
The goal is to add an interface so that Manila admins can use to set share QoS<br />
specification (IOPS, bandwidth, Latency, priority and other vendor specified attributes),<br />
which can be enforced in Manila back-end;<br />
<br />
The design for QoS isn't complete. We have a vision for the feature, and we're trying to define the details.<br />
<br />
=Problem description=<br />
<br />
The current implementation of QoS spec management process in<br />
Manila provides no validation of the specs key/value pair.<br />
Administrators have no way to get a response as to whether the QoS spec<br />
key/value pair they just created is valid or not. The validation of the<br />
key/value pair only happens during the share creation process which is far too<br />
late by that point. Having a validation of the key/value pair done immediately<br />
within the QoS spec creation or edit process will significantly improve the<br />
usability and user experience of this task.<br />
<br />
=Method 1=<br />
Use the extra-specs tables with vendor scoped keys.<br />
<br />
How to make sure the user need create a share with qos?<br />
<br />
1、Add qos_support in share type to make sure the user need create a share with qos.<br />
<br />
eg: share_type: qos_support='<is> True' or '<is> False'<br />
netapp:max_iops=100<br />
driver update: qos_support=true<br />
<br />
Add qos_support in common capabilities.(https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)<br />
<br />
=Method 2=<br />
<br />
Add an interface so that admins can use to express QoS requirements for shares<br />
(of specific back-ends), which will be consumed by back-end drivers.<br />
<br />
- Add a new resource extension to 'types_extra_specs' API extension to allow list/create/update/delete of type QoS specs.<br />
- Modify 'type_manage' API extension to be able to accept QoS specification info.<br />
qos-associate Associates qos specs with specified share type.<br />
qos-create Creates a qos specs.<br />
qos-delete Deletes a specified qos specs.<br />
qos-disassociate Disassociates qos specs from specified share type.<br />
qos-disassociate-all Disassociates qos specs from all associations.<br />
qos-get-association Gets all associations for specified qos specs.<br />
qos-key Sets or unsets specifications for a qos spec.<br />
qos-list Lists qos specs.<br />
qos-show Shows a specified qos specs.<br />
- Modify share_types.create() to accept QoS specification info and do the checks.<br />
- Add 'qos_specs' to request_specs and filter properties for a share create request and pass to driver.<br />
- To enable the QoS for Manila driver, an qos spec needs to bind to a share type. All the following<br />
changes apply to the Manila driver code.<br />
Create share: If QoS is enabled and specs is available as the QoS key, set the qos spec of the share<br />
into the specified qos spec value.<br />
Create snapshot: The QoS attributes will be copied to the snapshot.<br />
Create share from snapshot: If QoS is enabled and IOThrottling is available as the QoS key, set the<br />
qos spec of the share into the specified qos spec value.<br />
<br />
Database schema changes:<br />
<br />
* A new qos_specs_id boolean column will be added to the share_types table.<br />
* A new quality_of_service_specs table will be created for a particular share types. There will be<br />
one entry in quality_of_service_specs table for every share_type_id and specs_id combination.<br />
It will be a one-to-one relationship.<br />
<br />
::<br />
<br />
mysql> DESC quality_of_service_specs;<br />
+------------+--------------+------+-----+---------+-------+<br />
| Field | Type | Null | Key | Default | Extra |<br />
+------------+--------------+------+-----+---------+-------+<br />
| created_at | datetime | YES | | NULL | |<br />
| updated_at | datetime | YES | | NULL | |<br />
| deleted_at | datetime | YES | | NULL | |<br />
| deleted | tinyint(1) | YES | | NULL | |<br />
| id | varchar(36) | NO | PRI | NULL | |<br />
| specs_id | varchar(36) | YES | MUL | NULL | |<br />
| key | varchar(255) | YES | | NULL | |<br />
| value | varchar(255) | YES | | NULL | |<br />
+------------+--------------+------+-----+---------+-------+<br />
8 rows in set (0.00 sec)<br />
<br />
mysql> DESC share_types;<br />
+--------------+--------------+------+-----+---------+-------+<br />
| Field | Type | Null | Key | Default | Extra |<br />
+--------------+--------------+------+-----+---------+-------+<br />
| created_at | datetime | YES | | NULL | |<br />
| updated_at | datetime | YES | | NULL | |<br />
| deleted_at | datetime | YES | | NULL | |<br />
| deleted | tinyint(1) | YES | | NULL | |<br />
| id | varchar(36) | NO | PRI | NULL | |<br />
| name | varchar(255) | YES | | NULL | |<br />
| qos_specs_id | varchar(36) | YES | MUL | NULL | |<br />
| is_public | tinyint(1) | YES | | NULL | |<br />
+--------------+--------------+------+-----+---------+-------+<br />
8 rows in set (0.00 sec)<br />
<br />
<br />
REST API impact:<br />
<br />
* Extend share type creation response to include qos_specs_id field<br />
* Extend share type list to include qos_specs_id field<br />
* Extend share type detail to include qos_specs_id field<br />
* Add ability to create/delete a qos specs<br />
* Add ability to associates/disassociate qos specs with specified share type<br />
* Add policy for the new extension<br />
<br />
Other end user impact:<br />
<br />
* Manila-ui should be updated to support this new extension.<br />
* python-manilaclient should be updated to allow the use of this new extension.<br />
<br />
Proposed python-manilaclient shell interface::<br />
<br />
manila qos-associate <qos_specs> <share_type_id><br />
Associates qos specs with specified share type.<br />
<br />
manila qos-create <name> [--max_kbps <max_kbps>] [--min_kbps <min_kbps>] [--max_iops <max_iops>] [--min_iops <min_iops>] <key=value> [<key=value> ...]<br />
Creates a qos specs.<br />
max: The prefix 'Max_' is means the max value can not be exceed.<br />
<br />
min: The prefix 'min_' is means the min value is a soft limit, that make the current value is larger than the minimum value as much as possible. <br />
<br />
manila qos-delete [--force <True|False>] <qos_specs><br />
Deletes a specified qos specs.<br />
<br />
manila qos-disassociate <qos_specs> <share_type_id><br />
Disassociates qos specs from specified share type.<br />
<br />
manila qos-disassociate-all <qos_specs><br />
Disassociates qos specs from all associations.<br />
<br />
manila qos-get-association <qos_specs><br />
Gets all associations for specified qos specs.<br />
<br />
manila qos-key <qos_specs> <action> key=value [key=value ...]<br />
Sets or unsets specifications for a qos spec.<br />
<br />
manila qos-list<br />
Lists qos specs.<br />
<br />
manila qos-show <qos_specs><br />
Shows a specified qos specs.<br />
<br />
=Question=<br />
1.Why QoS can not be used in the same way - extra specs with possibilities?<br />
<br />
Because the QoS is an independant resource and special feature. The QoS need a complete set of API.<br />
<br />
<br />
2.Why associate QoS only with share type? why not tenant? user? specific share?<br />
<br />
For user only need to see share_type. If user want to use QoS, then they will associate QoS with share type.<br />
If we provide more access(such as: add QoS as a parameter when we creating a share), User will feel more<br />
complicated.<br />
<br />
=Cinder QoS vs Manila QoS=<br />
*Manila QoS add a few common capabilities in qos-create command.<br />
*Cinder support both front-end QoS and back-end QoS, Manila only support back-end QoS.<br />
<br />
=Assignee(s)=<br />
-----------<br />
<br />
Primary assignee:<br />
zhongjun (jun.zhongjun@huawei.com)<br />
<br />
Other contributors:<br />
zhaohua (zhaohua.zhao@huawei.com)<br />
<br />
=Work Items=<br />
<br />
* Add logic to coordinate calling each driver's ``validate`` function<br />
* Add ``validate`` function to base manila driver<br />
* Add ``validate`` function to lvm driver<br />
<br />
=Dependencies=<br />
<br />
Unit tests for all changed files<br />
<br />
=Documentation Impact=<br />
<br />
* The manila API documentation will need to be updated to reflect the fact that the API may return a failure.<br />
<br />
==Sub Pages==<br />
<br />
<br />
{{Special:PrefixIndex/:Manila/QoS|hideredirects=1}}</div>Zhongjun2https://wiki.openstack.org/w/index.php?title=Manila/QoS&diff=96563Manila/QoS2015-11-12T13:19:57Z<p>Zhongjun2: /* Method 1 */</p>
<hr />
<div>=Intro=<br />
<br />
<br />
https://blueprints.launchpad.net/manila/+spec/manila-support-qos<br />
<br />
The goal is to add an interface so that Manila admins can use to set share QoS<br />
specification (IOPS, bandwidth, Latency, priority and other vendor specified attributes),<br />
which can be enforced in Manila back-end;<br />
<br />
The design for QoS isn't complete. We have a vision for the feature, and we're trying to define the details.<br />
<br />
=Problem description=<br />
<br />
The current implementation of QoS spec management process in<br />
Manila provides no validation of the specs key/value pair.<br />
Administrators have no way to get a response as to whether the QoS spec<br />
key/value pair they just created is valid or not. The validation of the<br />
key/value pair only happens during the share creation process which is far too<br />
late by that point. Having a validation of the key/value pair done immediately<br />
within the QoS spec creation or edit process will significantly improve the<br />
usability and user experience of this task.<br />
<br />
=Method 1=<br />
Use the extra-specs tables with vendor scoped keys.<br />
<br />
How to make sure the user need create a share with qos?<br />
<br />
1、Add qos_support in share type to make sure the user need create a share with qos.<br />
eg: share_type: qos_support='<is> True' or '<is> False'<br />
netapp:max_iops=100<br />
driver update: qos_support=true<br />
<br />
Add qos_support in common capabilities.(https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)<br />
<br />
=Method 2=<br />
<br />
Add an interface so that admins can use to express QoS requirements for shares<br />
(of specific back-ends), which will be consumed by back-end drivers.<br />
<br />
- Add a new resource extension to 'types_extra_specs' API extension to allow list/create/update/delete of type QoS specs.<br />
- Modify 'type_manage' API extension to be able to accept QoS specification info.<br />
qos-associate Associates qos specs with specified share type.<br />
qos-create Creates a qos specs.<br />
qos-delete Deletes a specified qos specs.<br />
qos-disassociate Disassociates qos specs from specified share type.<br />
qos-disassociate-all Disassociates qos specs from all associations.<br />
qos-get-association Gets all associations for specified qos specs.<br />
qos-key Sets or unsets specifications for a qos spec.<br />
qos-list Lists qos specs.<br />
qos-show Shows a specified qos specs.<br />
- Modify share_types.create() to accept QoS specification info and do the checks.<br />
- Add 'qos_specs' to request_specs and filter properties for a share create request and pass to driver.<br />
- To enable the QoS for Manila driver, an qos spec needs to bind to a share type. All the following<br />
changes apply to the Manila driver code.<br />
Create share: If QoS is enabled and specs is available as the QoS key, set the qos spec of the share<br />
into the specified qos spec value.<br />
Create snapshot: The QoS attributes will be copied to the snapshot.<br />
Create share from snapshot: If QoS is enabled and IOThrottling is available as the QoS key, set the<br />
qos spec of the share into the specified qos spec value.<br />
<br />
Database schema changes:<br />
<br />
* A new qos_specs_id boolean column will be added to the share_types table.<br />
* A new quality_of_service_specs table will be created for a particular share types. There will be<br />
one entry in quality_of_service_specs table for every share_type_id and specs_id combination.<br />
It will be a one-to-one relationship.<br />
<br />
::<br />
<br />
mysql> DESC quality_of_service_specs;<br />
+------------+--------------+------+-----+---------+-------+<br />
| Field | Type | Null | Key | Default | Extra |<br />
+------------+--------------+------+-----+---------+-------+<br />
| created_at | datetime | YES | | NULL | |<br />
| updated_at | datetime | YES | | NULL | |<br />
| deleted_at | datetime | YES | | NULL | |<br />
| deleted | tinyint(1) | YES | | NULL | |<br />
| id | varchar(36) | NO | PRI | NULL | |<br />
| specs_id | varchar(36) | YES | MUL | NULL | |<br />
| key | varchar(255) | YES | | NULL | |<br />
| value | varchar(255) | YES | | NULL | |<br />
+------------+--------------+------+-----+---------+-------+<br />
8 rows in set (0.00 sec)<br />
<br />
mysql> DESC share_types;<br />
+--------------+--------------+------+-----+---------+-------+<br />
| Field | Type | Null | Key | Default | Extra |<br />
+--------------+--------------+------+-----+---------+-------+<br />
| created_at | datetime | YES | | NULL | |<br />
| updated_at | datetime | YES | | NULL | |<br />
| deleted_at | datetime | YES | | NULL | |<br />
| deleted | tinyint(1) | YES | | NULL | |<br />
| id | varchar(36) | NO | PRI | NULL | |<br />
| name | varchar(255) | YES | | NULL | |<br />
| qos_specs_id | varchar(36) | YES | MUL | NULL | |<br />
| is_public | tinyint(1) | YES | | NULL | |<br />
+--------------+--------------+------+-----+---------+-------+<br />
8 rows in set (0.00 sec)<br />
<br />
<br />
REST API impact:<br />
<br />
* Extend share type creation response to include qos_specs_id field<br />
* Extend share type list to include qos_specs_id field<br />
* Extend share type detail to include qos_specs_id field<br />
* Add ability to create/delete a qos specs<br />
* Add ability to associates/disassociate qos specs with specified share type<br />
* Add policy for the new extension<br />
<br />
Other end user impact:<br />
<br />
* Manila-ui should be updated to support this new extension.<br />
* python-manilaclient should be updated to allow the use of this new extension.<br />
<br />
Proposed python-manilaclient shell interface::<br />
<br />
manila qos-associate <qos_specs> <share_type_id><br />
Associates qos specs with specified share type.<br />
<br />
manila qos-create <name> [--max_kbps <max_kbps>] [--min_kbps <min_kbps>] [--max_iops <max_iops>] [--min_iops <min_iops>] <key=value> [<key=value> ...]<br />
Creates a qos specs.<br />
max: The prefix 'Max_' is means the max value can not be exceed.<br />
<br />
min: The prefix 'min_' is means the min value is a soft limit, that make the current value is larger than the minimum value as much as possible. <br />
<br />
manila qos-delete [--force <True|False>] <qos_specs><br />
Deletes a specified qos specs.<br />
<br />
manila qos-disassociate <qos_specs> <share_type_id><br />
Disassociates qos specs from specified share type.<br />
<br />
manila qos-disassociate-all <qos_specs><br />
Disassociates qos specs from all associations.<br />
<br />
manila qos-get-association <qos_specs><br />
Gets all associations for specified qos specs.<br />
<br />
manila qos-key <qos_specs> <action> key=value [key=value ...]<br />
Sets or unsets specifications for a qos spec.<br />
<br />
manila qos-list<br />
Lists qos specs.<br />
<br />
manila qos-show <qos_specs><br />
Shows a specified qos specs.<br />
<br />
=Question=<br />
1.Why QoS can not be used in the same way - extra specs with possibilities?<br />
<br />
Because the QoS is an independant resource and special feature. The QoS need a complete set of API.<br />
<br />
<br />
2.Why associate QoS only with share type? why not tenant? user? specific share?<br />
<br />
For user only need to see share_type. If user want to use QoS, then they will associate QoS with share type.<br />
If we provide more access(such as: add QoS as a parameter when we creating a share), User will feel more<br />
complicated.<br />
<br />
=Cinder QoS vs Manila QoS=<br />
*Manila QoS add a few common capabilities in qos-create command.<br />
*Cinder support both front-end QoS and back-end QoS, Manila only support back-end QoS.<br />
<br />
=Assignee(s)=<br />
-----------<br />
<br />
Primary assignee:<br />
zhongjun (jun.zhongjun@huawei.com)<br />
<br />
Other contributors:<br />
zhaohua (zhaohua.zhao@huawei.com)<br />
<br />
=Work Items=<br />
<br />
* Add logic to coordinate calling each driver's ``validate`` function<br />
* Add ``validate`` function to base manila driver<br />
* Add ``validate`` function to lvm driver<br />
<br />
=Dependencies=<br />
<br />
Unit tests for all changed files<br />
<br />
=Documentation Impact=<br />
<br />
* The manila API documentation will need to be updated to reflect the fact that the API may return a failure.<br />
<br />
==Sub Pages==<br />
<br />
<br />
{{Special:PrefixIndex/:Manila/QoS|hideredirects=1}}</div>Zhongjun2