| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-03-07 | |||
| 16:36:04 | bauzas | I'll add the launchpad bobcat series after the meeting so technically, we can now start to approve new specs and specless blueprints | |
| 16:36:20 | sean-k-mooney | ack | |
| 16:36:35 | sean-k-mooney | we should start using the placement repo for placement thigns now too | |
| 16:36:38 | bauzas | that's it for this topic (larger than usual) | |
| 16:36:45 | sean-k-mooney | were started to do that partly last cycle but not consitently | |
| 16:36:58 | bauzas | sean-k-mooney: placement will also have its own launchpad bobcat series | |
| 16:37:05 | sean-k-mooney | yes | |
| 16:37:16 | bauzas | and yeah, we have to mimic the same than nova | |
| 16:37:25 | bauzas | as we agreed on stopping to use Storyboard | |
| 16:37:27 | sean-k-mooney | but we used a mix of stories and task instory board and some lanchpad stuff | |
| 16:37:39 | sean-k-mooney | so lets try and just use lanuchpad this time | |
| 16:37:58 | bauzas | that's a good point, I should somehow signal in Storyboard that we no longer support it for Placezment | |
| 16:38:23 | sean-k-mooney | ideally we should see if we can make it readonly and/or clsoe the exiting issues | |
| 16:38:38 | bauzas | #action bauzas to clean-up the stories in Storyboard and tell their owners to recreate a Launchpad bug or blueprint if they wish to carry it on | |
| 16:39:05 | bauzas | moving on | |
| 16:39:17 | bauzas | #info Uggla and auniyal are the new release liaisons https://review.opendev.org/c/openstack/releases/+/876758 | |
| 16:39:29 | elodilles | \o/ | |
| 16:39:53 | bauzas | elodilles: don't feel overlooked :p | |
| 16:39:58 | elodilles | :] | |
| 16:40:05 | elodilles | i won't :) | |
| 16:40:09 | auniyal | we need to update the bug tracker link here https://opendev.org/openstack/placement | |
| 16:40:39 | bauzas | auniyal: excellent point, fancy creating a change against it ? | |
| 16:40:45 | auniyal | yes | |
| 16:40:52 | sean-k-mooney | i belvie that is in the governance repo | |
| 16:40:53 | bauzas | cool, thanks | |
| 16:41:02 | sean-k-mooney | posibly the main config repo | |
| 16:41:07 | bauzas | sean-k-mooney: I'm pretty it isn't | |
| 16:41:13 | bauzas | sure* | |
| 16:41:38 | bauzas | I've recently seen the project yaml files and I don't remember any mention of the bug tracking system | |
| 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 | |