Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(Weekly Nova team meeting)
(Agenda for next meeting)
Line 38: Line 38:
 
Next meetings scheduled for:
 
Next meetings scheduled for:
  
* February 6 2020 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200206T140000)
 
 
* February 13 2020 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200213T210000)
 
* February 13 2020 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200213T210000)
 +
* February 20 2020 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20200220T140000)
  
 
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 45: Line 45:
 
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-01-30-21.00.html
+
** #link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-02-06-14.00.html
 
*** ACTION: sean-k-mooney to do the train implemented specs business
 
*** ACTION: sean-k-mooney to do the train implemented specs business
 +
**** Done: https://review.opendev.org/#/c/706276/
 
*** ACTION: lyarwood to curate rocky EM list
 
*** ACTION: lyarwood to curate rocky EM list
*** ACTION: lyarwood to propose train & stein releases
+
*** ACTION: efried to ML about spec scrub day
 +
**** Done: http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012424.html
  
 
* #topic Bugs (stuck/critical)
 
* #topic Bugs (stuck/critical)
Line 54: Line 56:
  
 
* #topic Reminders
 
* #topic Reminders
** SPEC FREEZE IS NEXT WEEK
+
** SPEC FREEZE IS NOW
*** At that time I'd like to do a pass through the Definition:Approved specs and decide which we should Direction:Approve and which we should defer.
+
*** I'd like to do a pass through the Definition:Approved specs and decide which we should Direction:Approve and which we should defer.
 
*** #link etherpad for working the scrub (feel free to leave notes etc.) https://etherpad.openstack.org/p/nova-ussuri-planning
 
*** #link etherpad for working the scrub (feel free to leave notes etc.) https://etherpad.openstack.org/p/nova-ussuri-planning
 
*** #link ussuri blueprints https://blueprints.launchpad.net/nova/ussuri
 
*** #link ussuri blueprints https://blueprints.launchpad.net/nova/ussuri
*** 22/42 Design:Approved, including 7 Implemented
+
*** X/Y Design:Approved, including Z Implemented
 
** Rocky EM (lyarwood)
 
** Rocky EM (lyarwood)
 
*** #link open rocky patches https://review.opendev.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/rocky
 
*** #link open rocky patches https://review.opendev.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/rocky
Line 74: Line 76:
 
* #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.
*** [huaqiang] the spec 'mixed cpu policy instance spec' still needs more input
+
*** ?
**** # link Use PCPU and VCPU in one instance : https://review.opendev.org/#/c/668656/
 
**** placement-ess style interface ('resources:(P|V)CPU') vs legacy flavor style (eg: 'hw(:|_)numa_pinned_cpus')  interface through a CPU mask
 
  
 
* #topic Open discussion
 
* #topic Open discussion
** https://blueprints.launchpad.net/nova/+spec/config-tsc-freq
+
** ?
*** https://etherpad.openstack.org/p/invtsc
 
*** proposal is to add the ability to expose an invariant tsc cpu flag and specify the frequency to allow live migration.
 
*** we previously discussed this and said it could be a specless blueprint if the blueprint content was sufficient. do we agree that it is?
 
  
 
== Sub-teams ==
 
== Sub-teams ==

Revision as of 14:24, 7 February 2020

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.

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 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.
      •  ?
  • #topic Open discussion
    •  ?

Sub-teams

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

Previous meetings