Revision as of 14:44, 18 May 2017

Weekly Nova team meeting

MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-meeting)

This meeting is a weekly gathering of developers working on OpenStack Compute (Nova). We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.

NOTE: this wiki page should be 'emptied' at the end of each meeting.

Agenda for next meeting

Next meetings scheduled for:

• May 18th 2017 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170518T140000)
• May 25th 2017 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170525T210000)
• June 1st 2017 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170601T140000)

Where you see "?" feel free to just edit the wiki and add your item.

Here is the agenda for the next meeting:

• Release News
  • #link Pike release schedule: https://wiki.openstack.org/wiki/Nova/Pike_Release_Schedule
  • #info Next upcoming milestone: Jun 8: p-2 milestone (3 weeks)
  • #info Blueprints: 70 targeted, 66 approved, 12 completed, 6 not started
• Bugs (stuck/critical)
  • Critical bugs
  • #help Need help with bug triage; there are 91 new untriaged bugs as of today (May 18)
  • Gate status
    • #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
  • 3rd party CI
    • #link 3rd party CI status http://ci-watch.tintri.com/project?project=nova&time=7+days
• Reminders
  • #link Pike Review Priorities etherpad: https://etherpad.openstack.org/p/pike-nova-priorities-tracking
  • If you led sessions at the Forum, it would be good to provide summaries in the mailing list.
• Stable branch status:
  • stable/ocata: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata,n,z
  • stable/newton: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/newton,n,z
    • #link We have a few bugs which were regressions in Newton that we need to get fixed on master and backported: https://review.openstack.org/#/c/465042/ https://bugs.launchpad.net/nova/+bug/1658070 https://review.openstack.org/#/c/464088/
• Subteam Highlights
  • Cells v2 (dansmith)
  • Scheduler (edleafe)
  • API (sdague/alex_xu)
  • Notification (gibi)
  • Cinder (mriedem, johnthetubaguy, ildikov) - Review focus is on the new detach flow: https://review.openstack.org/#/c/456896/
    • #help Will need a 3rd core to help move new cinder attach flow changes along.
• Stuck Reviews
  • Please note "stuck review" means a review where there is some disagreement that needs resolving. Its not for reviews that just haven't had attention, except for exceptional cases. Where you see "?" feel free to just edit the wiki and add your item.
  • Any stuck code reviews to discuss:
    •  ?
• Open discussion
  • (mlakat) We'd like to get some advice on: What is the standard OpenStack way of running something (in this case an os.path.getsize()) with a timeout? This came up as part of: https://bugs.launchpad.net/nova/+bug/1691131 Basically what happened is that a broken NFS connection might block os.path.getsize(path) forever. Approaches tried:
    • putting it on a separate green thread: Still blocks the main green thread forever
    • putting it on a separate Thread: We have no way of killing threads nicely in python
    • use multiprocess module: seems to work, but I am a bit worried about the overhead of it
    • Someone must have solved this already in OpenStack
  •  ?

Sub-teams

There are also some Nova subteam meetings. See Nova#Active_Sub-teams: for details.

Previous meetings

• All other meetings are here