Earlier  
Posted Nick Remark
#openstack-nova - 2023-02-07
16:49:25 bauzas I thought it would be better to somehow have an idea on how many topics we gonna discuss before saying how many slots we need :)
16:49:36 bauzas but I know
16:49:47 bauzas lots of topics will arrive the week before the PTG :)
16:50:03 sean-k-mooney the more virtual ptgs we have the less energy i have for them. that said i would prefer to have more slots over more days then a few short long ones
16:50:04 bauzas the thing is, you have the etherpad, feel free to amend it
16:50:14 sean-k-mooney s/short//
16:50:41 bauzas sean-k-mooney: this cycle, we will also have a "physical PTG" at the middle of bobcat-1
16:50:54 bauzas that could alleviate some discussions
16:50:55 sean-k-mooney that should really be for C planning
16:51:08 bauzas or B implementation phasing :)
16:51:26 sean-k-mooney either/both its close to Spec Freeze
16:51:33 bauzas I haven't checked whether the proposed B agenda is merged yet
16:51:39 sean-k-mooney so proably to late for directional changes on large specs
16:52:01 bauzas sean-k-mooney: don't disagree, I'm just saying it could help some small contributors to get audience when they need
16:52:02 elodilles B schedule was merged
16:52:08 bauzas cool
16:52:10 bauzas so
16:52:13 sean-k-mooney https://releases.openstack.org/bobcat/schedule.html
16:52:16 sean-k-mooney so yes its merged
16:53:02 bauzas https://releases.openstack.org/bobcat/schedule.html ays that pPTG will be 3 weeks before specfreeze (if we agree on the PTG at b-2 being spec freeze)
16:53:23 bauzas so, that's why I'm saying we could have a shorter but productive vPTG
16:53:31 bauzas like 2 hours per day
16:53:45 bauzas (and ideally, I'd like to attend some TC discussions this time)
16:54:00 sean-k-mooney i would prefer to frontload the plannign to the vPTG and have the physical one be more C focused but ok
16:54:16 bauzas don't disagree
16:54:19 sean-k-mooney because of its time in the cycle it feels more like a fourm then a ptg
16:54:23 bauzas anyway, we're rushing out of time
16:54:30 bauzas #topic Review priorities
16:54:41 bauzas #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2)
16:54:47 bauzas #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review
16:54:51 bauzas #topic Stable Branches
16:54:57 bauzas elodilles: you have 5 mins (sorry)
16:54:59 elodilles #info stable branches seem to be OK back till wallaby
16:55:04 bauzas huzzah
16:55:05 elodilles stable/wallaby gate is passing (failing openstacksdk-functional-devstack job was removed from wallaby)
16:55:13 bauzas thanks gmann for the hard work on stable/wallaby
16:55:18 elodilles yepp
16:55:19 elodilles ++
16:55:21 elodilles #info stable/victoria gate is affected by the same failing openstacksdk-functional-devstack job
16:55:30 elodilles #info ussuri and train gates are broken broken ('Could not build wheels for bcrypt, cryptography' errors)
16:55:38 elodilles #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:55:41 elodilles EOM
16:55:54 bauzas elodilles: I'll pay attention to the ussuri branch with the CVE backport
16:56:01 elodilles bauzas: ack
16:56:10 bauzas ... when I have time :)
16:56:18 elodilles bauzas: i have a proposed potential workaround
16:56:26 elodilles for ussuri
16:56:42 bauzas elodilles: cool, let's figure that out after the meeting, tomorrow per say
16:56:51 elodilles bauzas: ++
16:56:54 bauzas fwiw, I'm planning to deliver the cve fix down to ussuri
16:57:07 bauzas but not provide any backport to train
16:57:08 elodilles why not train? :)
16:57:16 bauzas due to the oslo.utils versioning
16:57:26 bauzas most of the distros now made the backports
16:57:36 bauzas so it's upstream support
16:57:42 bauzas and Train is on EM
16:57:50 elodilles well, Wallaby is EM
16:57:56 bauzas and ussuri too
16:57:57 elodilles (and Xena soon, too)
16:58:12 bauzas but it was simple to backport the fix down to ussuri
16:58:19 bauzas it was cheap, so we proposed it
16:58:28 bauzas backporting it to train is a totally different story
16:58:28 elodilles ok :) thanks for that!
16:58:54 bauzas it requires some oslo.utils backport too (and then a janga puzzle with dependency management)
16:59:06 elodilles :S
16:59:24 bauzas so, things are said, crystal clear.
16:59:39 elodilles thanks, i see
16:59:41 bauzas elodilles: thanks elodilles for the stable report
16:59:46 elodilles np
16:59:50 bauzas last point for the 20 secs left
16:59:54 bauzas #topic Open discussion
16:59:59 bauzas nothing on the agenda
17:00:04 bauzas so I'll close the meeting
17:00:16 bauzas feel free to add your items for next week
17:00:19 bauzas thnaks all
17:00:21 bauzas #endmeeting
17:00:21 opendevmeet Meeting ended Tue Feb 7 17:00:21 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
17:00:21 opendevmeet Minutes: https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-07-16.01.html
17:00:21 opendevmeet Minutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-07-16.01.txt
17:00:21 opendevmeet Log: https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-07-16.01.log.html
17:02:33 elodilles thanks o/
17:02:37 sean-k-mooney elodilles: we can chat after the meeting but is the crytography issue beign adressed in train.
17:04:07 gibi bauzas: I left feedback in https://review.opendev.org/c/openstack/nova/+/872975
17:04:29 elodilles sean-k-mooney[m]: ensure-trust workaround seems to be working for stable/ussuri (i proposed it to master last time accidentally): https://review.opendev.org/c/openstack/grenade/+/872969/
17:05:01 bauzas gibi: appreciated. I can speak French, English and a bit of German and Spanish, but my eventlet is definitely small
17:05:24 elodilles sean-k-mooney[m]: and ykarel in neutron added it to tempest (devstack, actually) as well for train, so hopefully something like that should do the trick in train
17:05:53 gibi it is not a big codebase (eventlet + greenlet) but it is not straitforward either. And greenlet has parts of it implemented as a C extension to python :)
17:06:46 bauzas gibi: elodilles: thanks for the reviews
17:07:00 elodilles np
17:07:00 bauzas to clarify, 1/ this is hard to tell which tests are in cause
17:07:16 sean-k-mooney elodilles: ack i was asking as its currenlty blocking a ceilometer/devstack fix i was working on
17:07:43 sean-k-mooney elodilles: changes to the telemetry tempest plugin check for compatiablity with train
17:07:44 bauzas elodilles: you missed today's conversation but I basically grepped the occurrences of such problem trying to intersect the failing tests and basically there were no suspects
17:07:58 bauzas elodilles: because the failing test is not responsible
17:08:21 bauzas elodilles: this is just an unfortunate test that runs at the same time than the thread is throwing the exception
17:08:23 sean-k-mooney elodilles: i tought you siad orginaly ensure-rust would not work
17:08:28 bauzas bite by the bullet
17:08:57 bauzas gibi: about your comment, not sure I fully understand
17:09:09 bauzas gibi: I can remove the DNM: prefix in the log
17:09:14 elodilles sean-k-mooney: yepp, and i was wrong :/ (pushed it to the wrong branch)

Earlier   Later