Jump to: navigation, search

Difference between revisions of "Meetings/Nova"

(Agenda for next meeting)
(Agenda for next meeting)
 
Line 1: Line 1:
  
 
= Weekly Nova team meeting =
 
= Weekly Nova team meeting =
'''MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-meeting)'''
+
 
 +
''' Regular MEETING TIME: '''Tuesdays'''  16:00 UTC (#openstack-nova on OFTC)'''
  
 
This meeting is a weekly gathering of developers working on [[Nova|OpenStack Compute (Nova)]].  We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.
 
This meeting is a weekly gathering of developers working on [[Nova|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.
+
== Project Heartbeat ==
 +
 
 +
This information will be updated weekly but not mentioned in the meeting unless specifically called out on the agenda.
 +
 
 +
* #topic Release News
 +
** #link Nova 2024.2 Dalmatian schedule https://releases.openstack.org/dalmatian/schedule.html
 +
** #link Nova 2024.1 Caracal schedule https://releases.openstack.org/caracal/schedule.html
 +
** #link Nova 2023.2 Bobcat schedule https://releases.openstack.org/bobcat/schedule.html
 +
** #link Nova 2023.1 Antelope schedule https://releases.openstack.org/antelope/schedule.html
 +
 
 +
* #topic Stable branch status
 +
** #link stable/2024.1: https://review.opendev.org/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/placement+OR+project:openstack/nova)+branch:stable/2024.1
 +
** #link stable/2023.2: https://review.opendev.org/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/placement+OR+project:openstack/nova)+branch:stable/2023.2
 +
** #link stable/2023.1: https://review.opendev.org/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/placement+OR+project:openstack/nova)+branch:stable/2023.1
 +
** #link stable/zed: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/placement+OR+project:openstack/nova)+branch:stable/zed
 +
** #link stable/yoga is Unmaintained (branch:unmaintained/yoga)
 +
 
 +
* #topic Bugs (stuck/critical)
 +
** #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags
 +
** #help need help with bug triage
 +
 
 +
* #topic Gate status
 +
** #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
 +
** #link 3rd party CI status (not so dead) http://ciwatch.mmedvede.net/project?project=nova
 +
 
 +
* #topic Review status page
 +
** #link http://status.openstack.org/reviews/#nova
 +
** Count: 438 (+20); Top score: 2303 (+21) (last refresh was 09-03)
 +
** #help Pick a patch near the top, shepherd it to closure
  
 
== Agenda for next meeting ==
 
== Agenda for next meeting ==
  
 
Next meetings scheduled for:
 
Next meetings scheduled for:
* November 26th 2015 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151126T140000)
+
* Apr 02 2024 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2024-04-02T16:00:00)
* December 3rd 2015 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151203T210000)
+
* Apr 09 2024 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2024-04-09T16:00:00)
 
+
* Apr 16 2024 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2024-04-16T16:00:00) CANCELLED
Add your IRC nick to this list to be pinged at the start of the meeting:
+
* Apr 23 2024 16:00 UTC #openstack-nova (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2024-04-23T16:00:00)
<code>
 
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 belliott
 
dguitarbite sdague jroll diana_clarke _diana_ raildo jichen gjayavelu mdorman klindgren
 
sorrison belmoreira mrda mmmpork PaulMurray gcb thorst duncant
 
</code>
 
  
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.
 
Where you see "?" feel free to just edit the wiki and add your item.
  
 
Here is the agenda for the next meeting:
 
Here is the agenda for the next meeting:
* Release Status
+
 
** Virtual doc sprint December 8th and 9th
+
* #topic Bugs (stuck/critical)
** Mitaka-1 is December 1st-3rd
+
** #info [https://bugs.launchpad.net/nova/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress No] Critical bug
*** December 3rd is also non-priority spec and blueprints freeze
+
** #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 67 new untriaged bugs (+2 since the last meeting)
*** https://wiki.openstack.org/wiki/Nova/Mitaka_Release_Schedule
+
** #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
** Specs:
+
** #info bug baton is Uggla
*** https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
+
 
** Review of specless blueprints:
+
* #topic Gate status
*** NOTE: we will not go through the full list in real time, its just to advertise the list and discuss any disagreement/appeal
+
** #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
*** please review the list on here: https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
+
** #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
** Call for backward incompatible changes for python-novaclient 3.0 (mitaka-2): http://lists.openstack.org/pipermail/openstack-dev/2015-November/079915.html
+
** #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
* Regular Reminders
+
** #info Please look at the gate failures and file a bug report with the gate-failure tag.
** New review focus list: https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking
+
** #info #info Please try to provide meaningful comment when you recheck
* Bugs (stuck/critical)
+
 
