[openstack-dev] [Cinder] Midcycle Action item Summary

Kendall Nelson kennelson11 at gmail.com
Fri Jul 22 16:20:53 UTC 2016

Hello All,

   We came out of the Midcycle with a lot of things on a lot of people’s
plates. Here is a summary of what everyone signed up for and what things
need owners.



   Pick a time to meet weekly to discuss and push ahead with Active-Active
   HA (day1)

   Find out the process for how swift uses feature branches and teach us

   Write a devstack to fix config for tempest multibackend (just pass
   $CINDER_ENABLED_BACKENDS through to tempest.conf; make sure the string
   formats match up between tempest and cinder) (day2)



   Make a list of minimal risk Active-Active HA patches to focus on first



   Work with scottda on getting the logic back into Nova (?) that was
   ripped out for setting up multiple back ends; it used to be there but was
   removed because there were errors coming from LVM (day2)

   Work with xyang and e0ne on consolidating a single stable fake driver



   Rebase nested quota support patches (day1)

      https://review.openstack.org/#/c/298453/ Functional Tests for nested

      https://review.openstack.org/#/c/285640/ Cinder test cases for nested



   Figure out what needs to be changed in the client for min vol sizes

   Create a wiki or document and schedule for stable branch release plans



   Write template for email to send to failing CI’s (day1)



   Push code for your stochastic scheduler spec(day3)



   Convert functional job in gate to be a stripped down devstack that can
   have the driver be configured

~~~Needs an owner~~~


   QA Liaison

   Request Infra to make driver branches for old releases (day2)

   Set up project config for driver branches for old releases (day2)

   Spec for the desired result for seamless failback after replication

   Set provisioning to thick=true in all drivers and then change the
   default provisioning to thin (day3)

   Update documentation for tests to explain differences between unit,
   functional, in-tree tempest, and tempest tests- i.e. what services run in
   functional environment versus in-tree tempest tests, what each’s purpose
   is, maybe examples of things that would be tested in each area? (day3)

   Set up jobs for fake driver and real drivers for functional tests (day3)

Links to etherpads where notes were taken and todo’s were set up:

Day1: https://etherpad.openstack.org/p/newton-cinder-midcycle-day1

Day2: https://etherpad.openstack.org/p/newton-cinder-midcycle-day2

Day3: https://etherpad.openstack.org/p/newton-cinder-midcycle-day3


Kendall Nelson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160722/030a6d75/attachment.html>

More information about the OpenStack-dev mailing list