Difference between revisions of "Meetings/Nova"
John Garbutt (talk | contribs) m (→Agenda for next meeting) |
|||
| Line 54: | Line 54: | ||
** Gate status | ** Gate status | ||
*** http://status.openstack.org/elastic-recheck/index.html | *** http://status.openstack.org/elastic-recheck/index.html | ||
| + | *** Time to review the jobs Nova uses on every commit, given the node reduction lately (dansmith) | ||
| + | **** Currently we require 21 nodes in check for all the tests we run | ||
| + | **** Reconsider things like the v2.0 API, postgres, etc jobs? | ||
| + | **** Maybe make ceph our default job (90% of our customers use it, apparently it's not very stable currently)? | ||
** 3rd party CI status | ** 3rd party CI status | ||
*** http://ci-watch.tintri.com/project?project=nova&time=7+days | *** http://ci-watch.tintri.com/project?project=nova&time=7+days | ||
Revision as of 18:07, 3 February 2016
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:
- February 4th 2016 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160204T210000)
- February 11th 2016 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160211T140000)
Add your IRC nick to this list to be pinged at the start of the meeting:
mikal tjones cburgess jgrimm adrian_otto funzo mjturek jcookekhugen
irina_pov krtaylor danpb alexpilotti flip214 jaypipes garyk edleafe dims
moshele anteaya Nisha sileht claudiub lxsli neiljerram markus_z swamireddy alevine
tonyb andreykurilin ndipanov sc68cal akuriata artom jlvillal mnestratov kashyap
aloga rgeragnov bauzas xyang tpatil med_ nic scottda nagyz belliott
dguitarbite sdague jroll diana_clarke _diana_ raildo jichen gjayavelu mdorman klindgren
sorrison belmoreira mrda auggy PaulMurray gcb thorst duncant macsz thomasem tpatzig
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.
Here is the agenda for the next meeting:
- Release Status
- Final date for non-priority features is Friday Feb 5th 2016
- Summary of Non-priority feature freeze: https://etherpad.openstack.org/p/mitaka-nova-non-priority-ff-tracking
- http://lists.openstack.org/pipermail/openstack-dev/2016-February/085455.html
- Mar 1-3, Mitaka-3 and feature freeze, Final release for client libraries, Soft String Freeze, etc.
- http://docs.openstack.org/releases/schedules/mitaka.html
- Final date for non-priority features is Friday Feb 5th 2016
- Regular Reminders
- Review focus list: https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking
- Bugs (stuck/critical)
- Gate status
- http://status.openstack.org/elastic-recheck/index.html
- Time to review the jobs Nova uses on every commit, given the node reduction lately (dansmith)
- Currently we require 21 nodes in check for all the tests we run
- Reconsider things like the v2.0 API, postgres, etc jobs?
- Maybe make ceph our default job (90% of our customers use it, apparently it's not very stable currently)?
- 3rd party CI status
- Critical bugs
- ?
- Reminders:
- volunteers for 1 week of bug skimming duty? Weekly_bug_skimming_duty
- Nova bugs team IRC meeting will start at February the 9th http://lists.openstack.org/pipermail/openstack-dev/2016-January/084543.html
- Stable branch status: https://etherpad.openstack.org/p/stable-tracker
- Gate status
- 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
- DocImpact bugs to get generated into the Nova bug queue
- docs team find it hard to triage with current level of details in commit messages
- trying to not have tests on git commits due to the various issues that creates
- python-novaclient not supporting keystone v3 is causing issues for Cinder
- Midcycle details
- DocImpact bugs to get generated into the Nova bug queue
Sub-teams
There are also some Nova subteam meetings. See Nova#Active_Sub-teams: for details.
