Difference between revisions of "Meetings/Nova"
(→Agenda for next meeting) |
(→Weekly Nova team meeting) |
||
| Line 54: | Line 54: | ||
*** What are the rules for the v2 API? Do we not fix 500->400+ bugs there? | *** What are the rules for the v2 API? Do we not fix 500->400+ bugs there? | ||
*** How does any of this get backported to stable if there is a microversion involved to convert a 500 to a 400? Do we allow patch versions on stable/kilo, i.e. v2.3.1? | *** How does any of this get backported to stable if there is a microversion involved to convert a 500 to a 400? Do we allow patch versions on stable/kilo, i.e. v2.3.1? | ||
| + | ** (mriedem) We need a CI job that runs libvirt + LXC; at the Juno midcycle in Portland I thought some RAX guys said they were working on this - was that ever going to happen? We should be able to run it on community infrastructure. Bugs like https://bugs.launchpad.net/nova/+bug/1370590 should not happen. It also seems unfair to require 3rd party CI for libvirt + parallels/virtuozzo but we don't require it for libvirt + LXC. | ||
== Sub-teams == | == Sub-teams == | ||
Revision as of 02:05, 20 August 2015
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:
- August 20th 2015 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150820T140000)
- August 27th 2015 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150827T210000)
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 dannywilson belliott
dguitarbite
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
- August 18: Feature Proposal Freeze (see https://wiki.openstack.org/wiki/FeatureProposalFreeze)
- Updates on feature freeze in here: https://etherpad.openstack.org/p/liberty-nova-non-priority-feature-freeze
- Nova specific things: https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule
- Bugs (stuck/critical)
- Gate status
- Critical bugs
- ?
- Stable branch status: https://etherpad.openstack.org/p/stable-tracker
- Regular Review Reminders
- all please look here for what patches to review: https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
- we have a list of actions: https://etherpad.openstack.org/p/YVR-nova-liberty-summit-action-items and https://etherpad.openstack.org/p/liberty-nova-midcycle
- 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) The madness that is converting a 500 response to a 400+ response and the API microversion hoops that must be jumped through
- http://lists.openstack.org/pipermail/openstack-dev/2015-August/072448.html
- Do we really need a microversion bump to convert a 500 to a 400?
- Do we really need a microversion bump to add a 403 to the list of expected errors in a response?
- What are the rules for the v2 API? Do we not fix 500->400+ bugs there?
- How does any of this get backported to stable if there is a microversion involved to convert a 500 to a 400? Do we allow patch versions on stable/kilo, i.e. v2.3.1?
- (mriedem) We need a CI job that runs libvirt + LXC; at the Juno midcycle in Portland I thought some RAX guys said they were working on this - was that ever going to happen? We should be able to run it on community infrastructure. Bugs like https://bugs.launchpad.net/nova/+bug/1370590 should not happen. It also seems unfair to require 3rd party CI for libvirt + parallels/virtuozzo but we don't require it for libvirt + LXC.
- (mriedem) The madness that is converting a 500 response to a 400+ response and the API microversion hoops that must be jumped through
Sub-teams
There are also some Nova subteam meetings. See Nova#Active_Sub-teams: for details.