** Gate status
+
* #topic Release Planning
*** http://status.openstack.org/elastic-recheck/index.html
+
** #link https://releases.openstack.org/dalmatian/schedule.html
** 3rd party CI status
+
** #info Caracal GA on time for tomorrow
*** http://ci-watch.tintri.com/project?project=nova&time=7+days
+
 
** Critical bugs
+
* #topic vPTG Planning
*** ?
+
** #info The vPTG will be held on Apr 8-12
** Reminders:
+
** #info Nova sessions between Tues-Fri 1pm-5pm UTC
*** ?
+
** #link https://etherpad.opendev.org/p/nova-dalmatian-ptg add your own PTG topics in that etherpad
** Stable branch status: https://etherpad.openstack.org/p/stable-tracker
+
** #info Don't forget to register yourselves on http://ptg2023.openinfra.dev/
*** stable/kilo: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo,n,z
+
 
*** stable/juno: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/juno,n,z
+
* #topic Review priorities
*** Juno is frozen for the 2014.2.4 release and then EOL after that.
+
** #link https://etherpad.opendev.org/p/nova-dalmatian-status
* 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.
+
* #topic Stable Branches
** Any stuck code reviews to discuss:
+
** #info stable/202*.* branches' gates seem to be OK, but nova-ceph-multistore is constantly failing (?) on stable/zed
*** https://review.openstack.org/#/c/135387/18/specs/mitaka/approved/improve-unshelve-performance.rst (abhishekk)
+
** #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
*** Encryption support for rbd-backed volumes: https://review.openstack.org/#/c/239798/
+
 
**** How reasonable is it to wait for distros to ship and support a version of QEMU that handles RBD encryption natively?
+
* #topic Sub/related team Highlights
*** ?
+
** #info No subteam left
* Open discussion
+
 
** Moving encryption/decryption code into brick
+
* #topic vmwareapi 3rd-party CI efforts Highlights
*** https://review.openstack.org/#/c/247372/ and at least two mailing list discussions
+
** #info Page for viewing logs and config files also now support links with lines highlighted (Example: http://openstack-ci-logs.global.cloud.sap/openstack-nova-914671-8cvn7/index.html#file=n-cpu-1.service.log&highlight=2318-2348)
*** Some preference being expressed for keeping decryption only in nova, but this doesn't actually match the use cases
+
 
*** Encrypted images need to be figured out and documented I think (DuncanT)
+
* #topic Open discussion
*** Maybe create-encrypted-volume only in cinder (create from image, retype-to-encrypted volume) will work for enough use-cases. This is a key management thing (that barbican was supposed to provide semantics for, no idea if it currently does) not a where-the-code lives thing. Cinder does not want to copy and paste the code into cinder since that always causes issues with the code getting out of sync. Need a decision though, otherwise we'll have to copy-paste (or keep it in brick without nova moving over, which is effectively the same thing)
+
** (add your nick) add your topic
** In the 11/24 #openstack-performance team meeting it was noted that n-api-meta might be causing high CPU load in large ops testing (GoDaddy/Mirantis), mriedem to investigate a large ops job that runs the n-api-meta service; are there any issues with that?
+
** (bauzas) Could https://blueprints.launchpad.net/nova/+spec/aggregatemultitenancyisolation-to-support-unlimited-tenant be a specless blueprint ?
  
 
== Sub-teams ==
 
== Sub-teams ==
  
There are also some Nova subteam meetings.  See [[Nova#Active_Sub-teams:]] for details.
+
There are also some Nova subteam meetings.  See [[Nova#Nova_subteams]] for details.
  
 
== Previous meetings ==
 
== Previous meetings ==
  
 
* [http://eavesdrop.openstack.org/meetings/nova/ All other meetings are here]
 
* [http://eavesdrop.openstack.org/meetings/nova/ All other meetings are here]
* [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-21.01.html 2012-08-16]
 
* [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-21.00.html 2012-08-09]
 
* [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-21.40.html 2012-08-02]
 
  
 
[[category: compute]]
 
[[category: compute]]
 
[[category: meetings]]
 
[[category: meetings]]

Latest revision as of 16:00, 2 April 2024

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 Sub/related team Highlights
    • #info No subteam left

Sub-teams

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

Previous meetings