Difference between revisions of "Meetings/Nova"
John Garbutt (talk | contribs) (→Agenda for next meeting) |
John Garbutt (talk | contribs) (→Agenda for next meeting) |
||
| Line 48: | Line 48: | ||
*** oslo.config dropped the automatic config generation, as its proved very hard to maintain | *** oslo.config dropped the automatic config generation, as its proved very hard to maintain | ||
**** http://specs.openstack.org/openstack/oslo-specs/specs/juno/oslo-config-generator.html#developer-impact | **** http://specs.openstack.org/openstack/oslo-specs/specs/juno/oslo-config-generator.html#developer-impact | ||
| − | |||
**** Need an owner for the above work, as oslo.config has removed the old way of things we current use | **** Need an owner for the above work, as oslo.config has removed the old way of things we current use | ||
| + | **** Given how many options we have in so many files, there are concerns around maintaining the list of options | ||
**** Ideally, need care to avoid these fire drills in the future | **** Ideally, need care to avoid these fire drills in the future | ||
**** For this case, added a blueprint to track this effort: https://blueprints.launchpad.net/nova/+spec/oslo-config-generator | **** For this case, added a blueprint to track this effort: https://blueprints.launchpad.net/nova/+spec/oslo-config-generator | ||
| + | **** Our options are: | ||
| + | ***** merge this patch to adopt the new oslo method: https://review.openstack.org/#/c/180013/ | ||
| + | ***** refactor/move all our config definitions so its easier to maintain using the above method | ||
| + | ***** bring back the old config generator into the nova tree and maintain it outside of oslo | ||
** ? | ** ? | ||
Revision as of 12:44, 16 June 2015
Contents
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:
- June 18th 2015 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150618T210000)
- June 25th 2015 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150625T140000)
Add your IRC nick to this list to be pinged at the start of the meeting:
abhishekk mikal tjones cburgess jgrimm adrian_otto funzo mjturek jcookekhugen
irina_pov krtaylor danpb alexpilotti flip214 jaypipes gilliard garyk edleafe dims
moshele anteaya Nisha sileht claudiub lxsli neiljerram markus_z swamireddy alevine
tonyb andreykurilin ndipanov sc68cal akuriata artom jlvillal mnestratov kashyap
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
- http://lists.openstack.org/pipermail/openstack-dev/2015-June/065819.html
- June 23-25: liberty-1 (spec freeze)
- Track liberty priorities:
- Please review things on this list: https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
- Summit follow ups: https://etherpad.openstack.org/p/YVR-nova-liberty-summit-action-items
- Non-spec blueprints to discuss
- ?
- Stuck spec reviews?
- There are a few themes listed here: https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
- ?
- Stable branch status?
- ?
- http://lists.openstack.org/pipermail/openstack-dev/2015-June/065819.html
- Bugs (stuck/critical)
- Gate status
- Critical bugs
- ?
- Open discussion
- Any stuck code reviews to discuss:
- oslo.config dropped the automatic config generation, as its proved very hard to maintain
- http://specs.openstack.org/openstack/oslo-specs/specs/juno/oslo-config-generator.html#developer-impact
- Need an owner for the above work, as oslo.config has removed the old way of things we current use
- Given how many options we have in so many files, there are concerns around maintaining the list of options
- Ideally, need care to avoid these fire drills in the future
- For this case, added a blueprint to track this effort: https://blueprints.launchpad.net/nova/+spec/oslo-config-generator
- Our options are:
- merge this patch to adopt the new oslo method: https://review.openstack.org/#/c/180013/
- refactor/move all our config definitions so its easier to maintain using the above method
- bring back the old config generator into the nova tree and maintain it outside of oslo
- oslo.config dropped the automatic config generation, as its proved very hard to maintain
- ?
- Any stuck code reviews to discuss:
Sub-teams
There are also some Nova subteam meetings. See Nova#Active_Sub-teams: for details.
