Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2023-03-07
16:41:52 bauzas but I could have missed it
16:42:00 bauzas anyway, action is on me
16:42:22 bauzas next topic, and I'd like to see some quorum on it
16:42:24 bauzas #topic vPTG Planning
16:42:34 bauzas the usual reminder :
16:42:36 bauzas #link https://www.eventbrite.com/e/project-teams-gathering-march-2023-tickets-483971570997 Register your free ticket
16:43:02 bauzas even if this is a free event, it helps the foundation folks to correctly identify the attendance
16:43:21 bauzas #link https://etherpad.opendev.org/p/nova-bobcat-ptg Draft PTG etherpad
16:43:29 bauzas #info we need to agree on the agenda and how many slots we book
16:43:44 bauzas the ptg website is up
16:44:04 bauzas #link https://ptg.opendev.org/ptg.html
16:44:34 bauzas as you see, I've booked four hour slots per day between Tues and Friday
16:44:50 bauzas this is quite a large time, but I don't want to consume all of them
16:45:20 bauzas anyone having other opinions on the strawman proposal of 4x 4 hours ?
16:45:46 bauzas this would be 13:00-17:00 UTC
16:46:22 bauzas ideally, I'd also want to attend the TC sessions so I may require some co-chair if it conflicts
16:47:11 bauzas again, anyone having concerns with this proposal ?
16:47:57 sean-k-mooney no concerns really i assume we will subdevide the 4 hour into 4 50min slots and 10 min breaks
16:48:09 bauzas that's heard and agreed
16:48:21 bauzas I'm not a fan of long running days
16:48:26 bauzas this is exhausting at most.
16:49:05 bauzas I was somehow hoping the PTG could turn into some physical event before I stop running as a PTL, but I was wrong and I need to support it
16:49:57 bauzas and I think we'll possibly never return to a twice-a-year physical design event, so the ship has sailed and we need to get used to it
16:50:17 bauzas zoom FTW, yay.
16:50:36 bauzas anyway, I don't hear strong objections and the schedule is flexible
16:50:44 bauzas we can modify that later if we wish
16:51:09 bauzas this is just a matter of booking or unbooking a timeslot
16:51:20 bauzas moving on then
16:51:56 bauzas #action bauzas to notify the nova community by a ML thread of the proposed agenda for Nova sessions
16:52:34 bauzas again, as a reminder, don't forgot to add your PTG topics in advance
16:52:42 bauzas #topic Review priorities
16:52:49 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:52:54 bauzas moving on
16:53:00 bauzas #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review
16:53:04 bauzas #topic Stable Branches
16:53:09 bauzas elodilles: you have a quick time
16:53:16 elodilles ack
16:53:23 elodilles start with some repetition
16:53:26 elodilles #info stable/2023.1 branches were cut
16:53:34 elodilles #info stable gates seem to be OK - though it's hard to merge patches due to intermittent failures
16:53:43 bauzas unfortunately true
16:53:51 elodilles on older branches especially
16:53:54 elodilles #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:54:02 elodilles and that's all
16:54:07 elodilles to be quick
16:54:25 bauzas thanks a lot
16:54:33 bauzas last topic
16:54:40 bauzas #topic Open discussion
16:54:46 bauzas we have an item
16:54:53 bauzas (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.
16:55:04 bauzas tl;dr: answer is yes, this is expected behaviour
16:55:40 bauzas our release notes tooling provides a list of items based on YAML files that exist on a git branch
16:56:00 bauzas and accordingly heavily relies on git for the ordering and sorting
16:56:16 astupnik ack. I am wondering what's the best approach for tracking known issues?
16:56:33 bauzas known issues that aren't fixed ?
16:56:43 sean-k-mooney we dont really want to retoactivly delete the old release notes for knwon issues
16:56:56 bauzas that's a very good question and I don't have an existing solution on top of my head
16:56:57 sean-k-mooney we generally try ot refence the previous know issue in the patch that fixes it
16:57:02 sean-k-mooney and update the docs where approprate
16:57:35 astupnik the problem is that known issues in release notes only contain new issues, not ones that existed before release...
16:57:50 sean-k-mooney correct that is waht we wanted
16:57:55 astupnik ack
16:57:56 bauzas well, you have a list of known issues per release here https://docs.openstack.org/releasenotes/nova/zed.html
16:57:59 bauzas and others
16:58:17 sean-k-mooney we also tend to do thins like this https://docs.openstack.org/nova/latest/admin/virtual-gpu.html#caveats
16:58:39 bauzas but we don't have a specific page that references a list of known issues over all the releases, despite that being possible with the reno tool, I think
16:59:04 sean-k-mooney i dont know how we would mark them as resolved
16:59:18 bauzas the best remains to bug the worldwide intelligence that stays on that channel :)
16:59:23 sean-k-mooney you dont really want a list of all know issue ever just the ones that are still outstanding
16:59:34 astupnik thank you for clarifications. Simplest way I found is to look for "issue" in release notes folder. I was wondering if there is more user-friendly option.
16:59:40 bauzas sean-k-mooney: yeah tracking is a problem
16:59:46 sean-k-mooney im sure chatgpt can fix this for us :P
16:59:53 bauzas ideally a known issue should mention a bug report
16:59:55 astupnik sean-k-mooney: I want all unresolved issues
17:00:13 sean-k-mooney that is our launchpad open bug list
17:00:19 astupnik heh, ok
17:00:21 bauzas so people should know the status of that issue by querying the bug tracker
17:00:36 bauzas sean-k-mooney: on a side note, I have a PTG topic on it :)
17:00:45 sean-k-mooney ack
17:00:45 bauzas -ETOOMANY open bugs
17:00:58 bauzas let's just axe them ::)
17:01:06 bauzas anyway, we're overtime
17:01:08 bauzas thanks all
17:01:10 bauzas #endmeeting
17:01:10 opendevmeet Meeting ended Tue Mar 7 17:01:10 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
17:01:10 opendevmeet Minutes: https://meetings.opendev.org/meetings/nova/2023/nova.2023-03-07-16.00.html
17:01:10 opendevmeet Minutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-03-07-16.00.txt
17:01:10 opendevmeet Log: https://meetings.opendev.org/meetings/nova/2023/nova.2023-03-07-16.00.log.html
17:01:59 elodilles thanks o/
17:03:05 opendevreview Amit Uniyal proposed openstack/placement master: Bugtracker link update https://review.opendev.org/c/openstack/placement/+/876768
17:26:47 sean-k-mooney bauzas: im conflicted about https://review.opendev.org/c/openstack/nova/+/875621 by the way
17:27:09 sean-k-mooney you should not need to delete those test but we might need to modify them slightly
17:27:30 sean-k-mooney at some point we can drop the version check in the api and the tests
17:27:57 sean-k-mooney perhaps for now we should set https://docs.openstack.org/nova/latest/configuration/config.html#workarounds.disable_compute_service_check_for_ffu
17:27:59 sean-k-mooney in them
17:28:08 sean-k-mooney to disable the compute service verion check
17:32:09 dansmith I'm confused
17:32:26 dansmith I thought we were going to set the min version for bobcat to zed to keep testing N-2 to master
17:32:44 dansmith oh wait, I'm being stupid
17:32:52 dansmith no wait

Earlier   Later