Revision as of 21:13, 2 March 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:

• March 2nd 2017 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170302T210000)
• March 9th 2017 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170309T140000)
• March 16th 2017 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170316T210000)

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
• Bugs (stuck/critical)
  • Critical bugs
  • 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 template: https://etherpad.openstack.org/p/pike-nova-priorities-tracking
    • Subteams et al, please update, carrying over from https://etherpad.openstack.org/p/ocata-nova-priorities-tracking as appropriate.
  • Move and/or repropose specs for Pike in the nova-specs repo.
• Stable branch status: https://etherpad.openstack.org/p/stable-tracker
  • 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
    • #info Nova 14.0.4 was released for stable/newton.
  • stable/mitaka: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/mitaka,n,z
    • #info Nova 13.1.3 was released for stable/mitaka.
• Subteam Highlights
  • Cells v2 (dansmith)
  • Scheduler (edleafe)
  • Live Migration (tdurakov)
  • API (sdague/alex_xu)
  • SR-IOV/PCI (moshele)
  • Notification (gibi): [gibi]: I cannot join today. See couple of points below:
    • A short recap from the PTG is on the ML http://lists.openstack.org/pipermail/openstack-dev/2017-March/113098.html
    • Patches for the high prio searchlight notification bp is ready for the cores to look at https://review.openstack.org/#/q/topic:bp/additional-notification-fields-for-searchlight
    • Fix for the hight prio bug https://bugs.launchpad.net/nova/+bug/1665263 is ready for the cores to look at https://review.openstack.org/#/c/437222/
  • PowerVM (efried, thorst)
  • Cinder (mriedem, johnthetubaguy, ildikov)
    • Get lyarwood's bdm uuid/attachment_id DB schema changes in, and support for cinder v3
• 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
  • (mriedem): Spec freeze? Non-priority blueprint freeze?
    • In Newton and Ocata we had spec freeze on the first milestone. Should we still do that for Pike?
    • In Newton we had a non-priority feature freeze between n-1 and n-2. In Ocata we just had the feature freeze at o-3 because of the short schedule. What should we do for Pike? Same as Newton? Non-priority feature freeze at p-2? Or just feature freeze at p-3 for all, priority or not? We have fewer core reviewers so I personally don't want to cut off the majority of blueprints too early in the cycle.
  • (mriedem): The docs team is looking for a liaison from the Nova team to help coordinate things, like getting Nova specific changes into the install guide (like placement and cells v2 from Ocata). Is anyone interested in that role?

Sub-teams

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

Previous meetings

• All other meetings are here