Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(→‎Project Heartbeat)
(→‎Agenda for next meeting)
Line 41: Line 41:
 
Next meetings scheduled for:
 
Next meetings scheduled for:
  
−
* March 19 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200319T160000)
+
* March 26 2020 16:00 UTC, #openstack-meeting-3 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200326T160000)
  
 
Where you see "?" feel free to just edit the wiki and add your item.
 
Where you see "?" feel free to just edit the wiki and add your item.
Line 47: Line 47:
 
Here is the agenda for the next meeting:
 
Here is the agenda for the next meeting:
 
* #topic Last meeting
 
* #topic Last meeting
−
** #link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-03-12-16.00.log.html
+
** #link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-03-19-16.00.log.html
−
** gibi promised to follow up on the ML about the plans for a virtual PTG. This is still an open AP on gibi.
+
** gibi promised to follow up on the ML about the plans for a virtual PTG.
 +
*** proposal sent to the ML #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013555.html but I'm open to any suggestion about the format.
 +
** We had a discussion about the two company rule last week.
 +
*** the resulting ML thread #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013423.html
 +
*** based on the different discussion I'm now proposing a compromise #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013553.html Please raise your voice if you don't like it til next Tuesday
 +
** we discussed the core situation last week as well. It is resulted in a nomination of two new cores. Cores, please cast your votes on the ML til next Monday
 +
*** lyarwood #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013511.html
 +
*** gmann #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013519.html
  
 
* #topic Bugs (stuck/critical)
 
* #topic Bugs (stuck/critical)
Line 58: Line 65:
  
 
* #topic Release Planning
 
* #topic Release Planning
−
** Two weeks until "Final release for non-client libraries" (Apr 3.)
+
** One week until "Final release for non-client libraries" (Apr 3.)
−
*** What are the must-have items in os-vif to be merged before that deadline? #link https://review.opendev.org/#/q/project:openstack/os-vif+status:open
+
*** os-vif #link https://review.opendev.org/#/q/project:openstack/os-vif+status:open
−
*** What about os-resource-classes? #link https://review.opendev.org/#/q/project:openstack/os-resource-classes+status:open
+
*** os-resource-classes #link https://review.opendev.org/#/q/project:openstack/os-resource-classes+status:open
−
*** os-traits? #link https://review.opendev.org/#/q/project:openstack/os-traits+status:open
+
*** os-traits #link https://review.opendev.org/#/q/project:openstack/os-traits+status:open
 +
*** I see nothing open that is a must-have for Ussuri.
 +
*** Who will propose the releases for these libs next week?
  
 
* #topic Stable Branches
 
* #topic Stable Branches
Line 74: Line 83:
 
* #topic Stuck Reviews
 
* #topic Stuck Reviews
 
**  Please note "stuck review" means a review where there is some disagreement that needs resolving. It's not for reviews that just haven't had attention, except for exceptional cases.
 
**  Please note "stuck review" means a review where there is some disagreement that needs resolving. It's not for reviews that just haven't had attention, except for exceptional cases.
−
*** ?
+
*** (brinzhang_): https://review.opendev.org/#/q/topic:bp/destroy-instance-with-datavolume is stuck on whether we want a PATCH API or not.
  
 
* #topic Open discussion
 
* #topic Open discussion
−
** (gibi): I'm getting hit by RH-only patches as core-company diversity is low. Options? Opinions? (I'm just testing the waters here)
+
** (gibi): Note that this weekend EU goes to summer time (e.g. I will go from UTC + 1 to UTC + 2) but the meeting is will remain in 16:00 UTC.
  
 
== Sub-teams ==
 
== Sub-teams ==

Revision as of 08:28, 26 March 2020

Weekly Nova team meeting

MEETING TIME: Thursdays 16:00 UTC (#openstack-meeting-3)

The Thursday 8:00 UTC slot is kept as a unofficial office hour on #openstack-nova for contributors who cannot attend on the official meeting slot.

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
    • lyarwood: anything newsworthy?
  • #topic Sub/related team Highlights
  • #topic Open discussion
    • (gibi): Note that this weekend EU goes to summer time (e.g. I will go from UTC + 1 to UTC + 2) but the meeting is will remain in 16:00 UTC.

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=174346"