Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(→‎Agenda for next meeting)
(→‎Agenda for next meeting)
Line 86: Line 86:
 
** (IRC nickname) the topic you would want to discuss.
 
** (IRC nickname) the topic you would want to discuss.
 
** (astupnik) Known Issues section of Release Notes contains only known issues added during specific release cycle instead of complete list of known issues (all issues notes from nova/releasenotes/notes). I am wondering if this is normal or there is some bug in documentation framework? Example: min-bandwidth-workaround-0533ad03f67592a9.yaml introduced using I41f42c1a7595d9e6a73d1261bf1ac1d47ddadcdf and still affecting Nova.
 
** (astupnik) Known Issues section of Release Notes contains only known issues added during specific release cycle instead of complete list of known issues (all issues notes from nova/releasenotes/notes). I am wondering if this is normal or there is some bug in documentation framework? Example: min-bandwidth-workaround-0533ad03f67592a9.yaml introduced using I41f42c1a7595d9e6a73d1261bf1ac1d47ddadcdf and still affecting Nova.
−
** (jsanemet) Review API strategy for 'lock', 'migrate' and 'unshelve' actions. Coming from the following change: https://review.opendev.org/c/openstack/nova/+/875653, it was noted that while for older microversions the API requests are meant to look something like this: { 'lock' : null }, this other undocumented option is also accepted and used extensively by unit tests: { 'lock': {} }. Thing is, the documentation provided here: https://docs.openstack.org/api-ref/compute/#lock-server-lock-action only says that for older microversions the argument's value ought to be null, but not much else is specified in cases is it not. The change tries to fix a problem with so, in that the following: { 'lock': { 'foo': '...' } } was an accepted request that led to no effect on Nova. Now that will not be allowed, but from that comes the question on whether an empty dictionary should be allowed either or not. The same thing goes for the three actions.
 
  
 
== Sub-teams ==
 
== Sub-teams ==

Revision as of 09:53, 13 March 2023

Weekly Nova team meeting

Regular MEETING TIME: Tuesdays 16:00 UTC (#openstack-nova on OFTC)

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.

Project Heartbeat

This information will be updated weekly but not mentioned in the meeting unless specifically called out on the agenda.

Agenda for next meeting

Next meetings scheduled for:

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

Here is the agenda for the next meeting:

  • #topic Stable Branches
  • #topic Sub/related team Highlights
    • #info No subteam left
  • #topic Open discussion
    • (IRC nickname) the topic you would want to discuss.
    • (astupnik) Known Issues section of Release Notes contains only known issues added during specific release cycle instead of complete list of known issues (all issues notes from nova/releasenotes/notes). I am wondering if this is normal or there is some bug in documentation framework? Example: min-bandwidth-workaround-0533ad03f67592a9.yaml introduced using I41f42c1a7595d9e6a73d1261bf1ac1d47ddadcdf and still affecting Nova.

Sub-teams

There are also some Nova subteam meetings. See Nova#Nova_subteams for details.

Previous meetings

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/Nova&oldid=182848"