Jump to: navigation, search

Difference between revisions of "Manila/SteinCycle"

(Specs)
(Upgrade Health Checker)
Line 84: Line 84:
  
 
Reviews:
 
Reviews:
* https://review.openstack.org/#/c/611659
+
* https://review.openstack.org/#/c/611659 (Upgrade Health Check Framework: merged)
  
 
+
Next task: define any non-config upgrade checks for implementation in Stein.
Next task: define tasks
 
  
 
Tasks:
 
Tasks:
 +
* implement framework (done)
 +
* define non-config upgrade checks
 +
* implement these
 +
* define and implement config-related upgrade tasks (post Stein?  depends on oslo support)
  
 
== Approved Specs ==
 
== Approved Specs ==

Revision as of 14:26, 26 November 2018

Specs

In Review

Manage/Unmanage Share Servers

Lead: ganso

Reviews:

Share Networks Span Subnets

Lead: ganso

Reviews:

Create share from snapshots in another pool or back end

Lead: ganso

Reviews:

Storage Availability Zone Improvements

Lead: gouthamr

Reviews:

Share and Back End Capabilities Improvements

Lead: gouthamr

Reviews:

Approved Specs

Priority for Access Rules

Lead: zhongjun

Spec: https://specs.openstack.org/openstack/manila-specs/specs/stein/priority-for-access-rules.html

Reviews:

json schema request validation

Lead: ?

Spec:

Reviews:

Notes: gouthamr sent mail to initial committers asking if they are going to continue with this work or not.

Governance Goals

Python3

Lead: vkmc

Tasks:

  • Convert jobs to zuulv3 and allow setting py3 version there
    • Grenade job is still running on Xenial (we will need to explore zuulv3 so that we can set/override the python3 version which currently defaults to 3.5)

Done:

Upgrade Health Checker

Lead: tbarron

Reviews:

Next task: define any non-config upgrade checks for implementation in Stein.

Tasks:

  • implement framework (done)
  • define non-config upgrade checks
  • implement these
  • define and implement config-related upgrade tasks (post Stein? depends on oslo support)

Approved Specs

Priority for Access Rules

Lead: zhongjun

Spec: https://specs.openstack.org/openstack/manila-specs/specs/stein/priority-for-access-rules.html

Reviews:

json schema request validation

Lead: ?

Spec:

Reviews:

Notes: gouthamr sent mail to initial committers asking if they are going to continue with this work or not.

Other Work

OVS->OVN implications

Lead: tbarron

Next: define tasks

Tasks:

Manila UI plugin

Lead: vkmc

Next:

Tasks:

  1. features mappiing - how out of date are we?
  2. selenium test enablement (dustin wants to help)
  3. coordinate with horizon project plugin tests

Manila CSI

Lead: tbarron

Next: follow up with hodgepodge to set standing k8s-sig meeting time (gouthamr)

Tasks:

  • meet with bswartz regarding possibility of node-specific NFS plugin
  • study development/test environments and current proposals (tbarron)

Done:

  • met with CERN CSI developers to co-ordinate
    • idea: common manila master driver and protocol-specific plugins for nodes

Active-Active Share Service

Lead: gouthamr

Next:

Tasks:

uWSGI enablement

Lead: vkmc

Next:

Tasks:

OpenStack Client Integration

Lead: gouthamr

Next:

Tasks:

OpenStack SDK integration

Lead: amito

Workplan: https://storyboard.openstack.org/#!/story/2003752

Next:

Tasks:

  • Add basic resources and actions (Share Types, Shares, Access Rules) (amito)
    • This is nearly done. I will hopefully upload a patch in the upcoming week (01/11/2018, amito)
  • Add supplementary resources and actions (Snapshots, etc) (gouthamr, amito)

OS-Ansible manila role

Lead: Michael Vollman <michael.b.vollman@gmail.com>

Reviews:

Telemetry Extension

Lead: vkmc

Next task: Does this need a spec?

StoryBoard Migration

Probably won't cut over till T release

Lead: tbarron

Next:

Tasks: work with jungleboyj on replacing required launchpad functionality and landing page

Bug Triage

Bug Czar: dustins

Manila Bug Tracking Etherpad

Test Reviews

Lead:

Add link to test review etherpad or track them here?

Reference

Stein PTG Summary